What x402 going multichain looks like in the on-chain numbers
x402 launched on Base in May 2025 and expanded to Solana, Polygon, Avalanche, Sei, and Ethereum mainnet by April 2026. After three months of running a chain-aware revenue scanner across the full asset list, the distribution is sharper than the announcement implied.
The Coinbase announcement of x402's multichain expansion on 8 October 2025 described the change in two sentences: "x402 now supports six EVM chains and Solana mainnet, with USDC available on all of them." The press read it as a routine network expansion. The on-chain settlement distribution since then tells a different story.
Three months of running a chain-aware revenue scanner across every network on the x402 spec — Base, Solana, Polygon, Avalanche, Arbitrum, Optimism, and Ethereum mainnet — produces the volume breakdown below, sampled from the Coinbase Discovery API and verified against on-chain settlement events through Etherscan, Basescan, and the Solana public RPC.
What we measured
The scanner walks the CDP discovery feed, dereferences every
resource's accepts[] array to find its network + payTo, then
checks the per-chain ledger for inbound USDC (and EURC on Base +
Ethereum) over the trailing 30 days. Two separate code paths run
in parallel — eth_getLogs for the six EVM chains, the Solana
getSignaturesForAddress + getTransaction pair for SPL — because
Solana SPL transfers and EVM eth_getLogs are incompatible RPC
surfaces. The full methodology is documented at
agenstry.com/methodology and
the totals it produces refresh every five minutes on the
State of the Agent Economy
report.
Per-chain configuration matters here: an Arbitrum scan over a 30-day
window would naively need ~10 M blocks at ~0.25 s/block. Public free
RPCs reject that. We cap each chain at max_blocks_per_scan — the
ratio of blocks_per_day to that cap is the effective lookback per
chain. Base, Polygon, Optimism, and Ethereum scan a full 30-day
window; Arbitrum gets ~14 days because the block time is faster.
Documented under-count, surfaced in the methodology page.
Three months of distribution
Across the 798 x402-tagged resources currently indexed via CDP discovery (Agenstry registry, May 2026), the chains break out like this:
| Chain | Resources with payTo |
Resources with verifiable revenue (30 d) |
|---|---|---|
| Base | 629 | 16 |
| Solana | 87 | 3 |
| Polygon | 31 | 1 |
| Arbitrum | 24 | 1 |
| Optimism | 18 | 0 |
| Ethereum | 6 | 0 |
| Avalanche | 3 | 0 |
Two observations worth naming:
-
Base remains 79 % of resources and 80 % of settlement despite the multichain announcement. The other six chains together account for fewer than 50 resources with measurable inbound USDC in 30 days. Multichain availability did not redistribute traffic.
-
Solana sits second on resource count and third on settlement. The Coinbase x402 + Solana ecosystem activation on 10 October 2025 introduced 87 distinct payTo wallets within seven months. Three are receiving non-trivial inbound USDC. The Avalanche slot is advertised, almost unused.
The full distribution by source registry — agentic.market, the Coinbase CDP feed, the a2aregistry project, and 11 other ecosystems — sits on the State of the Agent Economy report and updates every five minutes.
Why the distribution stays Base-heavy
The CDP facilitator at
x402.org/facilitator lists Base USDC
first and lists every other chain's facilitator URL as "coming
soon" in three of seven cases. A Base-first README plus a Base-first
example payload in the
x402 SDK quickstart is
documentation pull, not network engineering — but documentation pull
is what builders actually ship against.
Solana's traction is the more interesting data point. The
Solana x402 reference implementation
landed in October 2025 with a complete SendTransaction-based
settlement flow that does not depend on the EVM facilitator. The 87
payTo wallets we see on Solana are not Base operators porting their
endpoints across; they are different operators, with different
agent-card text, and a notably different per-call price distribution
(median 0.05 USDC vs Base's 0.20 USDC). This is the chain x402
should adopt second, not third.
EURC support on Base launched in
April 2026. Our 30-day
totals show 0.32 EURC of inbound across all monitored wallets — three
orders of magnitude below USDC. The asset is technically supported,
practically unused. We continue to scan for it because the cost is
one extra eth_getLogs per scan and reporting "zero" honestly is
part of the surface; if EURC settlement starts growing, our weekly
revenue panel will catch it the same day.
The 79 % concentration is the actionable number
x402 going multichain was framed as a portability story. After three months the on-chain numbers say it is a Base story with optional Solana — and the choice to optimise for Base specifically (RPC cost, facilitator availability, USDC liquidity) remains the operationally correct choice for an x402 builder in 2026. The other five chains exist, are reachable, are not yet earning.
The protocol is healthier with them included than without; multichain removes the single-chain failure mode and gives EVM-native or Solana-native agents an on-ramp without rewriting around Base specifically. Treating the announcement as "x402 is now everywhere" is the misreading. The data says it is still mostly Base. That is useful to know if you are picking a chain for a new x402 deployment this quarter.
Sources
- Coinbase blog: "x402 going multichain" — Coinbase, 8 October 2025.
- x402 specification — Coinbase, ongoing.
- x402 SDK quickstart — Coinbase, retrieved 2026-05.
- CDP Discovery API documentation — Coinbase Developer Platform, retrieved 2026-05.
anza-xyz/x402-solana— Anza, October 2025.- Circle: EURC on Base + x402 — Circle, April 2026.
- Agenstry methodology — on-chain revenue scanner — Agenstry, May 2026.
- State of the Agent Economy — live report — Agenstry, live.
Cite this post
@misc{agenstry-x402-multichain-2026,
author = {Semler, Damiën},
title = {What x402 going multichain looks like in the on-chain numbers},
howpublished = {Agenstry research blog},
year = {2026},
month = {may},
url = {https://agenstry.com/blog/x402-multichain-three-months-onchain}
}