Every claim $remilio has ever paid is on this page. The vault balance is read live off solana. The arithmetic is checked in front of you. Nothing here is a screenshot and nothing here is our word for it.
If the vault ever held less than the ledger says it should, the vault would be lying and this box would go red. It is computed fresh every time you load this page.
| reading the vault... | ... |
vault wallet
The vault has no whitelist.
There is no snapshot we can edit, no list of winners, no admin function that pays a friend. When a claim arrives the vault asks ethereum one question, live, and pays only what the answer allows: does this address own that baby right now?
The answer comes from ownerOf on the Redacted Remilio Babies contract, read at the moment of the claim. Not from a file. Not from a database we maintain. If the chain does not say you hold the baby, nothing moves. We cannot add you, we cannot remove you, and we cannot pay ourselves.
The ledger is keyed by token id, never by wallet. The instant baby 1337 claims, the id 1337 is spent forever. Sell it afterwards and the buyer gets nothing. Buy a claimed baby and you get nothing. Move it between your own wallets and still nothing. The id is the unit, you are not. Check any id in the table below before you buy.
The id is written spent before a single token moves. Most airdrops send first and record after, which is exactly how double claims happen when something crashes or two requests race. Ours commits first, so our worst possible failure is a late payment we push through by hand. Being paid twice is not a bug we patched, it is a state the code cannot reach.
Three ways to claim, one queue. Paste a signature, connect a wallet, or send a 0 ETH transaction and never load this site. All three funnel into a single file queue, because two of them firing on the same baby at the same instant is the only way the arithmetic below could ever break.
The on chain path waits for ethereum finality and makes two independent RPC providers agree on the sender, the calldata and the block before the vault moves. A finalized block cannot reorg, so a paid claim can never be unwound underneath us, and one lying provider cannot invent a transaction from a wallet it does not control.
It refuses to pay an address that cannot receive. Solana addresses carry no checksum, so a single wrong character is normally a permanent burn with the claim marked used. The vault rejects off curve keys and refuses token accounts pasted where a wallet address belongs. It would rather bounce your claim than fire your tokens into a hole.
mint authority null. freeze authority null. Supply cannot grow, your tokens cannot be frozen, and the pool cannot be refilled or diluted. It only goes down, one baby at a time, until 9,995 have spoken.
Every number on this page comes from public chain data. Here is how to read it without us in the middle.
1. The vault balance, straight from solana. No API of ours involved.
2. The mint has no authorities. Look for mintAuthority null and freezeAuthority null.
3. Any claim in the table, on solscan. Click any payout signature below and watch the tokens land in that exact wallet.
4. Any claimer really held the baby. Read ownerOf yourself on etherscan for the token id and compare it to the eth address in the table.
5. The whole ledger as raw json, if you would rather audit it in your own script than trust our table.
One row per remilio. Newest first. This is the entire distribution, nothing withheld.
| loading the ledger... |