API Version: v1.6.0

CCIP v1.6.0 Aptos Errors API Reference

Errors

router

Errors that can occur in the main router module during a ccip_send call.

ccip_send_with_message_id

Error CodeSymbolDescription
2E_UNSUPPORTED_DESTINATION_CHAINThe provided dest_chain_selector does not correspond to a configured and supported destination chain in the router's state.
3E_UNSUPPORTED_ON_RAMP_VERSIONThe on-ramp version for the specified destination chain is not supported by the current router implementation. The call was aborted.

onramp

Errors originating from the onramp module, which handles the core logic for sending messages and tokens.

get_fee_internal

Error CodeSymbolDescription
12E_CURSED_BY_RMNThe transfer is blocked by the Risk Management Network (RMN).

resolve_fungible_asset

Error CodeSymbolDescription
13E_INVALID_TOKENThe provided token address is not a valid fungible asset metadata object.

resolve_fungible_store

Error CodeSymbolDescription
14E_INVALID_TOKEN_STOREThe provided token store address (or the primary store if 0x0 was passed) is not a valid fungible store object for the given token.

ccip_send

Error CodeSymbolDescription
4E_UNKNOWN_DEST_CHAIN_SELECTORThe destination chain configuration for the given dest_chain_selector does not exist.
6E_SENDER_NOT_ALLOWEDThe allow-list is enabled for the destination chain, and the caller's address is not in the list of permitted senders.
10E_UNSUPPORTED_TOKENThe token being transferred is not registered with the token admin registry and has no associated token pool.
15E_UNEXPECTED_WITHDRAW_AMOUNTThe amount of tokens withdrawn from the user's account did not match the expected amount.
16E_UNEXPECTED_FUNGIBLE_ASSETThe fungible asset withdrawn from the user's account does not match the expected asset metadata.
18E_MUST_BE_CALLED_BY_ROUTERAn internal consistency check failed; the on-ramp can only be called by its designated router.
19E_TOKEN_AMOUNT_MISMATCHThe number of items in token_addresses does not match the number of items in token_store_addresses.
20E_CANNOT_SEND_ZERO_TOKENSAn attempt was made to send a token amount of zero, which is not allowed.

fee_quoter

Errors related to fee calculation and processing of message arguments.

get_token_receiver

Error CodeSymbolDescription
11E_UNKNOWN_CHAIN_FAMILY_SELECTORThe destination chain's family (e.g., EVM, SVM) is unknown or not supported, preventing correct processing of extra_args.

process_message_args

Error CodeSymbolDescription
24E_MESSAGE_FEE_TOO_HIGHThe calculated fee in Juels exceeds the maximum allowed fee per message configured in the FeeQuoter.
25E_SOURCE_TOKEN_DATA_TOO_LARGEThe return data from a token pool's lockOrBurn function is larger than the allowed size.

token_admin_registry

Errors that occur when interacting with the token registry to manage token pool states.

start_lock_or_burn

Error CodeSymbolDescription
3E_INVALID_TOKEN_POOLThe token pool address is not a valid, registered TokenPoolRegistration object.
9E_NOT_IN_IDLE_STATEThe token pool is not in an idle state and cannot start a new lockOrBurn operation because it is already busy.
12E_NON_EMPTY_LOCK_OR_BURN_INPUTInternal state inconsistency: The lock_or_burn_input storage was expected to be empty but was not.
13E_NON_EMPTY_LOCK_OR_BURN_OUTPUTInternal state inconsistency: The lock_or_burn_output storage was expected to be empty but was not.
14E_NON_EMPTY_RELEASE_OR_MINT_INPUTInternal state inconsistency: The release_or_mint_input storage was expected to be empty but was not.
15E_NON_EMPTY_RELEASE_OR_MINT_OUTPUTInternal state inconsistency: The release_or_mint_output storage was expected to be empty but was not.

finish_lock_or_burn

Error CodeSymbolDescription
10E_NOT_IN_LOCK_OR_BURN_STATEAn attempt to finish a lockOrBurn operation failed because the token pool was not in the correct LOCK_OR_BURN state.
17E_MISSING_LOCK_OR_BURN_OUTPUTThe lockOrBurn operation could not be completed because the expected output data from the token pool was missing.

token_admin_dispatcher

This module dispatches calls to the appropriate token pool.

dispatch_lock_or_burn

The errors this function can revert with originate from the token_admin_registry module during the start_lock_or_burn and finish_lock_or_burn calls. Refer to the token_admin_registry table for a list of possible errors.

Get the latest Chainlink content straight to your inbox.