Treasury distribution
8,685 POTATCHI from the project’s original treasury to each wallet on a published list, sent directly by a contract.
Distribution
Checking…
Reading the distribution…
—of — transfers sent A transfer counts as sent once the contract’s record of it is in a block 30 blocks deep on Robinhood Chain. Nothing else moves this number: not the schedule, not a transaction that is still pending.
- Total allocation
- —
- Confirmed funding POTATCHI the original treasury moved into the distribution contract, counted from the contract’s own funding records once they are confirmed. Funding moves tokens into the contract; it pays nobody.
- —
- Tokens distributed
- —
- Remaining allocation
- —
- Transfers start
- All unlocked by
- Unlocked now The contract lets transfers out gradually: at any moment at most this many recipients can have received theirs in total. Unlocked isn’t sent; a transfer counts only once its record is confirmed on chain.
- —
- Pace
- —
- Checking the contract’s books…
- Checking the published list…
- Checking the burn before the start…
- Checking the sending program…
Is a wallet on the list?
Paste an address to check it against the published list. The check runs in your browser: the list (about 600 KB) is downloaded once and the address isn’t sent anywhere.
The result shows here.
Check it yourself
Every figure on this page comes from the distribution contract’s own records on Robinhood Chain, and each record links to Blockscout, the chain’s explorer.
Contract
Not deployed yet.
Funding
—
Latest transfers
- —
All transfer transactions (0)
Recipient list
Not published yet.
Snapshot
—
Data
—
Token
0xfad17d7cc41d9c9ca4a459da798a4446dd217974
Blockscout (opens in a new tab)
How to verify it yourself
- The list. Download the list file and compute its SHA-256 (on a Mac or Linux:
shasum -a 256 manifest.json). It must equal the contract’smanifestHash, shown above, so the file you see is the one the contract committed to. This page checks the same thing before the lookup uses the file. - The recipients. The contract stores the list’s Merkle root (
merkleRoot). Every transfer carries a proof against it, so the contract can send only to an address on that list, only its 8,685 POTATCHI, and only once. Nobody can add an address or change an amount, and after the first transfer nobody can cancel the distribution or move the funded tokens anywhere else. - The transfers. Each transfer is a
Distributedrecord in a transaction on Blockscout. The sent count on this page comes only from those records, once they are 30 blocks deep. - The schedule. On the contract’s Blockscout page,
unlockedCount(t)gives the most recipients that can have received theirs by timet, andstats()gives the totals: funded, distributed, recipients sent to.
How the list was made
From public on-chain data only: the largest liquid balances on Robinhood Chain at a fixed snapshot block (84,790,909, on 10 October 2026 at 06:33 UTC). The exact rules are in the list file’s method block and in the docs.
The largest wallets on the chain
A wallet’s liquid balance is its ETH and WETH, valued at the explorer’s ETH/USD rate at the snapshot, plus its USDG. The 5,000 wallets with the highest liquid balance, of those that qualify, are on the list. The balances come from RobinScan’s top 10,000 accounts by ETH and Blockscout’s WETH and USDG holder lists, read around the snapshot block. A wallet outside RobinScan’s top 10,000 by ETH (below about 1.64 ETH) is counted by its WETH and USDG only.
Wallets only
Ordinary wallets, delegated wallets (EIP-7702) and known smart-wallet contracts (such as Safe, Kernel or Coinbase Smart Wallet) can be on the list. Every other contract is left out: pools, routers, bridges, vaults and token contracts.
Who is never on the list
The project’s own wallets and contracts and burn addresses; accounts the explorers label (exchanges, bridges, protocols, market makers and other known services) or flag as scams; accounts with more than 200,000 transactions (sequencers, relayers, bots) or fewer than 3; and accounts holding more than $1M with fewer than 20 transactions, which look like custody rather than a person’s wallet.
Everyone gets the same
Every recipient gets exactly 8,685 POTATCHI, whatever their rank or route. The rank only decides who is on the list when more wallets qualify than there are places; ties are broken by a hash of the snapshot block and the address, never by address order.
Good to know
- Burn before the start. Before the first transfer, the project’s original treasury burned 20,000,456.59 POTATCHI through the distribution contract (20,000,000 plus the 456.59 left after 5,000 equal allocations, so it ended empty); the contract refuses every transfer until that burn is done. The burn is final and shows in the check above and on the Burns page.
- Direct transfer. The contract sends each recipient’s 8,685 POTATCHI straight to their address. There is nothing to claim.
- Never connect a wallet for it. No step of this distribution needs a wallet connection, a signature or a payment. Anyone who asks you for one, in a message, a post or on a website, isn’t us.
- Wallet apps. A confirmed transfer doesn’t always show up by itself in every wallet app; some need POTATCHI added once, by the token address above, on Robinhood Chain. The transaction on Blockscout is the record.
- Holder counts. While transfers go out, holder counts on this site and on third-party trackers rise because of them. That rise is the distribution, not organic growth.
- Not an offer. The distribution isn’t an offer or a sale, and it isn’t a reward for buying or holding POTATCHI: the list is chosen by ETH, WETH and USDG balances on Robinhood Chain.
Nothing here is financial advice, and nothing is promised. This project is not affiliated with, endorsed by, or officially connected with Robinhood Markets, Inc.