Skip to main content

How to claim

The OG claim is permissionless and proof-gated. No allowlist form, no Google sheet, no "DM us your wallet". If your address appears in the Merkle tree, you can claim. If it doesn't, you can't. The tree is published in the repo.

Who is eligible

Every address that ever received a Fantum on the prior chain.

This is broader than current holders. If you minted a Fantum in 2021 and sold it the next day, you're eligible. If you bought one on PaintSwap in 2023 and gifted it, you're eligible. If a Fantum was transferred through your wallet on its way to a graveyard, you're eligible.

We captured every Transfer event from the FUM contract between block 15,000,000 and the pinned snapshot block:

Source contract0x0C600D41b9C7656e60C0bf76D79B1532b4770D0C (FUM ERC-721, Fantom Opera)
Scan rangeblock 15,000,000 → 121,669,337
Filters appliedcontracts dropped (where eth_getCode == "0x"), burn addresses dropped, zero address dropped
Per-address slot capmin(uniqueFumEverReceived, 50)
Merkle leafkeccak256(abi.encode(holder, uint16 slots, bytes32[] dnaHashes))
Tree generation scriptscripts/snapshot-fantums/build-merkle.mjs

The pinned snapshot block is the canonical cut-off. Any Fantum movement after block 121,669,337 does not change the eligible set. The chain shuts down on 2026-06-30 — we froze the state ahead of the deadline so the answer would never wobble.

The check page

Before the claim window opens, you can verify eligibility on /og-check:

  • Connect your wallet or paste any EVM address.
  • The page looks up the address in the published proofs.json from the build-merkle script.
  • It shows:
    • Whether you're eligible
    • How many slots you have (1 to 50)
    • The list of inheritable ancestor token IDs
    • The mint discount (50% of the public tier price)
    • The full downstream perk list

When the claim window opens, the same page becomes the claim UI. No wallet handoff. No new contracts to approve.

The Merkle proof flow

If you want to claim from a script or your own UI, here's the call shape.

LegacyClaim.legacyMint(
bytes32[] calldata proof,
uint16 slotsAllowed,
bytes32[] calldata dnaHashes,
uint256 ancestorIndex
) external payable
  • proof — Merkle proof for the leaf keccak256(abi.encode(msg.sender, slotsAllowed, dnaHashes))
  • slotsAllowed — must equal min(uniqueFumEverReceived, 50) for msg.sender
  • dnaHashes — the full slate of ancestor FUM hashes, sorted ascending by original tokenId
  • ancestorIndex — which entry in dnaHashes the new Reborn token inherits from

Each call mints one Reborn token. To mint multiple slots you call multiple times, each with a different ancestorIndex. The contract tracks slotsUsed[address] so you can't exceed your cap.

The new Reborn token gets:

  • legacyDna set to dnaHashes[ancestorIndex] — immutable, on-chain, forever
  • isOG[tokenId] = true
  • +5% stat boost applied via _ogBoost
  • Discount applied via setPrice() (default 50% off public tier)

Snapshot block

Source chain : Fantom Opera (chainId 250)
FUM contract : 0x0C600D41b9C7656e60C0bf76D79B1532b4770D0C
Pin block : 121669337

The Merkle root

0xf5966178c7dce036fd934d5be3a38ee4b5161df9795fc847d99333a16c1684d0

This is the tree root committed to the LegacyClaim contract at deployment. If you re-run scripts/snapshot-fantums/build-merkle.mjs against the public snapshot data, you should derive the same root. If you don't, something is wrong with your input.

What if I lost my old wallet

Hard luck. The proof is keyed to the address that received the Fantum. If you've lost the private key, the OG slot for that address is unrecoverable. Any unclaimed slots at the end of the window roll to the public mint.

Burned Fantums and the deployer

  • The 8 burned tokens at 0x...dEAD: their DNA is acknowledged in lore but they don't get an OG slot — the burn address can't sign a transaction. Their hashes may still appear as ancestor options in a special "From the dead" public-mint trait.
  • The original deployer's 2 still-held Fantums at 0x60795390f5393e5641fE8F04099632A884168719: still eligible like any other address. Two slots, same rules.

See also

  • OG perks — what the badge actually unlocks once you've claimed
  • Reserved mint window — when the window opens and what happens to unclaimed slots
  • On-chain art — why the art on your new mint won't disappear like the original did

Last updated: 2026-05-21