Numetal Labs
Doc NML-003 · Rev A · 2026-07-17
Status: live
BOUNTY + PLATES retrodrop.
500M $NUMETAL back to the real holders of the predecessor tokens — snapshotted at the Numetal launch block, paid in 3 onchain batches via Smol Disperse. No signing, no claim. If you held, it just arrives.
loading status…
Retrodrop 01 · BOUNTY + PLATES · Base
numetal.xyz/airdrops
Snapshot · block 46,958,289
Total
500M
Batches
3
Wallets
657
Burn cover
2.36×
Batch tracker§01
| Batch | When | NUMETAL | Status | Tx |
|---|---|---|---|---|
| loading… | ||||
Each batch flips to a green tick with its Basescan tx once sent — verifiable onchain.
Check your allocation§02
No wallet connection — read-only lookup. Try 0xb1fd2b…
Full list — every address, holdings & allocation: raw CSV ↗ · table view ↗
The numbers§03
| Bounty | Plates | |
|---|---|---|
| Eligible holders | 654 | 17 |
| Tokens held | 24.29B | 50.27M |
| $NUMETAL allocated | 499.99M | 14.6K |
| Share of drop | 99.997% | 0.003% |
Snapshot · block 46,958,289 · Jun 6 2026 (Numetal launch).
Methodology§04
- Balances reconstructed from the full onchain transfer history of both tokens up to the launch block — every token accounted for.
- Real people only — 10 infra/bot wallets stripped (AMM pools, Clanker fee locker, MEV bots, CoW, routers); 152 personal smart wallets (Coinbase, Safe, MetaMask) kept.
- Liquidity-adjusted weighting — BOUNTY valued ~71× PLATES, since PLATES had near-zero real float and volume.
- Net-deflationary — 1.18B $NUMETAL already burned vs 500M airdropped (2.36× coverage).
How we enact it§05
Pushed via Smol Disperse on Base — 3 batches (100M · 180M · 220M) from agentbountydev.eth 0x15813f…B93c3. Recipients sign nothing; the tokens simply arrive. Each batch is logged on the fee-engine report tagged retrodrop N/3 — distribution, not a burn, so it never touches the burned total. Every batch is one onchain transaction, linked in the tracker above.