The pit
Four contracts. What each one is for.
This page explains the mechanism and quotes no figures, on purpose. The supply, the split, the fee at the door and the cut on swaps are constants in verified source. That is where they bind, and where they cannot be quietly rewritten or rounded for a screenshot.
Degenforget
the launchpadTakes the flat fee at the door and forwards it in the same transaction, mints the token, splits the supply, opens the pool, drops the pool's share and writes the lapse down. One transaction, four contracts, nothing left half-done: anything that can be refused is refused before the token exists.
Blackout
the swap feeA blackout is the part of the night nobody can account for afterwards. This one takes its cut of everything paid into a pool, in either direction — buy with ETH and the cut is ETH, sell the token back and it is the token. All of it goes to that pool's supply wallet. One pool, one payee, written once and never rewritten.
Oubliette
the holeA cell with a hole in the ceiling and no door; the word is French for the place you are forgotten in. The pool's share drops in once, and there is no function in the file that gives any back — no withdraw, no collect, no owner, no pause, no upgrade. Search it for a negative liquidity delta. There is not one.
ForgetToken
the tokenFixed supply, minted once, split between exactly two addresses in its own constructor. No mint, no owner, no pause, no blacklist. Both mints are logs in the launch transaction, so who got what is a receipt rather than a claim.
The depth gauge
Every lapse opens across a price range, and the pool starts at the cheap end of it so the first buy fills immediately. The gauge beside each entry is how far the price has come down that range: empty means nobody has bought, sunk to the bottom means the pool has worked through the whole of it. It is a shape, not a quote — the price sits beside it, and both ends of the range are in the contract.
A pool with no price is a pool nobody has bought from. It holds no ETH yet, which is not a fault: the whole position is still token until somebody trades.
Two fees that cannot reach each other
The launchpad earns once, at the door, in ETH, from whoever signs — and it never holds that money: it is forwarded inside the same transaction, and a recipient that cannot accept ETH fails the launch rather than stranding the fee. The token's supply wallet earns from trading, for as long as anybody trades.
Neither can reach the other. Where the door fee goes is an immutable in the launchpad and appears nowhere in the hook, and a pool's payee is written once by the launchpad and cannot be rewritten. The hook takes no beneficiary argument at all, so there is no address in it for a deployment to get wrong.
What you are trusting, and what you are not
- Not trusting: that the pool's liquidity stays put. There is no function to move it. That is a property of the file, not a promise from anybody.
- Not trusting: that the rate stays the rate. A pool's hook is part of its key, so it is fixed when the pool opens. A different hook is a different pool.
- Trusting: that whoever holds a supply wallet may sell. That share is liquid from the first block, and nothing here restrains it.
- Trusting: that the code does what it reads like. It is not audited. Read it, or have somebody read it.
Where to check all of this
The three addresses at the foot of this page, on the explorer, with their source published under MIT. Every figure this page refuses to quote is a constant there, and a launched token's own constructor arguments can be rebuilt from the chain alone.