tadpools$TADPOOL / ETHRobinhood Chain · not launched yetAwaiting first feed

Uniswap v4 · 0.25% pool fee · paired against ETH

Everyone owns a tad of a pool.

40% of the ETH side of every swap against $TADPOOL goes back to the tadpoles holding it, split by size, every 7 minutes. The rest never leaves. The bigger your tadpole, the more of each feed you take.

Fed to tadpoles since genesis

ETH

0.000000 ETH fed to tadpoles since genesis

Next feed

--:--

Est. next feed

no history yet

Tadpoles fed

0

at the last snapshot

Epoch

root 0x0000…0000

No epoch logs found. The keeper hasn't written to DATA_DIR yet — every panel below is live and fills in on the first distribution.

The pond

bigger tadpole · bigger slice

Still water

The pond is ranked from the latest epoch's allocations. The first tadpole appears with the first distribution.

Your tadpole

Connect, or paste any address, to see the tadpole it owns.

Every holder is a tadpole in the same pond, and the bigger the tadpole the more of each feed it takes. Paste an address to see what it has earned, or connect the wallet holding the token to claim.

The current

immutable · on-chain

Every swap pays a 0.25% fee to the pool, and it arrives in two currencies at once — ETH on one side, $TADPOOL on the other. The pond above is fed by 40% of the ETH side. Everything else — the other 60% of the ETH and every last unit of the $TADPOOL side — is forced straight back into the liquidity it came from, and there is no function anywhere that can take it out again. The water only ever gets deeper.

A closed circuit of water. A swap against $TADPOOL pays a 0.25% fee to the pool, in two currencies: an ETH side and a $TADPOOL side. A splitter divides them on fixed on-chain proportions. 40% of the ETH side leaves the circuit down a narrow tap to the tadpoles, who are fed pro rata by size every 7 min. The remaining 60% of the ETH side plus 100% of the $TADPOOL side returns along a channel three times as wide, through a one-way sluice, into the same liquidity position it came from — a deeper pond, which slips less, which gets traded more, which pays more fees. The splitter holds the position and has no function that transfers it out, so the compounded half can never be withdrawn and the water level only ever rises.THE PONDETH / $TADPOOL, ON UNISWAP V4HELD BY THE SPLITTER, PERMANENTLYNO FUNCTION TRANSFERS IT OUTA DEEPER POND SLIPS LESS,SO IT GETS TRADED MORE.ANY SWAP0.25%POOL FEE · BOTH SIDESTHE SPLITFIXED BPS · NO ADMIN60% OF THE ETH SIDE + 100% OF THE $TADPOOL SIDEFORCE-COMPOUNDED INTO THE SAME POSITIONONE WAYENFORCED ON-CHAIN — THE COMPOUNDINGRECIPIENT'S CLAIM REVERTS UNLESS THESAME TRANSACTION DEEPENS THIS POND.40% OF THE ETH SIDETHE ONLY EXITTADPOLESPRO RATA · EVERY 7 MIN
Deeper pondless slippagemore tradesmore feesboth again, forever

How the pond works

  1. Continuous

    The pond earns

    Every swap against $TADPOOL pays 0.25% to the liquidity position, and it lands in two currencies at once — ETH on one side, $TADPOOL on the other. Nothing about this is discretionary; it is the pool's fee tier.

  2. Same transaction

    The current divides

    40% of the ETH side is assigned to this launch and ends up feeding the pond. The other 60%, plus every unit of the $TADPOOL side, goes to a recipient that will only accept a claim in a transaction that also adds that value back as liquidity to the very position it came from. The proportions are basis points fixed at launch, with no admin able to move them.

    ETH side40% fed out60% compounded
    $TADPOOL side100% compounded
  3. Never reverses

    The compounded half is stuck there

    The splitter holds the LP position and has no code path that transfers it anywhere. Not the creator, not the protocol, not us. Liquidity added by compounding is liquidity nobody can withdraw — so the water this token trades against only ever gets deeper.

  4. Every 7 min

    Every tadpole gets measured

    The keeper snapshots holder balances at a block, works out each address's pro-rata slice, and posts a merkle root on-chain. Bigger tadpole, bigger slice — it is the same arithmetic for everybody. The snapshot excludes the pool itself, otherwise most of every feed would go straight back into liquidity.

  5. Whenever you like

    You claim

    Roots are cumulative, so each one carries your whole entitlement since genesis. Ignore this for a month and you still collect everything owed in a single transaction against the newest root.

Epoch log

awaiting first feed

Nothing has been fed yet

No epochs have been recorded. The keeper writes one file per distribution; as soon as the first lands it appears here.