Anychain describes a single onchain address that can receive stablecoins or tokens from any supported blockchain — without the receiver picking a chain in advance, and without the sender bridging first. It is the receive-side counterpart to a year of cross-chain send-side innovation, made possible by Eco's programmable addresses primitive launched in 2025. Updated April 2026.
​

The reason this is interesting is that "receiving" has always been the asymmetric part of blockchain UX. Senders pick the chain and the route; receivers just publish an address and hope the sender does the right thing. Anychain inverts that: the receiver publishes one address, the sender uses whatever chain is convenient, and the receiver's pre-programmed logic handles the rest the moment funds arrive.
​

Anychain solves the chain-by-chain address juggling problem. Today a payee who wants to accept USDC on Ethereum, Base, Arbitrum, and Solana publishes four addresses or insists every sender bridge first. Most senders won't, payments fail, support tickets pile up. Anychain replaces those four addresses with one that works everywhere.
​

The pain is well-documented. Centralized exchange deposit pages ask the user to pick a network: USDC on Ethereum vs USDC on Solana vs USDC.e on Polygon, and a wrong pick means lost funds. The address itself is an EOA on most chains, which carries no logic. B2B payments suffer the same friction, multiplied by the number of contractors and chains. Agent payments break entirely; an autonomous agent that pays vendors needs to know the right chain at decision time, not after a human emails the deposit address.
​

An anychain address is a deterministic smart contract whose address is identical on every supported chain. Funds arriving on any chain trigger pre-programmed logic. The receiver can keep, swap, route to a final destination, or split. The address is computed from the receiver's wallet and a configuration; the contract deploys lazily on first deposit, so there is no upfront cost.
​

Three properties matter. Determinism: the address is derivable in advance, so the receiver can hand it out before any contract exists. Programmability: the receive logic is configurable — bridge to a treasury, swap to a stablecoin, route to a Solana wallet, split among contractors. Permanence: the address is permanent, not session-scoped, so it can be embedded in invoices, agent prompts, or merchant checkout pages without rotation.
​

Under the hood, cross-chain settlement uses Eco Routes, which selects between Hyperlane and Circle's CCTP based on cost and finality. The receiver's contract verifies the cryptographic execution proof and runs the configured logic. Failed intents refund automatically — no bridge limbo. The same primitive that powers anychain receive also feeds Eco's broader stablecoin orchestration, which currently spans 15 chains including Ethereum, Solana, Base, Arbitrum, Tron, Polygon, plus Unichain.
​

Programmable addresses unlock four high-value patterns: cross-chain payments, B2B treasury routing, agent commerce, and exchange deposit deduplication. Each of these has been chain-by-chain workflow until now, with manual bridging and per-chain support overhead. The anychain pattern collapses them into one address per recipient.
​

Merchant payments. A merchant accepts USDC from any chain a customer holds it on. The contract automatically settles to the merchant's chosen treasury — a Gnosis Safe on Ethereum, a yield protocol like Aave V3 ($13.7B TVL per DeFiLlama), or a Solana wallet. No "please pay on Base" emails.
​

B2B and global payroll. A company paying contractors across chains sends one transaction from its treasury; each contractor's anychain address routes the payment to their preferred chain. This is the largest pain point Eco's launch announcement calls out — eliminating "support tickets and coordination overhead" for international teams.
​

Agent payments. An autonomous agent paying for SaaS or tool calls cannot reliably pick the right chain at decision time. With anychain, the agent pays once on whatever chain it has liquidity, and the merchant's address handles routing. Standards like ERC-7715 for wallet permissions sit naturally on top — the agent gets bounded permissions, the merchant gets the funds.
​

Exchange deposits. Centralized exchanges that historically required per-network deposit addresses can use anychain to deduplicate user-facing deposit flows. The user copies one address; the exchange's anychain contract routes the deposit to the correct internal sub-account regardless of source chain.
​

Developers integrate anychain through Eco's Routes API or CLI. The flow is: derive the address for a recipient, configure the receive logic (forward, swap, split), and publish the address. Funds arriving on any of the 15 supported chains automatically trigger the logic — no per-chain deployment, no manual bridge step. Full setup takes less than an hour for a typical merchant integration.
​

The starting point is the Routes CLI quickstart on GitHub. After installing, an interactive wizard walks through chain selection, token selection, and route configuration. The CLI emits the deterministic address and the configuration manifest. Funds arriving on any supported chain trigger the configured logic — no per-chain deployment script. Permanence and determinism mean the same address can be embedded in invoices or agent prompts and survive contract upgrades.
​

For programmatic environments, the Routes API exposes the same primitives via REST. Stablecoin coverage spans USDC, USDT, USDC.e, oUSDT, USDT0, USDbC, and USDG. Companion primitives like Permit3 let the same address authorize multichain approvals with a single signature, which closes the other half of the multichain UX gap. Together they remove most of the friction a multichain payment used to carry.
​

Stablecoins now circulate across more than ten production chains, and a $318B supply per DeFiLlama (Apr 2026) does not naturally consolidate to one. Anychain is the primitive that lets receivers stop caring which chain a payment arrived on. The asymmetry — senders pick chain, receivers want one address — is finally solved at the protocol layer.
​

The broader pattern is part of how Eco builds. The execution side is Eco Routes; the approval side is Permit3; the receive side is programmable addresses (anychain). Each closes a multichain UX gap that previously fell on the application developer to paper over.
​

Sources and methodology. Stablecoin supply and protocol TVL pulled from DeFiLlama on April 29, 2026. Programmable address mechanics sourced from Eco's launch announcement. Figures refresh quarterly.
​