Errors
You may encounter an error while interacting with Adena. Below is the list of error codes and their descriptions. We try to display errors and their details as concisely as possible.
Code | Type | Status | Message | Solution |
|---|---|---|---|---|
1000 | NOT_CONNECTED | Failure | A connection has not been established. | The web application must first establish a connection with Adena. |
1001 | UNRESOLVED_TRANSACTION_EXISTS | Failure | An unresolved transaction pop-up exists. | The user must approve or reject the previous transaction prior to initiating a new transaction. |
1002 | INVALID_FORMAT | Failure | The transaction is in an invalid format. | Be sure to match the format and fill it with the parameters Adena supports. |
2000 | WALLET_LOCKED | Failure | Adena is locked. | The user must unlock Adena. |
3001 | ACCOUNT_MISMATCH | Failure | The account does not match the caller. | Be sure to match the caller parameter with the actual account address. |
3002 | NO_ACCOUNT | Failure | No account found on Adena. | The user must create or restore an account on Adena. |
4000 | TRANSACTION_REJECTED | Failure | The transaction has been rejected by the user. | - |
4000 | SIGN_REJECTED | Failure | The signature has been rejected by the user. | - |
4000 | CONNECTION_REJECTED | Failure | The connection request has been rejected by the user. | - |
4000 | SWITCH_NETWORK_REJECTED | Failure | The network change has been rejected by the user. | |
4000 | ADD_NETWORK_REJECTED | Failure | The network addition request has been rejected by the user. | |
4001 | TRANSACTION_FAILED | Failure | Adena could not execute the transaction. | Check if all parameters are accurate. In case it's a blockchain network issue, you'll get an error code coming from the blockchain. |
4001 | SIGN_FAILED | Failure | Adena could not generate the signature hash. | Check if all parameters are accurate. |
4001 | ALREADY_CONNECTED | Failure | The account is already connected to this website. | - |
4001 | NETWORK_TIMEOUT | Failure | The network response has timed out. | Check the connection status of the blockchain network. |
4001 | REDUNDANT_CHANGE_REQUEST | Failure | Unable to change to the current network settings. | - |
4001 | NETWORK_ALREADY_EXISTS | Failure | The network already exists. | - |
4001 | UNADDED_NETWORK | Failure | The network has not been added on Adena. | Use the AddNetwork method to add the custom network to Adena first. |
4005 | UNSUPPORTED_TYPE | Failure | Adena does not support the requested type. | Only use types supported by Adena. |
9000 | UNEXPECTED_ERROR | Failure | Adena has encountered an unexpected error. | |
0 | CONNECTION_SUCCESS | Success | The connection has been successfully established. | - |
0 | GET_ACCOUNT_SUCCESS | Success | Account information has been successfully returned. | - |
0 | TRANSACTION_SUCCESS | Success | Transaction has been successfully executed. | - |
0 | SIGN_SUCCESS | Success | Signature hash has been successfully generated. | - |
0 | ADD_NETWORK_SUCCESS | Success | The network has been successfully added. | - |
0 | SWITCH_NETWORK_SUCCESS | Success | The network has been successfully changed. | - |
//The error thrown when a dapp requests to sign an unsupported transaction type.
{
"status": "failure",
"data": {},
"code": 4005,
"message": "Adena does not support the requested transaction type",
"type": "UNSUPPORTED_TYPE"
}
Need help?
Although most errors are easily comprehensible and resolvable, you may rarely encounter an unexpected issue. If you need support, join the official Gnoland Discord server and ask for help in the #adena channel.
Last modified 19d ago