--- name: error-handling-483bfdd4e05e description: Handle errors when swapping tokens through KyberSwap Aggregator API metadata: tags: - defi - kyberswap - error-handling - debugging - evm provider: KyberSwap homepage: https://kyberswap.com --- # KyberSwap Error Handling Skill This skill helps diagnose and resolve errors that occur when swapping tokens through the KyberSwap Aggregator API. --- ## When to use Use this skill when: - A user encounters an error while using KyberSwap API to swap tokens - A swap transaction fails on-chain - The KyberSwap API returns an error code - A user needs help understanding why their swap failed - Troubleshooting integration issues with KyberSwap Aggregator ## Error Categories Errors are categorized into three phases: 1. **API Errors** - Returned by KyberSwap API during route fetching/building 2. **Pre-Transaction Errors** - Route built successfully, but failed to push the transaction on-chain 3. **On-Chain Errors** - Transaction reverts on the blockchain --- ## Error Handling Workflow Follow this systematic approach when debugging swap failures: ### Step 1: Identify Error Phase 1. **API Error?** Check the HTTP response code and `code` field in JSON 2. **Pre-tx Error?** Check gas estimation or simulation results 3. **On-chain Error?** Check transaction receipt and revert reason ### Step 2: Look Up Error in This Guide 1. Find the error code (e.g., `4008`, `4222`, `4227`) in the API response 2. Navigate to the corresponding error section below: - **API Errors Reference** - for errors during route fetching/building - **Pre-Transaction Errors** - for gas estimation failures - **On-Chain Errors** - for transaction reverts 3. Read the **Description**, **Common Causes**, and **Solutions** for your specific error 4. Follow the recommended solutions in order ### Common Quick Fixes | Symptom | Quick Fix | |---------|-----------| | Route not found | Remove source filters, try smaller amount | | Token not found | Verify address, check chain | | Insufficient output | Increase slippage | | Transfer failed | Check balance and approval | | Request timeout | Retry, check network | | Gas estimation failed (4227) | Refetch route and retry, or use `suggestedSlippage` (not recommended) | | Quoted < estimated (4222) | Fetch fresh route, or exclude RFQ sources | | Slippage invalid | Set `ignoreCappedSlippage: true` (not recommended) | --- ## Best Practices ### Route Freshness - **Never cache routes** for more than 5-10 seconds - Always re-fetch route immediately before building transaction - Markets move fast - stale routes cause failures ### Slippage Configuration - Stablecoin ↔ Stablecoin (e.g. USDC→USDT): **5 bps** (0.05%) - Common tokens (e.g. ETH→USDC, WBTC→ETH): **50 bps** (0.50%) - All other / unknown pairs: **100 bps** (1.00%) ### Rate Limiting - Always include `X-Client-Id` header --- ## API Errors Reference > Note: Error codes 4008, 4009, 4010, 4011 are documented in official KyberSwap API docs. Other codes listed here (including 5-digit variants like 40010, 40011) are based on observed API behavior and may change without notice. > > **Maintenance note:** Observed (non-official) error codes should be periodically re-verified against live API behavior to ensure they are still accurate and relevant. ### Error 4000: Bad Request ```json { "code": 4000, "message": "bad request", "details": [ { "fieldViolations": [ { "field": $validField, "description": "invalid" } ] } ] } ``` **Description:** Generic bad request error with field-specific validation failures. **Common Field Violations:** | Field | Description | Cause | |-------|-------------|-------| | `tokenIn` | `required` | Missing tokenIn parameter | | `tokenIn` | `invalid` | Wrong length, uppercase `0X`, missing `0x` prefix, non-hex chars | | `tokenIn` | `identical with tokenOut` | Same token for input and output | | `tokenOut` | `required` | Missing tokenOut parameter | | `amountIn` | `invalid` | Zero, negative, decimal, scientific notation (1e18), hex (0x...) | | `feeAmount` | `invalid` | Float value instead of integer | | `gasPrice` | `invalid` | Non-numeric value | | `chargeFeeBy` | `invalid` | Value other than `currency_in` or `currency_out` | | `deadline` | `in the past` | Unix timestamp before current time | | `slippageTolerance` | `invalid` | Negative value, or > 2000 without `ignoreCappedSlippage` (build only) | | `recipient` | `required` | Missing recipient in build request | | `route.route` | `empty route` | Empty or null route array in routeSummary | | `to` | `required` | Missing `to` parameter in route/build endpoint | **Solutions:** 1. Read the `fieldViolation` and `description` in the API response to see which field failed and the root cause. 2. For address-related fields: use valid 42-character hex strings with lowercase `0x` prefix (not `0X`) 3. For amount-related fields: use valid integer strings in wei - no decimals, no scientific notation, no hex 4. For `deadline`: use a Unix timestamp in the future (past timestamps are invalid) 5. For `slippageTolerance` in build: keep under 2000, or set `ignoreCappedSlippage: true` 6. Check that all required parameters are included --- ### Error 4001: Query Parameters Malformed ```json { "code": 4001, "message": "unable to bind query parameters", "details": null, "requestId": "" } ``` **Description:** The API cannot parse the query parameters in the request. **Common Causes:** - Invalid value for a boolean query parameter (e.g. not accepted by the API) **Solutions:** 1. For boolean query parameters: use exactly `true` or `false` as required by the API. Avoid other values (e.g. `1`/`0`, `"yes"`/`"no"`). --- ### Error 4002: Request Body Malformed ```json { "code": 4002, "message": "unable to bind request body", "details": null, "requestId": "" } ``` **Description:** The POST request body cannot be parsed (for `/route/build` endpoint). **Common Causes:** - Data types don't match schema (e.g., string instead of number) - Invalid JSON syntax in request body **Solutions:** 1. Ensure that `deadline` and `slippageTolerance` are Numbers. `enableGasEstimation` and `ignoreCappedSlippage` are booleans (`true` or `false`) 2. DO NOT modify the `routeSummary` object - pass it unchanged --- ### Error 4003: Invalid Swap ```json {"code": 4003, "message": "invalid swap"} ``` **Description:** The get route request is invalid and cannot be processed. **Common Causes:** - Error in dex integration from KyberSwap **Solutions:** 1. Try to re-fetch the route after a period of time (recommended) 2. Use `excludedSources` to skip the failing DEX 3. Report to KyberSwap --- ### Error 4004: Invalid config for fee receiver ```json { "code": 4004, "message": "invalid value", "details": null, "requestId": "" } ``` **Description:** The fee configuration is incomplete or invalid. When `feeAmount` is specified, a valid `feeReceiver` address must also be provided to receive the collected fees. **Common Causes:** - `feeAmount` is set but `feeReceiver` is missing or empty - Mismatch between number of `feeAmount` values and `feeReceiver` addresses when using multiple fee receivers **Solutions:** 1. **Add a valid `feeReceiver` address** - Provide the wallet address that should receive the fees 2. **Match fee arrays** - When using multiple receivers, ensure `feeAmount` and `feeReceiver` have the same number of comma-separated values 3. **Remove fee parameters entirely** - If you don't need to charge fees, omit both `feeAmount` and `feeReceiver` --- ### Error 4005: Fee Amount Greater Than Amount In ```json { "code": 4005, "message": "feeAmount is greater than amountIn", "details": null, "requestId": "" } ``` **Description:** The configured fee exceeds the input amount when charging by input token. **Common Causes:** - `feeAmount` set too high relative to `amountIn` - Incorrect `isInBps` configuration (treating BPS as absolute value or vice versa) - Multiple fee receivers with combined fees exceeding input **Solutions:** 1. Reduce `feeAmount` to be less than `amountIn` 2. If using BPS (`isInBps: true`), verify calculation: `10` = 0.1%, `100` = 1% 3. When not using BPS, `feeAmount` is in token wei - ensure it's less than `amountIn` 4. For multiple fees, ensure sum of all `feeAmount` values < `amountIn` --- ### Error 4007: Fee Amount Greater Than Amount Out ```json { "code": 4007, "message": "feeAmount is greater than amountOut", "details": null, "requestId": "" } ``` **Description:** The configured fee exceeds the output amount when charging by output token. **Common Causes:** - `feeAmount` set too high relative to expected `amountOut` - Incorrect `isInBps` configuration (treating BPS as absolute value or vice versa) - Multiple fee receivers with combined fees exceeding input - Using `chargeFeeBy: "currency_out"` with miscalculated fee **Solutions:** 1. Reduce `feeAmount` to be less than expected `amountOut` 2. If using BPS (`isInBps: true`), verify calculation: `10` = 0.1%, `100` = 1% 3. When not using BPS, `feeAmount` is in token wei - ensure it's less than `amountOut` 4. Consider switching to `chargeFeeBy: "currency_in"` for predictable fee calculation 5. Calculate maximum allowable fee based on estimated output --- ### Error 4008: Route Not Found ```json {"code": 4008, "message": "route not found"} ``` **Description:** No viable swap path exists between the specified tokens. **Common Causes:** - No liquidity pools exist for the token pair - Token is not listed on any DEX on this chain - Extremely low liquidity for the pair - Token has transfer restrictions blocking swaps - Too restrictive source filtering (`includedSources`/`excludedSources`) **Solutions:** 1. Verify both tokens are valid and tradeable on this chain 2. Remove source filters to search all liquidity sources 3. Try a different chain if the token is multi-chain 4. Reduce trade size - some routes only work for smaller amounts 5. Refetch route and retry after a short period of time --- ### Error 4009: Amount In Exceeds Maximum ```json {"code": 4009, "message": "amountIn is greater than max allowed"} ``` **Description:** The input amount exceeds the maximum supported by the available liquidity sources or by the current KyberSwap API configuration. **Common Causes:** - Trade size too large **Solutions:** 1. **Reduce the trade size** - split into multiple smaller swaps --- ### Error 4010: No Eligible Pools ```json {"code": 4010, "message": "route not found"} ``` **Description:** No pools are eligible for routing after applying filters. **Common Causes:** - All pools filtered out by `includedSources`/`excludedSources` - Liquidity exists but doesn't meet minimum requirements - Pools exist but have insufficient liquidity for the amount **Solutions:** 1. Remove or adjust source filters 2. Reduce trade size to fit available liquidity 3. Try without `onlyDirectPools` or `onlySinglePath` restrictions 4. Check if pools exist on block explorer for the token pair --- ### Error 4011: Token Not Found ```json {"code": 4011, "message": "token not found"} ``` **Description:** The specified token address cannot be found or is not supported. **Common Causes:** - Token address is incorrect or has typo - Token doesn't exist on this chain - Token is not indexed by KyberSwap - Using wrong chain for the token - Token was recently deployed and not yet indexed **Solutions:** 1. Verify the token contract address on a block explorer 2. Ensure you're using the correct chain 3. Check token address checksums (case-sensitive for EIP-55) 4. For native tokens, use: `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE` 5. For newly deployed tokens, wait for indexing 6. Try swapping a different, well-known token to verify API connectivity --- ### Error 4222: Quoted Amount Smaller Than Estimated *Last verified: 2026-02-19 (observed behavior, not officially documented)* ```json { "code": 4222, "message": "quoted amount is smaller than estimated", "details": null, "requestId": "" } ``` **Description:** The actual quote from an RFQ market maker or limit order source is lower than the initially estimated output amount, causing the route to be rejected. **Common Causes:** - Market price moved between estimation and quote request - RFQ market maker cannot offer the estimated rate for your trade size - Stale estimation due to AMM pool state changes - Price impact compounding in multi-hop routes - High volatility in the token pair **Solutions:** 1. **Fetch new route and retry the request** - Stale routes can cause failures (recommended) 2. **Use `excludeRFQSources: true`** - Avoid RFQ sources and rely only on AMM pools for more consistent pricing 3. **Use `onlyScalableSources: true`** - Stick to pools with predictable, calculable pricing 4. **Reduce trade size** - Smaller amounts typically get better and more stable quotes 5. **Increase slippage tolerance** - If using a tight `slippageTolerance`, the quote may fall outside the acceptable range ### Error 4227: Gas Estimation Failed *Last verified: 2026-02-19 (observed behavior, not officially documented)* ```json { "code": 4227, "message": "estimate gas failed: return amount is not enough", "details": ["estimate gas failed: return amount is not enough"], "requestId": "", "suggestedSlippage": 230 } ``` ```json { "code": 4227, "message": "estimate gas failed: insufficient funds for gas * price + value: have 1031632630608236 want 2000000000000000", "details": [ "estimate gas failed: insufficient funds for gas * price + value: have 1031632630608236 want 2000000000000000" ], "requestId": "" } ``` ```json { "code": 4227, "message": "estimate gas failed: execution reverted: TransferHelper: TRANSFER_FROM_FAILED", "details": [ "estimate gas failed: execution reverted: TransferHelper: TRANSFER_FROM_FAILED" ], "requestId": "" } ``` **Description:** Gas estimation failed during the build step. The API simulates the transaction before returning it, and the simulation reverted. The `message` field contains the specific revert reason. This error has several variants depending on the root cause. #### Variant 1: "return amount is not enough" The simulated swap would return less than the minimum acceptable amount based on current slippage settings. The API provides a `suggestedSlippage` value (in bps) that would make the transaction succeed. **Common Causes:** - Price moved unfavorably between route fetch and build - Slippage tolerance is too tight for current market conditions - High volatility in the token pair - Route includes RFQ sources with changing quotes **Solutions:** 1. **Fetch a new route and retry** - The route is stale; get a fresh quote (recommended) 2. **Use the `suggestedSlippage` value** - The API returns a suggested slippage (e.g., `230` = 2.3%) that would work 3. **Increase slippage tolerance** - Use a higher `slippageTolerance` in the build request **Note:** The `suggestedSlippage` field is helpful but refetching a fresh route is generally the better approach as it gives you an updated price quote. #### Variant 2: "insufficient funds for gas * price + value" The sender's native token balance (e.g., ETH, MATIC) is not enough to cover the transaction value plus gas fees. **Common Causes:** - Sender wallet does not have enough native token to cover `amountIn` (for native token swaps) plus gas fees - Gas price spiked between route fetch and build, increasing the total cost - The `sender` address provided in the build request holds less native token than expected **Solutions:** 1. **Check sender's native token balance** - Ensure the `sender` address has enough native token to cover the full transaction value plus gas fees 2. **Reduce the swap amount** - Lower `amountIn` to leave room for gas fees 3. **Top up the wallet** - Transfer more native token to the sender address before retrying #### Variant 3: "TransferHelper: TRANSFER_FROM_FAILED" The router contract failed to pull the input token from the sender during simulation. **Common Causes:** - Sender has not approved the router contract to spend the input token - Token approval amount is less than `amountIn` - Sender's token balance is less than `amountIn` - The token contract has transfer restrictions (e.g., blacklists, paused transfers, max transfer limits) **Solutions:** 1. **Check token approval** - Ensure the `sender` has approved the `routerAddress` to spend at least `amountIn` of the input token 2. **Check token balance** - Ensure the `sender` holds at least `amountIn` of the input token 3. **Check token restrictions** - Some tokens have blacklists, transfer fees, or pause mechanisms that block transfers --- ### Error 40010: Empty sender address *Last verified: 2026-02-19 (observed behavior, not officially documented)* ```json { "code": 40010, "message": "sender address can not be empty when enable gas estimation", "details": null, "requestId": "" } ``` **Description:** The API requires a sender address to estimate gas costs, but none was provided in the request. **Common Causes:** - Missing `sender` parameter in the API request - Empty string passed as sender address - Using `enableGasEstimation: true` without providing a sender **Solutions:** 1. **Provide a valid sender address** - Include the `sender` parameter with the user's wallet address 2. **Disable gas estimation** - If you don't need gas costs, set `enableGasEstimation: false` (or omit it) 3. **Use a placeholder address** - For quote-only requests, you can use any valid address format (e.g., `0x0000000000000000000000000000000000000001`) --- ### Error 40011: Filtered Liquidity Sources *Last verified: 2026-02-19 (observed behavior, not officially documented)* ```json {"code": 40011, "message": "filtered liquidity sources"} ``` **Description:** A route exists but was filtered out by user-defined liquidity source restrictions, or the user attempted to include a non-existent liquidity source in the `includedSources` field. **Common Causes:** - Using `includedSources` that do not exist or have no liquidity for this pair - Using `excludedSources` that filters out all viable routes **Solutions:** 1. Remove `includedSources` and `excludedSources` parameters 2. Expand the list of included sources 3. Check which DEXs have liquidity for this pair and include them --- ### Error 4221: WETH Not Configured ```json {"code": 4221, "message": "weth not found"} ``` **Description:** WETH (Wrapped ETH) is not configured for this network. **Common Causes:** - Chain doesn't support native token wrapping - Network misconfiguration - Using unsupported testnet **Solutions:** 1. Use the wrapped native token address directly instead of native token address 2. Check if WETH is configured on this chain --- ### Error 4990: Request Canceled *Last verified: 2026-02-19 (observed behavior, not officially documented)* ```json {"code": 4990, "message": "request was canceled"} ``` **Description:** The request was canceled. **Common Causes:** - Client canceled the request - Network latency causing timeout **Solutions:** 1. Retry the request 2. Check network connectivity 3. Try during lower traffic periods 4. If persistent, contact KyberSwap support with `requestId` --- ### Error 500: Internal Server Error ```json { "code": 500, "message": "internal server error", "details": null, "requestId": "" } ``` **Description:** An unexpected error occurred on the KyberSwap server. This is typically a bug or edge case that the API didn't handle gracefully. **Common Causes:** - Invalid `feeReceiver` address format (e.g., non-hex string like "invalid") - Server-side processing error - Malformed data that bypassed initial validation **Solutions:** 1. **Verify all addresses** - Ensure all address fields are valid 42-character hex strings starting with `0x` 2. **Don't modify routeSummary** - Pass the routeSummary exactly as returned from get route API 3. **Retry the request** - The error may be transient --- ### HTTP 404: Chain Not Found ```json { "message": "", "path": "/invalidchain/api/v1/routes?...", "request_id": "", "request_ip": "", "status": 404 } ``` **Description:** The specified chain in the API path is not supported or doesn't exist. **Common Causes:** - Typo in chain name (e.g., "etherium" instead of "ethereum") - Using a testnet that's not supported (e.g., "goerli", "sepolia") - Chain name is case-sensitive or formatted incorrectly **Solutions:** 1. **Use correct chain names** - Refer to the supported chains list: `ethereum`, `bsc`, `polygon`, `arbitrum`, `optimism`, `avalanche`, `base`, `linea`, `mantle`, `sonic`, `berachain`, `ronin`, `unichain`, `hyperevm`, `plasma`, `etherlink`, `monad`, `megaeth` 2. **Check spelling** - Chain names are lowercase and must match exactly 3. **Verify chain support** - New chains may not be immediately available ### PMM/RFQ Errors These errors occur when the route includes PMM (Private Market Maker) or RFQ (Request for Quote) sources such as Hashflow, Bebop, Native, or limit orders. They are returned during the **build-route** step when the maker fails to provide a firm quote. #### Error Categories | Category | Errors | Cause | |----------|--------|-------| | **Blacklist / Banned** | `ErrFirmQuoteBlacklist`, `ErrAddressBanned`, `ErrRFQDenyListed`, `ErrRFQBlacklisted` | Sender address is on the maker's deny list | | **Insufficient Liquidity** | `ErrFirmQuoteInsufficientLiquidity`, `ErrRFQInsufficientLiquidity`, `ErrEmptyOrderList` | Maker doesn't have enough balance or pulled liquidity | | **Amount Too Small** | `ErrMinGreaterExpect`, `ErrOrderIsTooSmall`, `ErrRFQMinSize`, `ErrRFQBelowMinimumAmount` | Trade amount is below the maker's minimum | | **Amount Too Large** | `ErrRFQExceedsSupportedAmounts` | Trade amount exceeds the maker's maximum | | **Market Moved** | `ErrFirmQuoteMarketCondition`, `ErrQuotedAmountSmallerThanEstimated` | Price changed between get-route and build-route | | **Slippage** | `ErrAmountOutLessThanMin(4227)` | Firm quote output is below minimum acceptable amount | | **Rate Limited** | `ErrRFQRateLimit` | Too many requests to the maker | | **Pair Not Supported** | `ErrRFQNoMakerSupports`, `ErrRFQTokenNotSupported` | Maker doesn't support this token pair | | **Volatility** | `ErrRFQMarketsTooVolatile` | Maker refuses to quote due to high volatility | | **Timeout** | `ErrRFQTimeout` | Maker didn't respond in time | | **Same Sender/Maker** | `ErrSameSenderMaker` | Taker and limit order maker are the same address | | **Generic Failure** | `ErrRFQFailed`, `ErrFirmQuoteFailed`, `ErrQuoteSignFailed`, etc. | Catch-all failures from various makers | #### General Handling Methods 1. **Retry with a fresh route** - Most PMM/RFQ errors are transient. Call get-route again to get fresh indicative prices, then build-route. Stale routes are the most common cause of failures. 2. **Exclude the failing source** - Use `excludedSources` to skip the problematic maker (e.g., `excludedSources=hashflow,bebop`). The router will find routes through other liquidity sources. 3. **Adjust trade amount** - If you hit min/max size errors, increase or decrease `amountIn` accordingly. For "gas exceeds size" errors, increase the trade to make it economically viable. 4. **Increase slippage tolerance** - For market-movement and slippage errors, a higher slippage tolerance gives the maker more room. Alternatively, just retry quickly before the price moves further. 5. **Wait and retry for rate limits** - For rate limit errors, back off for a few seconds before retrying. 6. **Use a different wallet for blacklist errors** - Blacklist/banned errors mean the maker has blocked your address. There is no workaround other than using a different sender address. 7. **Don't self-fill limit orders** - For `ErrSameSenderMaker`, use a different wallet than the one that created the limit order. --- ## Pre-Transaction Errors These errors occur **after** successfully calling the Get Route and Build Route APIs, but **before** the transaction lands on-chain. The user's wallet or RPC node fails to estimate gas or submit the transaction. **Flow where these errors occur:** ``` Get Route API ✓ → Build Route API ✓ → Wallet/RPC Submission ✗ (fails here) ``` --- ### Gas Estimation Failed / Cannot Estimate Gas **Description:** The wallet or RPC node failed to estimate gas for the transaction. The transaction was never broadcast to the network. **Common Causes:** - RPC node is overloaded, rate-limited, or experiencing issues - Route has become stale (pool states changed since route was fetched) - Price moved beyond slippage tolerance since route was built - Network congestion causing RPC timeouts - Token contract has transfer restrictions or blacklists **Solutions:** 1. **Retry the transaction** - Transient RPC issues often resolve on retry 2. **Fetch a fresh route** - The route may be stale; call Get Route and Build Route again 3. **Change RPC URL** - Switch to a different RPC provider (e.g., Alchemy, Infura, QuickNode, or chain's public RPC) 4. **Check RPC rate limits** - If using a free RPC, you may be rate-limited; use a paid tier or different provider --- ### Transaction Submission Failed **Description:** Gas estimation succeeded, but the transaction failed to be broadcast to the network. **Common Causes:** - RPC node rejected the transaction - Nonce issues (pending transactions blocking new ones) - Insufficient ETH/native token for gas fees - Network connectivity issues - RPC provider downtime **Solutions:** 1. **Check gas balance** - Ensure sufficient native token (ETH, MATIC, etc.) for gas fees 2. **Reset nonce** - If stuck transactions exist, cancel them or reset wallet nonce 3. **Try a different RPC** - Switch RPC provider to rule out provider-specific issues 4. **Wait and retry** - Network congestion may clear up 5. **Check wallet connection** - Ensure wallet is properly connected to the correct network --- ### Simulation Revert **Description:** The transaction simulation indicates it would revert on-chain. **Common Causes:** - Insufficient token balance - Insufficient token approval - Route expired (stale route data) - Price moved beyond slippage tolerance - Token has transfer fees or restrictions **Solutions:** 1. **Verify balance** - Ensure sender has at least `amountIn` of the input token 2. **Check approval** - Approve `routerAddress` to spend at least `amountIn` 3. **Fetch fresh route** - Re-call Get Route and Build Route immediately before executing 4. **Increase slippage** - Use higher `slippageTolerance` (e.g., from 50 to 100 for 1%) 5. **Check token restrictions** - Some tokens have transfer fees, blacklists, or max transaction limits --- ## On-Chain Errors (Transaction Reverts) These errors occur when a submitted transaction reverts on the blockchain. ### Diagnosing On-Chain Reverts When a transaction reverts, use these tools to decode the revert reason: **Using Foundry `cast run` (recommended — requires archive node):** ```bash cast run {txHash} --rpc-url {RPC_URL} ``` This replays the transaction and shows the full execution trace, including the exact revert reason and the internal call that failed. **Using Foundry `cast call` at historical block (alternative):** ```bash cast call \ --rpc-url {RPC_URL} \ --from {sender} \ --value {tx.value} \ --block {blockNumber} \ {tx.to} \ {tx.data} ``` Replays the call at the block where it reverted. Requires archive node. **Using ethers.js (for non-Foundry environments):** ```javascript const provider = new ethers.JsonRpcProvider(RPC_URL); const tx = await provider.getTransaction(txHash); const receipt = await provider.getTransactionReceipt(txHash); try { await provider.call( { from: tx.from, to: tx.to, data: tx.data, value: tx.value }, receipt.blockNumber ); } catch (error) { console.log("Revert reason:", error.reason || error.message); } ``` **Using block explorer (no tools needed):** Check the transaction on the chain's block explorer (e.g., etherscan.io). Most explorers decode common revert reasons automatically and show them in the transaction details under "Revert Reason" or "Status". > **Note:** `cast run` and historical `cast call` require an **archive node**. Public RPCs often only keep recent state. If you get "missing trie node" errors, use an archive-enabled RPC provider (Alchemy, QuickNode, etc.) or check the block explorer instead. Use the `/swap-status` skill for a guided diagnosis workflow that automates these steps. --- ### TransferHelper: TRANSFER_FROM_FAILED **Description:** The router contract failed to transfer tokens from the sender. **Common Causes:** - Insufficient token approval for router contract - Insufficient token balance in sender wallet **Solutions:** 1. **Check balance:** Ensure sender has at least `amountIn` of the input token 2. **Check approval:** Approve `routerAddress` to spend at least `amountIn`. ```solidity token.approve(routerAddress, amountIn) ``` --- ### TransferHelper: ETH_TRANSFER_FAILED **Description:** Native ETH transfer failed during the swap. **Common Causes:** - Insufficient ETH balance for swap + gas - Contract recipient rejects ETH transfers - Recipient is a contract without receive/fallback function **Solutions:** 1. **Check ETH balance:** Ensure sufficient ETH for both `amountIn` and gas fees 2. **Verify recipient:** If recipient is a contract, ensure it can receive ETH 3. **Check `transactionValue`:** Send exactly the `transactionValue` from build response --- ### Return Amount Is Not Enough (InsufficientAmountOut) **Description:** The actual output amount is less than the minimum required based on slippage settings. **Common Causes:** - Price moved unfavorably between quote and execution - High price volatility - Slippage tolerance too tight - Large trade causing price impact - MEV/sandwich attack **Solutions:** 1. **Increase slippage tolerance:** ```json {"slippageTolerance": 100} // 1% ``` 2. **Re-fetch route:** Get fresh quote immediately before executing 3. **Reduce trade size:** Smaller trades have less price impact 4. **Use private RPC:** Submit through Flashbots or private mempool to avoid MEV --- ### Out of Gas **Description:** The transaction reverted because it consumed all allocated gas before completing the swap. The EVM stops execution when the gas limit is reached, causing the entire transaction to fail and revert. **Common Causes:** - **Gas limit too low:** The gas limit set when submitting the transaction is lower than the actual gas needed for the swap path - **Complex route:** Multi-hop routes or routes through many pools require more gas than simple single-hop swaps - **Underestimation:** Gas estimation (e.g. from `eth_estimateGas` or the build response) was inaccurate due to state change or edge case - **Wallet/SDK default:** The client overwrites the suggested gas limit with a conservative default that is too low for aggregator routes **Solutions:** 1. **Use suggested gas and add buffer:** Take the `gas` or gas estimate from the build response and multiply by 1.2–1.3 (20–30% buffer) when submitting the transaction 2. **Do not cap gas limit:** If your app or wallet caps gas limit, allow a higher cap for KyberSwap routes 3. **Check integration:** Ensure your code passes through the gas limit from the build response instead of replacing it with a fixed or default value 4. **Re-fetch route:** A different route might use fewer hops and less gas; try building again --- ### Call Failed (Internal Liquidity Source Error) **Description:** An internal call to a liquidity source (DEX pool) failed. **Common Causes:** - Pool state changed between quote and execution - Pool has insufficient liquidity - Pool contract is paused or malfunctioning - Route included a deprecated pool **Solutions:** 1. **Wait and retry:** Pool state may stabilize 2. **Re-fetch route:** Get a fresh route that may use different pools 3. **Exclude problematic source:** Use `excludedSources` to skip the failing DEX 4. **Reduce trade size:** May route through more stable pools --- ## Unlisted Error Codes For any error code not documented above, show the raw `code` and `message` from the API response to the user and suggest: 1. Re-fetch the route and retry 2. Check the official KyberSwap API docs: https://docs.kyberswap.com/kyberswap-solutions/kyberswap-aggregator/aggregator-api-specification/evm-swaps --- Source attribution: jiayaoqijia Original project: https://github.com/jiayaoqijia/cryptoskill/blob/69944d183361da29bf536496d6e39c8780150086/skills/defi/kyberswap-official-error-handling/SKILL.md License: AGPL-3.0-only License information: https://www.gnu.org/licenses/agpl-3.0.html Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software. A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public. The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version. An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU Affero General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Remote Network Interaction; Use with the GNU General Public License. Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements. You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see . # Mega AI Hub resource metadata Creator / publisher: jiayaoqijia Original project: https://github.com/jiayaoqijia/cryptoskill/blob/69944d183361da29bf536496d6e39c8780150086/skills/defi/kyberswap-official-error-handling/SKILL.md Attribution basis: Source repository record Fields of work: Marketing Roles: Growth Marketer, Product Marketer, Marketing Analyst Specialties: API Tools: Kyberswap Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: 0fe83e1ecd147d93bebd203882baccec68fcaeba34f5a3c3f330d3704753bf79