Supported Networks

​

Overview

Meridian supports multiple EVM networks with different levels of functionality for each network. This page documents the current network support and capabilities.

​

Contract Addresses

​

Mainnet

​

Non-EIP-3009 Token Note

Chains whose payment token does not natively support EIP-3009 use Permit2 via x402ExactPermit2Proxy 0x402085c248EeA27D92E8b30b2C58ed07f9E20001. This is the canonical exact Permit2 proxy from the official x402 repository, deployed at the same address on supported EVM chains. This includes MegaETH, BSC, and BOT chain testnet and mainnet. For these integrations:

• Keep payTo set to the facilitator 0x8E7769D440b3460b92159Dd9C6D17302b036e2d6
• Set paymentRequirements.asset to the ERC-20 token address the buyer will pay with
• Use Permit2 0x000000000022D473030F116dDEE9F6B43aC78BA3 as the approval target
• Use x402ExactPermit2Proxy 0x402085c248EeA27D92E8b30b2C58ed07f9E20001 as the Permit2 spender

​

Tempo Note

Tempo has no native gas token. Transaction fees are paid in TIP-20 stablecoins such as USDC.e. Meridian uses USDC.e at 0x20C000000000000000000000b9537d11c60E8b50 for payment flows. The public RPC is https://rpc.tempo.xyz, the WebSocket endpoint is wss://rpc.tempo.xyz, the explorer is https://explore.tempo.xyz, and Circle CCTP/Gateway is not currently supported.

​

Testnet

Fluent testnet currently uses a mock USDC deployment, including function mint(to, amount) to receive test USDC.

​

Arc Testnet Note

Arc Testnet uses USDC as the native gas token. Meridian uses the ERC-20 USDC interface at 0x3600000000000000000000000000000000000000 for payment flows. The public RPC is https://rpc.testnet.arc.network, the WebSocket endpoint is wss://rpc.testnet.arc.network, the explorer is https://testnet.arcscan.app, and the Circle CCTP/Gateway domain is 26.

​

Network Monitoring

• Monitor network status via /v1/supported endpoint
• Implement fallback logic for network outages
• Cache network information with appropriate TTL