Router
The following table outlines potential errors that may occur during interactions with the router contract in GnoSwap:
Code | Error | Description |
---|---|---|
GNOSWAP-ROUTER-001 | Caller has no permission | Occurs when a user without the required permissions attempts an action restricted to authorized callers. |
GNOSWAP-ROUTER-002 | Not registered token | Occurs when a token used in an operation has not been registered within the router. |
GNOSWAP-ROUTER-003 | Already registered token | Occurs when there is an attempt to register a token that has already been registered. |
GNOSWAP-ROUTER-004 | Can't transfer token while locked | Occurs when a transfer is attempted on tokens that are currently locked and unavailable for transfer. |
GNOSWAP-ROUTER-005 | Invalid input data | Occurs when input data does not match the expected format or parameters, making the operation invalid. |
GNOSWAP-ROUTER-006 | Invalid protocol fee tier | Occurs when an invalid protocol fee tier is provided, such as a tier outside the acceptable range. |
GNOSWAP-ROUTER-007 | Invalid swap fee | Occurs when the swap fee specified in the transaction is not valid for the operation or pool. |
GNOSWAP-ROUTER-008 | Invalid swap type | Occurs when an unsupported or incorrect swap type is specified, causing the transaction to fail. |
GNOSWAP-ROUTER-009 | Invalid pool path | Occurs when an invalid or non-existent pool path is referenced in the transaction. |
GNOSWAP-ROUTER-010 | Wrap,unwrap failed | Occurs when an attempt to wrap or unwrap tokens fails, potentially due to insufficient balance or invalid input. |
GNOSWAP-ROUTER-011 | Less than minimum wugnot amount | Occurs when the amount provided for an operation is below the minimum allowed for wugnot tokens. |
GNOSWAP-ROUTER-012 | Slippage | Occurs when the execution price deviates beyond the user’s specified slippage tolerance, causing the transaction to fail. |
Last updated