The first burn book on this chain. Lock a supply and it cannot move until the clock runs out. Burn one and it is gone. A lock can be turned into a burn at any moment, never released early. Every one of them gets a page, written by a contract with no owner, no fee and no way to edit it, including by us.
Connect a wallet, pick a token, choose lock or burn. Everything below runs against the registry contract on chain 4663. No backend, no database, no form that we could edit later.
The contract has no owner, no admin, no pause and no upgrade path. Nothing here can be turned off, not by us and not by anyone who buys the token.
Approve the registry, then lock a balance until a timestamp. The tokens sit in the contract and physically cannot move before the clock runs out. The page records the balance that actually arrived, so a fee on transfer token cannot inflate the number.
A lock can be pushed further out, added to, or handed to another wallet. It can never be shortened. At any moment the owner can convert it into a burn, which sends the balance to the dead address and writes a second page for it.
After the unlock time the owner calls withdraw and the page stays in the book, marked closed. Every state it passed through keeps its own entry, so the history reads as a record rather than a current balance.
A trust product that hides its own edges is not a trust product.
There is no admin key, so nobody can move your tokens, and nobody can get them back for you either. If this contract has a bug, what is inside it is stuck forever. That is the trade, and it is why the contract is short enough to read in one sitting.
No firm has audited this. The source is verified on Blockscout, the tests are in the repo, and the maths was checked against the live chain with state overrides before a single wei of gas was spent. Read it yourself before you lock anything that matters.
Fee on transfer tokens are handled by measuring what actually arrived. Rebasing tokens will drift away from their page, so do not put one in. Liquidity on this chain graduates into Uniswap v4, where a position is an ERC-721, and that needs a second code path. It is next, not now.
The book proves that a balance is held by a contract until a date. It cannot tell you anything about the wallet that locked it, what else that wallet holds, or what it does on the day the clock runs out. Read the page, not the intention.
