This message has the following data encoded and should only be sent
after the interchainTokenId has been properly generated (a user should
not be able to claim just any interchainTokenId)
This message has the following data encoded and should only be sent
after the proper tokens have been procured by the service. It should
result in the proper funds being transferred to the user at the
destination chain.
This message is used to receive an ITS message from the ITS Hub. The ITS Hub applies
certain security checks, and then routes it to the ITS contract. The message is accepted if the
trusted address corresponding to the original source chain is set to the ITS Hub identifier.
This message is used to route an ITS message via the ITS Hub. The ITS Hub applies certain
security checks, and then routes it to the true destination chain. This mode is enabled if the
trusted address corresponding to the destination chain is set to the ITS Hub identifier.
The messages going through the Axelar Network between
InterchainTokenServices need to have a consistent format to be
understood properly. We chose to use abi encoding because it is easy to
use in EVM chains, which are at the front and center of programmable
blockchains, and because it is easy to implement in other ecosystems
which tend to be more gas efficient.