Deployed contracts
Mainnet addresses, explorer links, the release manifest, and a read-only connection example.
Understand a launch
Learn the currency choices, launch fee, allocations, and opening policy.
Current availability
The onchain state below was verified at block 21,240,866, on September 17, 2026 at 00:14 UTC. Read the contracts again when preparing an operation; launch controls and token registration can change.
Currency admission and launch availability are separate. The registry owner opens new launches; the current pause applies to FX-pair, single-currency, and dedicated official-FX launches.
Deployment identity
The completed deployment records 23 successful transactions across blocks 21,239,186–21,239,239. The contract reference contains the complete manifest, including runtime code hashes and the release fingerprint.
Deployed execution policy
These settings were read from the deployedFXReleasePolicy contract. That contract has no settings setters.
Reserved funds, remaining spend allowances, current and observed liquidity, execution pauses, and settlement bounds still limit each purchase. These settings do not promise a purchase schedule. Official FX must be registered before a buyback can execute.
The opening surcharge applies to all launch types: an initial 99%, a nominal 500-millisecond half-life, and expiry after five seconds. See the opening window for fee bases and the chain-time calculation.
See fees and FX revenue for the fixed launch economics and 90/10 accounting.
Currency and service availability
The deployed registry has USDC and EURC configured, and the admitted currency pool has a 0.05% native LP fee. Exact identities are listed under currencies and pair. Other currency-pair examples in these docs describe possible extensions. They are not additional enabled markets. The live RPC proxy serves approved JSON-RPC reads. It does not provide the indexed/api/markets service or accept transaction submission. The market-data reference documents that separate service in preparation for hosting.
Verification scope
The deployment record checks transaction receipts, component bindings, ownership, and deployed runtime code. The documentation’s mainnet check independently matched all 15 manifest contract code hashes and read the launch gate, token registration, currency configuration, and release policy. These checks establish the recorded deployment and settings. They are not an independent security audit or a guarantee of favorable market execution.FX website
The official project website.
FX on X
Follow project and app-release updates.