Skip to main content
FX’s V6 revision 6 contracts are deployed on Arc mainnet, chain ID 5042. Use this page to identify the release and connect to its onchain interfaces.
The public app and indexed market API are not hosted yet. At the latest release check, new launches were paused and official FX was not registered. Direct contract reads are available.

Network

See Arc’s network setup for wallet configuration. Arc exposes native USDC at 18-decimal precision and its ERC-20 interface at 6 decimals. They represent the same balance; do not count them as separate assets.

Core contracts

The router is the spending target for the documented trading flow. The quoter simulates execution; it does not hold a spending allowance. Use the matching R6 ABI and check quote and settle before constructing an order.

Revenue and policy

See architecture for each component’s role and production settings for the installed policy.

Currencies and pair

Both quote assets and the EURC/USDC relationship were enabled at the documented snapshot. New launches remain subject to the separate global pause and current admission checks. The registry’s pair ID is:
The admitted external currency pool uses this PoolKey on the PoolManager above. Its fee value is in parts per million: 500 means 0.05%.
The relationship is discovered through the registry. An empty pairs array in the deployment manifest is intentional when registryDiscovery is enabled; it does not mean the registry has no admitted pair.

Read the current state

This example uses viem and makes read-only requests to the public Arc RPC. It does not need a wallet.
A zero protocolToken address means official FX has not been registered. Read the factory again after registration; a token’s name or symbol does not establish official status. The live FX proxy at https://fx.meme/api/rpc accepts approved JSON-RPC read requests. It is a read service, not a signing or transaction-submission endpoint.

Release manifest

All 15 contract code hashes below matched the mainnet bytecode at block 21,240,866. Explorer links identify the contract accounts; source-code verification by an explorer is a separate property. The fingerprint is Keccak-256 of the UTF-8 compact JSON serialization of the release object, with object keys sorted recursively and array order preserved. Pin the expected fingerprint independently of responses that supply market data.
This manifest identifies the deployed contracts and currencies. It does not configure a hosted app or indexed market API.
For the documented snapshot, the release policy’s onchain policyHash() was:
The release fingerprint covers the manifest. The policy hash covers the constructor-selected opening and buyback settings. They identify different data and should not be interchanged.