WMTX Base Airdrop

Supply across chains

What it adds up to

Pipeline — click a stage to open those wallets

Wallets ↻ reload

Batches

Batch close

Quarantine queue

Wallets the categorizer could not clear automatically (contracts, EIP-7702 delegations, Base address already occupied…). Every release or exclusion needs a reason and is audit-logged.

Exclusions — what we are NOT minting, and why

Post-hack activity

What every snapshot wallet did with its WMTX after the pin block (26,016,081, the last block before the first unauthorised mint). The airdrop mints each wallet its snapshot balance regardless of what happened afterwards, so this tab is the review list, not a rule: it shows where the snapshot amount and today's reality differ. Generated on the server by migration-activity.js, which scans from the pin block to the chain head at the time it runs; re-run it before every mainnet wave.

Clean = no WMTX movement since the pin, mint at full value. Received only = tokens came in but the snapshot amount never left, still safe. Moved funds = the wallet sent WMTX after the pin (sold, bridged, or transferred): listed below with a verdict. Post-hack acquirers = wallets not in the snapshot that bought or received WMTX after the hack; they get nothing from the migration and are the communications exposure.

Snapshot wallets that moved WMTX after the pin

One row per non-team snapshot wallet that sent WMTX after the pin block. Review is what the pipeline will do with it today: eligible, full mint means nothing has been done and the wallet gets its whole snapshot balance on Base; held means it is quarantined or excluded; double-pay risk means it also has a stuck bridge message that could deliver the same tokens twice, and it is not held; minted means it is already in a batch or on Base. Moved out is the total sent since the pin, received the total that came in, balance now the Ethereum balance when the report ran. Click an address to open the wallet and hold or exclude it.

Largest post-hack acquirers (not in the snapshot)

Wallets with no snapshot balance that hold WMTX bought or received after the hack, by net amount held when the report ran. They are not part of the migration. Listed for communications and exchange screening only; the full set is in the report on the server.

Exchange deposit screening

Deposit exports supplied by exchanges, screened by sender against the attacker roots, the DEX venues that received attacker tokens, the time-aware taint trace and the pre-hack snapshot. Generated on the server with exchange-deposits.js <file> --exchange <name>; read-only — nothing here changes wallet state.

Deposits

Exchange-supplied addresses

Audit trail

Hash-chained, append-only. Genesis anchors to the artifact Merkle root; audit.js re-verifies the chain.