RPC Errors

Here are some common error messages that Kryptokrona and Kryptokrona-service spit out, why they occured and how to fix them. Listed are also some possible alternative errors which they could spit out.

BAD_ADDRESS / Bad address

Possible Alternative Error: The supplied address parameter is invalid or in an incorrect format

Description: This error can happen when an address you supply is invalid, or the address field in your request is improperly formatted.

Solution: First make sure that the address you are attempting to send to is a valid 99 character long TRTL address, or 236 character integrated address. Next, make sure that your request is properly formatted - for instance, in a SendTransaction request where you are sending from multiple addresses, the address field must be an array of strings, and the address field within the transfers array must be a single string.

WRONG_AMOUNT / Wrong amount

Possible Alternative Error: The requested send amount is in an incorrect format, or your wallet does not have enough balance or available inputs to send the requested amount

Description: This error can happen when the amount you are trying to send within a transaction is above the sum of your available inputs, or is in an incorrect format. This can also occur when you have dust inputs that are unsendable. These generally comprise a very small amount of your balance, but may prevent you from sending all your balance at once.

Solution: This error can be solved by ensuring that the amount you are attempting to send is valid and within the bounds of your available balance, and that your wallet has been properly optimized/fused.

MIXIN_COUNT_TOO_BIG / MixIn count is too big

Possible Alternative Error: I'm not sure if internal node error suggests something else as well, I have seen it only when encountering the mixin too big error.

Description: The network can't find enough outputs to mix your transaction with.

Solution: This can be rectified by using zero mixin or lowering the amount you are sending. This is very unlikely to be encountered on mainnet, and is mainly found on testnet.

NOT_INITIALIZED / Object was not initialized

Description: -

Solution: -

WRONG_PASSWORD / The password is wrong

Possible Alternative Error: The wallet password is incorrect

Description: This is a pretty simple one. The wallet password is wrong. If you're 100% sure it's correct, check that you're opening a wallet file, and it's not got corrupted.

Solution: Enter the correct password! Import via keys if you cannot remember it.

ALREADY_INITIALIZED / The object is already initialized

Description: -

Solution: -

INTERNAL_WALLET_ERROR / Internal error occurred

Description: -

Solution: -

TRANSACTION_SIZE_TOO_BIG / Transaction size is too big

Possible Alternative Error: Transaction is too large to fit in a block, try reducing the amount you are sending

Description: This is caused when the transaction size (in bytes, not amount), is too large to fit into a block. Currently this limit is around 125k bytes, and the size of transactions is based upon how many key images you need to supply for the transaction - each key image comes from a previous transaction, and so if you have lots of small payments, your transactions will need a lot of key images to sum to the desired amount.

Solution: You can either:

• Perform fusion transactions, to fuse your small key images into larger ones, letting you send more at once, or

• Split your one transaction into multiple transactions, until each smaller one can fit into a block. This will slightly raise the fee you have to pay of course.

###SUM_OVERFLOW / Sum overflow

Possible Alternative Error: Amount + fee would cause integer overflow. Please lower the amount you are sending.

Description: When sending a transaction, the amount+fee would cause integer overflow. This is very unlikely to occur in practice, as the data type used is a uint64_t.

Solution: Send a smaller amount in one transaction.

###ZERO_DESTINATION / The destination is empty

Possible Alternative Error: No destination address specified, or amount specified is zero

Description: This is caused by either:

• A transaction amount of zero, or

• No address was specified to transfer to.

Solution: Ensure you supply an address parameter in the transfers array, and that the amount is larger than zero.

TX_CANCEL_IMPOSSIBLE / Impossible to cancel transaction

Description: -

Solution: -

WRONG_STATE / The wallet is in wrong state (maybe loading or saving),try again later

Description: -

Solution: -

OPERATION_CANCELLED / The operation you've requested has been cancelled

Description: -

Solution: -

TX_TRANSFER_IMPOSSIBLE / Transaction transfer impossible

Description: -

Solution: -

WRONG_VERSION / Wrong version

Description: This is encountered when loading the wallet file with walletd. There are a few possible causes for it:

• Your wallet file is the wrong version

• The wallet file has got corrupted.

Solution: Delete the blockchain db, delete the .wallet file, import your keys, and resync from scratch

FEE_TOO_SMALL / Transaction fee is too small

Possible Alternative Error: Transaction fee lower than minimum of 0.1 TRTL.

Description: This occurs if the transaction fee is below the minimum allowed.

Solution: Make sure the fee used is at least 0.1 TRTL, or 10 in atomic units.

KEY_GENERATION_ERROR / Cannot generate new key

Description: -

Solution: -

INDEX_OUT_OF_RANGE / Index is out of range

Description: -

Solution: -

ADDRESS_ALREADY_EXISTS / Address already exists

Possible Alternative Error: The address you are trying to create already exists in this wallet.

Description: The address you are trying to add with createAddress() already exists.

Solution: Um, address already exists, so don't do that? If you just want a new random address, don't supply the view/spend key parameter, and it will generate a random one.

TRACKING_MODE / The wallet is in tracking mode

Possible Alternative Error: This method is not usable in a view only wallet.

