What problem does it solve? Choosing and correctly implementing a cross-chain rail for Stellar is error-prone: wrong rail selection wastes engineering effort, and mistakes like misencoded CCTP hook data or missing trustlines can permanently destroy funds. This Skill routes each cross-chain task to the right protocol and documents the exact contract calls, encodings, and pitfalls. ## Core Features & Use Cases - Rail selection routing: A decision table maps tasks to Circle CCTP V2 (native USDC burn-and-mint, Stellar domain 27), Axelar GMP (contract-to-contract messaging), Axelar ITS (multichain tokens), or NEAR Intents (intent-based swaps into XLM/USDC). - CCTP V2 deep dive: Verified mainnet/testnet contract addresses, the mandatory CctpForwarder pattern for Stellar recipients, hook-data byte layout with a TypeScript builder, 7-vs-6 decimal handling, and Iris attestation polling. - Axelar GMP and ITS reference: Compile-verified Soroban signatures for pay_gas, call_contract, the AxelarExecutable derive pattern, interchain token deployment, canonical token registration, and flow limits. - Use Case: A user asks to bridge USDC from Base to a Stellar wallet. The Skill routes to cctp.md, which specifies depositForBurnWithHook with the CctpForwarder as mintRecipient, the recipient strkey encoded in hook data, and mint_and_forward on Stellar — avoiding the permanent fund-loss mistake of sending directly to a G… account. ## Quick Start Ask how to bridge USDC from Ethereum to a Stellar account and follow the routed guidance for encoding the forwarder hook data and polling the Iris attestation API.
