Implement Axelar cross-chain messaging and interchain token transfers with GMP and ITS.
npx skills add https://github.com/andresdefi/cryptoskills --skill axelar-andresdefi
Please help me install this Agent Skill. Skill: axelar Source: https://github.com/andresdefi/cryptoskills/tree/main/skills/axelar Command: npx skills add https://github.com/andresdefi/cryptoskills --skill axelar-andresdefi
_execute() callback. - Interchain Token Service (ITS): Deploy canonical multichain tokens with deterministic tokenIds, extend them to new chains, and transfer them cross-chain with burn-on-source/mint-on-destination semantics. - Gas Estimation & Recovery: Estimate cross-chain fees via the Axelar SDK or REST API, add gas to underfunded messages, and manually relay stuck transactions. - Use Case: Deploy a cross-chain messenger on Ethereum and Arbitrum, register trusted remotes, estimate gas for the route, send a message, and track its delivery status on Axelarscan until execution. ## Quick Start Ask the agent to write an AxelarExecutable contract that sends a GMP message from Ethereum to Arbitrum with proper gas payment and trusted remote validation.High-intent search queries and answers about installing and using this skill.
Call AxelarGasService.payNativeGasForContractCall with native tokens first, then call gateway.callContract with the destination chain name, address string, and payload. The receiving contract inherits AxelarExecutable and overrides _execute to handle the message.
Gateway callContractWithToken moves Axelar-wrapped assets like axlUSDC that are registered in the Gateway. ITS deploys canonical tokens that burn on the source chain and mint on the destination with a deterministic tokenId, suited for new multichain token deployments.
The most common cause is missing or insufficient gas payment on the source chain. Check for the GasPaidForContractCall event in the source transaction, add gas with addNativeGas if underfunded, or use manualRelayToDestChain from the Axelar SDK.
No. Axelar uses lowercase string chain names like "ethereum", "arbitrum", and "base", not numeric chain IDs like 1 or 42161. Passing a numeric ID routes the message to a nonexistent chain and it will never execute.
Call InterchainTokenFactory.deployInterchainToken on the origin chain with a salt, then deployRemoteInterchainToken for each target chain with gas payment. Use the same deployer address and salt on every chain so the tokenIds link correctly.
Common causes are a missing trusted remote entry, payload encoding that does not match the decoding types, or an insufficient gas limit. Verify the trustedRemotes mapping, match abi.encode and abi.decode parameter order, and raise the gas estimate.
phpmacRun Foundry-style Solidity tests against a forked mainnet with Hardhat v3.
adaptive-enforcement-labRoute events from sources to triggers with filtering and transformation.
prapanchEnforce security, upgrade, testing, and audit readiness for Solidity contract releases.
stanahDesign cross-chain bridges and messaging patterns for Solidity projects.