Description: This error occurs when you are using a view only wallet (A tracking wallet), and call a method that can only be used with wallets that can spend, such as sendTransaction().

Solution: Don't use methods which require spending with a view only wallet.

WRONG_PARAMETERS / Wrong parameters passed

Possible Alternative Error: Individual errors for each specific issue.

Description: This error can occur in a number of scenarios.

• A supplied private/public key is invalid/cannot be parsed.

• A spend key was specified to createAddress in a view only wallet, or a null spend key was specified in a non view only wallet

• The blocks count given is less than 1

• The blockindex given is less than 1

For more info on the exact error, check your walletd.log or console window.

Solution: Check the API Docs for examples on how to use the method you are toying with, to help determine what parameter is invalid.

OBJECT_NOT_FOUND / Object not found

Description: -

Solution: -

WALLET_NOT_FOUND / Requested wallet not found

Possible Alternative Error: Wallet address could not be found in the wallet container.

Description: The wallet address you are trying to retrieve the balance of does not exist in your wallet container.

Solution: Ensure you are checking the balance of a wallet that exists in your container.

CHANGE_ADDRESS_REQUIRED / Change address required

Possible Alternative Error: No change address given with a multi address wallet.

Description: This occurs when you omit the change address parameter in a transaction. This is not required in a single address wallet, but if multiple addresses have been added to a wallet container, then the change address is required. Generally, you will want this value to be the same as the address you are sending from.

Solution: Include a change address with your requests to allow your code to work with single and multi address wallets.

CHANGE_ADDRESS_NOT_FOUND / Change address not found

Possible Alternative Error: Change address is not present in your wallet container.

Description: This occurs when the address you specified in the change address parameter is not a wallet that exists in your wallet container file.

Solution: Make sure you set the change address value to a wallet address that exists in your container.

DESTINATION_ADDRESS_REQUIRED / Destination address required

Possible Alternative Error: No destination address given with a multi address wallet.

Description: This occurs when you omit the destination address parameter in a fusion transaction. This is not required in a single address wallet, but if multiple addresses have been added to a wallet container, then the destination address is required. Generally, you will want this value to be the same as the address you are sending from.

Solution: Include a destination address with your fusion transactions to allow your code to work with single and multi address wallets.

DESTINATION_ADDRESS_NOT_FOUND / Destination address not found

Possible Alternative Error: Destination address is not present in your wallet container.

Description: This occurs when the address you specified in the destination address parameter is not a wallet that exists in your wallet container file.

Solution: Make sure you set the destination address value to a wallet address that exists in your container.

BAD_PAYMENT_ID / Wrong payment id format

Possible Alternative Error: Payment ID is not 64 characters or is not a valid hex string.

Description: Your payment ID is not a valid, 64 char hex string.

Solution: Ensure you are correctly generating payment ID's. They should contain only a-z 0-9 characters, and be 64 characters long.

BAD_TRANSACTION_EXTRA / Wrong transaction extra format

Possible Alternative Error: Transaction extra is not a valid hex string.

Description: This occurs when your transaction extra is not hex encoded data.

Solution: Your transaction extra should only contain a-z 0-9 characters.

MIXIN_ABOVE_THRESHOLD / Mixin above maximum allowed threshold

Possible Alternative Error: Mixin is above maximum allowed threshold of <x>

Description: This occurs when your anonymity value is above the maximum allowed. You can check the current mixin limits by viewing their values in CryptoNoteConfig.h. Currently, the maximum allowed mixin is 100. This will change to 7 at block 620k.

Solution: Make sure your anonymity value is within the allowed limits.

MIXIN_BELOW_THRESHOLD / Mixin below minimum allowed threshold

Possible Alternative Error: Mixin is below minimum allowed threshold of <x>

Description: This occurs when your anonymity value is above the minimum allowed. You can check the current mixin limits by viewing their values in CryptoNoteConfig.h. Currently, the minimum allowed mixin is 0. This will change to 7 at block 620k.

Solution: Make sure your anonymity value is withing the allowed limits.

CONFLICTING_PAYMENT_IDS / Multiple conflicting payment ID's werespecified via the use of integrated addresses

Description: When using integrated addresses, if a payment ID is specified, it must match the payment ID included in the integrated address. Furthermore, if multiple integrated addresses are used, they must all have the same payment ID.

Solution: Only send to one integrated address at once, and don't include a payment ID, to avoid confusion.

KryptokronaCoind Errors

• https://github.com/Kryptokronacoin/Kryptokronacoin/blob/master/src/NodeRpcProxy/NodeErrors.h

NOT_INITIALIZED / Object was not initialized

Description: -

Solution: -

ALREADY_INITIALIZED / Object has been already initialized

Description: -

Solution: -

NETWORK_ERROR / Network error

Description: KryptokronaCoind is not open / not responding.

Solution: I'm not sure if you can experience this with walletd, I have seen it with walletgreen.

NODE_BUSY / Node is busy

Description: -

Solution: -

INTERNAL_NODE_ERROR / Internal node error

Description: -

Solution: -

REQUEST_ERROR / Error in request parameters

Description: -

Solution: -

CONNECT_ERROR / Can't connect to daemon

Description: -

Solution: -