/dɪˈbeɪs/ verb · debased; debasing; debases
From de- “down” + base “low, of little worth” — as in a base metal, the opposite of a noble one. The word has spent six hundred years meaning to make something worse while pretending otherwise. Four of its five senses describe things this token cannot do. The fifth is the oldest, and it is the only instruction the contract takes.
Senses — four struck, one standing
To reduce the intrinsic value of a coin by alloying it with base metal.
Nothing is alloyed in. There is no mint function, no admin key that can call one, and no upgrade path to add one later. The supply was fixed at 69 billion in the constructor and the only arithmetic the contract will do to it is subtraction.
See The ledger
To lower in quality, value, or character.
Quality here is frozen, not managed. The rate, the split it divides into and the burn address were written into the launch, and there is no function that can edit any of them — the hook has no tax setter at all, and the call that wrote them reverts if it is ever made twice for the same pool. The locker has no withdraw function either, so the floor is not a policy we maintain. One platform-level lever does exist; it is named in full under Verify rather than left for you to find.
See The toll
To lower in status, dignity, or esteem; to degrade.
It has no authority over you to abuse. No treasury, no multisig, no governance token, no vote that can reach your balance. Nobody can be demoted by a contract that cannot be persuaded.
See Verify
To adulterate; to mix with something inferior.
Two pools, one price. A <redacted> pool and an ETH pool, taxed identically, with the ETH side quoted off that one at launch so the two open at one valuation instead of two. Nothing is diluted into the mix and there is nothing free to arbitrage.
See The toll
Archaic: to bring down; to lower physically.
This one still applies, and it is the whole design. Every trade feeds a fire that buys DEBASE off the market and destroys it. The supply is brought down, block by block, by the act of trading it — and there is no function anywhere that can raise it again.
Still true · the only sense the contract implements
Supply remaining · none of it burned yet
69,000,000,000
nothing has traded yet, so nothing has burned
and there is no code path that could
set by the first trade; fixed supply, so it is also fully diluted
buy / sell, identical on both pools
| Sink | What it does | Share |
|---|---|---|
| the fire | Spent buying DEBASE off the market and sending it to an address nobody holds the keys to. On a buy, this is the toll turning your own purchase into a smaller supply. | 50% |
| the vault | Paid to the shared <redacted> vault. Bond there and you earn from this token and from every other launch pointed at the same vault. | 25% |
| the creator | Declared on-chain before a single trade, at an address anyone can read. Not a treasury, not a multisig, not a promise. | 25% |
The same split on both pools, frozen into the launch. The creator cannot change it and neither can we: there is no setter for the rate or the split anywhere in the hook, and the call that writes them reverts if it is ever made twice for the same pool.
One platform-level exception exists and is listed with the addresses under Verify, where you can check it yourself rather than take this page’s word for it.
A quarter of every toll goes to a vault the whole platform shares. Bond <redacted> there and you are not betting on this one token staying interesting — you hold a single claim on the fee flow of every launch pointed at the same vault, this one included.
the bonded token, in escrow — it never touches a pool
paying out to bonders over 30 days
+0.1× every week you stay, to a ceiling at week 40
Every sentence on this page is a function you can call. The split, the burn address, the locked positions and the vault's books are all readable without asking anyone — and the claim that matters most, that nobody can make more of it, is the absence of a function rather than the presence of a policy.