A launchpad on Robinhood Chain
Degens forget.
The pit doesn't give it back.
One signature mints a token, opens its pool against ETH, and drops the pool's share into a contract that owns no function to hand any back. Forgetting is the feature. What the site refuses to forget is the receipt: every term it runs on is a constant in published, verified source.
The log
The contracts are written and tested. They are not on chain yet. Once they are, every lapse turns up here by itself — this list is read from the launchpad, not from a file somebody remembers to update.
One signature, three consequences
- 01
The supply is minted once and split in the token's own constructor
Two balances come out of it: the oubliette's share for the pool, and a wallet you name. Both are Transfer logs in the same transaction. Nobody has to be believed about who got what.
- 02
The pool opens against native ETH, with the blackout in its key
No WETH, no wrapper, no second token. The LP fee is zero, so the blackout's cut is the whole fee schedule — and a pool's hook is part of its key, so that rate is fixed the moment the pool exists.
- 03
The pool's share goes down the hole
One position, in a contract with no withdraw, no collect, no owner, no pause and no upgrade. Not a timelock. Not a multisig. There is no function in the file to call.
The part nobody should forget
The share that does not go into the pool is minted to a wallet the launcher names, and it is liquid from the first block. Not vested. Not cliffed. Not locked. No contract here restrains it and none of them pretends to — whoever holds that wallet can sell into any bid that appears. That same wallet takes the swap fee.
It is a constant in the launchpad rather than a choice made per token, so it is identical for every entry in the log and there is one number to check instead of one per launch. Degenforget can make sure you knew before you bought. It cannot make anybody hold.