Transaction Failed

An error occurred during transaction execution

Error Details

Loading Exadon migration…

Fetching migration window, allocation stats, and your holdings.

Admin Migration Checklist (Immutable)
  1. Lock Max Supply on EXADON (one-time).
  2. Set EXA per NFT, EXA cap, and Claim Start, then lock config (one-time).
  3. Fund the migration contract with EXA equal to the cap (dev: use “Fund EXA Cap”).
  4. Set Merkle root for each source chain (ETH, SONIC, MATIC, AVAX, POLYGON, BSC, BTC Ordinals).
  5. Announce the migration window (1 year from Claim Start).
  6. After the window ends, call Finalize Migration to sweep leftovers to treasury.
Minted

-

Remaining: -

Migration-only supply tracked on Immutable.

Migration Window
-
—

Claims are available for 1 year from the configured start time.

EXA Allocation
Per NFT: -
Claimed: -
Remaining: -

15% of total EXA supply is reserved for migration claims.

Claim Migration

We auto-load your legacy holdings and proof to make claiming easy. EXA claims still mint the NFT to treasury.

Make sure your proof matches the selected source and index.
Legacy NFTs (Demo)

These are the legacy Exadons used to generate the migration proofs in test environments.

My Exadons
Wallet: -
Admin Controls

Set per-source Merkle roots or finalize the migration after the window ends.

One-time Config
Local Hardhat only. Advances the node clock to the configured claim start.
Status
Treasury: -
EXA Claim Cap: -
Total NFTs Claimed: -
Config Locked: -
Supply Locked: -