Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mrdn.finance/llms.txt

Use this file to discover all available pages before exploring further.

​
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

NetworkChain IDUSDCFacilitator
avalanche431140xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E0x8E7769D440b3460b92159Dd9C6D17302b036e2d6
base84530x833589fCD6eDb6E08f4c7C32D4f71b54bdA029130x8E7769D440b3460b92159Dd9C6D17302b036e2d6
bsc560x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d0x8E7769D440b3460b92159Dd9C6D17302b036e2d6
optimism100x0b2C639c533813f4Aa9D7837CAf62653d097Ff850x8E7769D440b3460b92159Dd9C6D17302b036e2d6
polygon1370x3c499c542cef5e3811e1192ce70d8cc03d5c33590x8E7769D440b3460b92159Dd9C6D17302b036e2d6
unichain1300x078d782b760474a361dda0af3839290b0ef57ad60x8E7769D440b3460b92159Dd9C6D17302b036e2d6
ink570730x2D270e6886d130D724215A266106e6832161EAEd0x8E7769D440b3460b92159Dd9C6D17302b036e2d6
worldchain4800x79A02482A880bCe3F13E09da970dC34dB4cD24D10x8E7769D440b3460b92159Dd9C6D17302b036e2d6
sei13290xe15fC38F6D8c56aF07bbCBe3BAf5708A2Bf423920x8E7769D440b3460b92159Dd9C6D17302b036e2d6
hyperevm9990xb88339CB7199b77E23DB6E890353E22632Ba630f0x8E7769D440b3460b92159Dd9C6D17302b036e2d6
megaeth43260xFAfDdbb3FC7688494971a79cc65DCa3EF82079E70x8E7769D440b3460b92159Dd9C6D17302b036e2d6

​
BSC Note

BSC is supported through the same facilitator address as the other mainnets, but its USDC token does not natively support the EIP-3009 transferWithAuthorization flow used by standard x402 exact payments. Meridian deploys facilitator V4_1 on BSC and configures usdcContract to the BSC EIP3009Forwarder 0x2c2d8EF0664432BA243deF0b8f60aF7aB43a60B4, just as the legacy USDm path does on MegaETH. For BSC integrations:
  • Keep payTo set to the facilitator 0x8E7769D440b3460b92159Dd9C6D17302b036e2d6
  • Treat the BSC USDC token 0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d as the settlement token
  • The buyer must approve the BSC forwarder 0x2c2d8EF0664432BA243deF0b8f60aF7aB43a60B4 once before signing EIP-3009-style authorizations
  • The signed authorization is verified against the forwarder’s EIP-712 domain, while authorization.to remains the facilitator

​
MegaETH Note

New MegaETH integrations should use the Permit2 flow:
  • Keep payTo set to the facilitator 0x8E7769D440b3460b92159Dd9C6D17302b036e2d6
  • Set paymentRequirements.asset to the ERC-20 token address the buyer will pay with. USDm is 0xFAfDdbb3FC7688494971a79cc65DCa3EF82079E7
  • Use Permit2 0x000000000022D473030F116dDEE9F6B43aC78BA3 as the approval target
  • Use x402ExactPermit2Proxy 0x402085c248EeA27D92E8b30b2C58ed07f9E20001 as the Permit2 spender
The USDm forwarder 0x2c2d8EF0664432BA243deF0b8f60aF7aB43a60B4 is deprecated and should be used only for legacy EIP-3009 compatibility.

​
Testnet

NetworkChain IDUSDCFacilitator
base-sepolia845320x036CbD53842c5426634e7929541eC2318f3dCF7e0x8e633dBf31adCc7D41BE3e95B7c8DD3526B5235A
fluent-testnet209940xa5544e6DDe3d8927Bf3bD9556e84f49067E36bAf0xB3Ac1B7871942bCdCD0bD6C65765272bBE70B8Da
optimism-sepolia111554200x5fd84259d66Cd46123540766Be93DFE6D43130D70x8e633dBf31adCc7D41BE3e95B7c8DD3526B5235A
Fluent testnet currently uses a mock USDC deployment, including function mint(to, amount) to receive test USDC.

​
Network Monitoring

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