Skip to main content

Contract addresses

The canonical Fantums Reborn contracts deploy to Sonic mainnet (chain ID 146) and Sonic testnet (chain ID and address space published at launch). All addresses below are TBD until deploy day — verify against the live repo at launch before sending funds.

Addresses are published in three places when they're final:

  1. This page
  2. script/deploy/deployments.json in the public repo
  3. On the verified contract page on sonicscan.org

If those three disagree, the on-chain bytecode wins.

Reborn contracts (Sonic mainnet)

ContractAddressPurpose
Fantums.solTBD at launchERC-721 with on-chain combat stats, traits, OG flag, legacyDna
SFUMS.solTBD at launchUtility ERC-20, fixed supply 100,000
SFUMSTimelock.solTBD at launchTeam vesting lock for sFUM allocation
MintDrop.solTBD at launchPublic mint, USDC + S accepted, tier-priced
LegacyClaim.solTBD at launchOG reserved-window mint, Merkle-gated
Duel.solTBD at launchPvP combat with signed-result EIP-712
DuelRouter.solTBD at launchMatchmaking + queue management
Graveyard.solTBD at launchPermadeath escrow + paid revival
Marketplace.solTBD at launchIn-house secondary marketplace
ArenaOptOut.solTBD at launchVanity-mode flag
FeeMSplitter.solTBD at launchSonic FeeM rebate distribution
FantumRenderer.solTBD at launchOn-chain SVG renderer library

Reborn contracts (Sonic testnet)

ContractAddressStatus
All Reborn contractsTBD at testnet deployA full mirror of mainnet deploys to testnet for integration testing

The testnet deployment is typically two weeks ahead of mainnet so external integrators can integrate against real addresses before launch.

Canonical Sonic addresses we depend on

These are not Reborn contracts — they're protocol-level Sonic infrastructure that our contracts call into:

WhatAddress
Wrapped S (wS)Sonic canonical address — published in frontend/.env.example
Native USDC (CCTP V2)Sonic canonical address — published in frontend/.env.example
Bridged USDTSonic canonical address — published in frontend/.env.example
WETHSonic canonical address — published in frontend/.env.example
Multicall3Same canonical address as every EVM chain (0xcA11bde05977b3631167028862bE2a173976CA11)
Sonic Gateway bridgeSonic canonical address
Sonic FeeM registryTBD at launch (FeeM registration is a deploy-day action)
Chainlink S/USD oracleTBD at launch
Primary DEXTBD at launch (SwapX / Shadow / Beethoven / Equalizer — chosen on TVL + LP-burn UX)

The canonical addresses are committed in frontend/.env.example and re-derived programmatically at build time — they're not duplicated by hand in multiple files.

Original FUM contracts (Fantom Opera — read-only reference)

These are the original contracts on Fantom Opera (chain 250). They are reference only. The Reborn contracts do not call them at runtime. Fantom Opera shuts down on 2026-06-30.

ContractAddressPurpose
FUM (original ERC-721)0x0C600D41b9C7656e60C0bf76D79B1532b4770D0CThe original Fantums collection (10,860 supply)
FOO (original ERC-20)0xfbc3c04845162f067a0b6f8934383e63899c3524Original duel currency, 100M supply
sFOO (original staking)0x57c47A330022edAe0a2eC8d6546689508e1278e8Original FOO staking token
RIP token0x659D813beB17435acF822CdD80DB0c7090755771Added Sept 2021
Original deployer EOA0x60795390f5393e5641fE8F04099632A884168719Still holds 2 FUM as of snapshot
SushiSwap FOO/FTM LP0xc9a3ad55ef7b859e0c5fdb81e4f4b6a709d758fdOriginal liquidity pool

These addresses are in the project memory and the historical snapshot. They are not callable from the Reborn deployment.

Snapshot artifacts

The frozen snapshot of the original FUM collection lives at data/fantum-snapshot/:

FileContents
owners.jsontokenId → owner address, all 10,860
hashes.jsontokenId → on-chain DNA hash, all 10,860
eligible-holders.jsonEOA-filtered holder set at snapshot block
merkle/tree.jsonMerkle tree for legacy claim
merkle/proofs.jsonPer-address proofs

Snapshot pin block: 121,669,337 on Fantom Opera. Frozen, never re-derived.

Verifying a contract address

Three things to check before sending value:

  1. The address appears in script/deploy/deployments.json in the public repo on the right network
  2. The address has verified bytecode on sonicscan.org matching the source in the public repo
  3. The address signature on Twitter and Discord match — we cross-post canonical addresses on launch day

If any of those three disagree, do not send funds. Wait for confirmation from the founder wallet.

See also


Last updated: 2026-05-21