# Supported Chains ## Payments The payment proxy smart contracts enable the various payment types. The most widely deployed payment proxy is the ERC20FeeProxy. The most frequently used payment proxy is the ERC20ConversionProxy. {% hint style="info" %} For an explanation of what each smart contract does, see [Smart Contracts Overview](/advanced/protocol-overview/contracts.md) {% endhint %} {% hint style="info" %} Make sure to scroll horizontally to see all the payment proxy types! :wink: {% endhint %}

Chain	Chain Name	Chain ID	ERC20FeeProxy	EthereumFeeProxy	Erc20ConversionProxy	EthConversionProxy	BatchConversionPayments	ERC20SwapToPay	Erc20SwapToConversion	ERC20TransferableReceivable	ERC20EscrowToPay	ERC20Proxy	EthereumProxy	BatchPayments (deprecated)
Ethereum Mainnet	mainnet	1	true	true	true	true	true	true	true	true	true	true	true	true
Sepolia	sepolia	11155111	true	true	true	true	true	true	true	false	true	true	true	false
Goerli (deprecated)	goerli	5	true	true	true	true	true	true	true	true	true	false	true	true
Optimism	optimism	10	true	true	true	true	true	true	true	false	true	false	true	true
Arbitrum One	arbitrum-one	42161	true	true	true	true	true	true	false	false	false	false	true	true
Base	base	8453	true	true	true	true	true	true	true	false	false	true	true	false
zkSync Era	zksyncera	324	true	true	false	false	true	false	false	false	false	false	false	false
zkSync Goerli (deprecated)	zksynceratestnet	280	true	true	false	false	true	false	false	false	false	false	false	false
Gnosis	xdai	100	true	true	true	false	true	true	true	false	false	false	true	true
Polygon	matic	137	true	true	true	true	true	true	true	true	true	false	true	true
Mumbai	mumbai	80001	true	false	false	false	false	false	false	false	false	false	false	false
BSC	bsc	56	true	true	true	true	true	true	false	false	false	false	true	true
BSC Testnet	bsctest	97	true	false	true	false	false	false	false	false	false	false	false	false
Celo	celo	42220	true	true	true	true	true	true	false	false	false	false	true	true
Alfajores	alfajores	44787	true	false	false	false	false	false	false	false	false	false	false	false
Fantom	fantom	250	true	true	true	true	true	true	false	false	false	false	true	true
Tombchain	tombchain	6969	true	true	false	false	false	false	false	false	false	false	false	false
Core	core	1116	true	true	false	false	false	false	false	false	false	true	true	false
Avalanche	avalanche	43114	true	true	true	true	true	true	false	false	false	false	true	true
Fuse	fuse	122	true	true	false	false	true	true	false	false	true	false	true	true
Moonbeam	moonbeam	1284	true	true	true	true	true	true	true	false	true	false	true	false
Ronin	ronin	2020	true	true	false	false	false	false	false	false	false	false	false	false
Mantle	mantle	5000	true	true	false	false	false	false	false	false	false	true	true	false
Mantle Testnet	mantle-testnet	5001	true	true	false	false	false	false	false	false	false	true	true	false
NEAR	N/A	N/A	true	true	false	true	false	false	false	false	false	false	false	false
NEAR Testnet	N/A	N/A	true	false	false	false	false	false	false	false	false	false	false	false

## Storage These smart contracts facilitate storing IPFS content addressable hashes (CIDs) on-chain.

Chain	Chain ID	RequestHashStorage	RequestOpenHashSubmitter
Gnosis	100	true	true
Sepolia	11155111	true	true
Ethereum Mainnet (deprecated)	1	true	true
Goerli (deprecated)	5	true	true

## REQ Token and Burn Mechanism The REQ Token is on Ethereum Mainnet. The burn contracts facilitate locking xDAI on Gnosis, bridging xDAI to Ethereum, swapping xDAI for REQ, and burning the REQ.

Chain	Chain ID	lockForREQBurn	DaiBasedREQBurner	RequestToken
Ethereum Mainnet	1	false	true	true
Gnosis	100	true	false	false

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://legacy.docs.request.network/general/supported-chains.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.