Route Release status
Documentation revision 2026-09-27. Mainnet contract 1.43.0-preview; testnet 0.10.7-preview. This is a release summary, not a live uptime monitor. Ethereum, Base and Arbitrum USDC → Stellar CCTP quotes now check burn limits, CCTP mappings and pause states at quote time, and source gas history can reach the documented 24 hours within its read budget; see the changelog. Stellar-source CCTP supports exact-amount token approval before the burn. Burns now pass their own signature and submission rechecks. An expired approval, or an expired burn or transfer that was never signed, can be renewed on the same payment. An unfunded payment whose current Stellar action provably expired can be closed, releasing its wallet sequence and holds. See Stellar CCTP approval, approval renewal and closing an expired Stellar payment. Eligible expired NEAR Stellar classic source deposits now support same-payment renewal with fresh wallet signatures; see source renewal. Standalone saved EVM source signatures now support verified cancellation closure on Ethereum, Base and Arbitrum; see signed-source recovery. A verified first-leg EVM cancellation closes the unfunded composed parent and releases unused payment holds. Supported intermediate EVM source cancellations can be closed and explicitly continued on the same parent; see recovery.
Available capabilities#
Route integrates eight provider families; Garden is currently paused. Rift adds optional REST quotes and direct reviewed EVM/Bitcoin order preparation, funding and tracking, with explicit acceptance of variable output. Provider reports remain separate from verified chain settlement. HyperCore and composed Rift execution are not available. Rift health and live quotes for Ethereum USDC → Base USDC and Ethereum USDC → Ethereum AAPLon were verified from isolated Cloudflare staging on October 1, 2026. No orders were created or funded; live order execution and settlement remain unverified. These checks do not establish ongoing availability for every pair. Circle, Allbridge, NEAR, LayerZero and Axelar have execution integrations for specific paths. SwapKit adds simple EVM and native Bitcoin deposit execution on the reviewed paths; Garden is excluded from new quotes and execution. Use Check compatibility, GET /adapters, and the current candidate and wallet-action flags before selecting a payment.
Hosted testnet supports CCTP native USDC from Ethereum Sepolia to Stellar testnet. Mainnet supports the assets and directions exposed by the catalog and execution contract. The testnet example does not restrict the mainnet product to Stellar.
Circle-to-Stellar managed delivery uses OpenZeppelin Channels; customer-funded destination minting is also available. Recipient activation and trustlines remain customer responsibilities. See destination execution.
EVM actions offer wallet submission alongside the existing sign-only flow. The app reserves the handoff, asks its wallet to send the exact legacy transaction, then reports the hash for Route verification. Missing-hash recovery and finalized-cancellation closure are available for the documented recovery cases. New testnet payments default to managed Stellar minting. An expired customer-signed Stellar mint with no recorded submission can be explicitly renewed for a fresh signature; submitted or uncertain mints still require reconciliation.
Auto-route supports two or three separately authorized transfers with a fresh comparison before each remaining leg. Every leg must have an execution builder and receipt verifier; intermediate wallets are currently supported on Ethereum, Base and Arbitrum. Garden paths are excluded while the platform pause is active. Each completed logical Auto-route payment incurs one completion charge. SwapKit supports the simple EVM and native Bitcoin deposit paths described in compatibility.
Availability conditions#
Outbound webhooks require operator approval of the receiver's HTTPS origin and are not generally enabled. Until enabled for your receiver, use polling with backoff.
Prepared, signed and uncertain payments keep their existing identifiers and recovery constraints. Automatic replacement transactions and release of uncertain wallet reservations are not available. See Track and recover.
Documentation and changes#
Use compatibility for supported paths and signing requirements. Current quote and prepared-action flags determine whether a payment can proceed.
Read the changelog for affected fields and required client changes. Billing owns current credit rates and reservation rules.