Tallystick, an Ethereum token: its trades queue up as obligations, discharged in opening order by retiring the token’s own supply.
Tallystick (TALL) · Uniswap v4 · Ethereum · trades price in ETH
Four named parts do everything. There is nothing else in the mechanism.
Every trade — a buy same as a sell — contributes two percent: the Paring. It is the one and only charge, and the contract can spend it on one thing only: working the queue. The mechanism is funded by use alone.
With the same trade, a Notch opens: its TALL size and the Ethereum block that saw it, written to the Scoreline’s tail — an append-only run the contract keeps itself. No trade is passed over, and none is rewritten.
Anyone may call a Tallage whenever they like; there is no permission to give or withhold. The gathered Paring buys TALL from the market, retiring it in the same motion; the oldest live Notch is discharged before any younger one — the queue cannot be worked out of order.
TALL retired by a Tallage becomes Char: gone from supply for good — never sold, never handed back, and no function mints a replacement. The launch figure of 900,000 TALL is therefore the permanent ceiling. The view charred() reads the running total.
Any Ethereum wallet keeps TALL natively, and the Uniswap v4 pool prices it in ETH — the 2% Paring shown inside each trade, never as a separate charge.
A Tallage asks no permission. Call one: gathered Paring buys TALL from the market, retiring it immediately and marking the oldest live Notch first. tallage is a public call.
scoreline(), cuttings(n) and charred() are public views, and each trade and Tallage emits an event. Anyone can read the whole state on an Ethereum explorer.
Two things: it pays the 2% Paring into the mechanism, and a Notch opens on the Scoreline carrying that trade’s TALL size and opening block.
No. A Tallage marks the oldest live Notch before any younger one, and the contract gives no account a way to alter that.
No. The Paring, the working order, the supply — the Standing Rules, written without setters; nobody can adjust them.
It becomes Char: out of supply for good. Char is not sold and not handed back, and charred() keeps the running count.
None at all. No function anywhere lets the deployer touch balances, trading, or retired units.
On an Ethereum explorer: scoreline() for the queue and the waiting Paring, cuttings(n) for any single Notch, charred() for the retired total. The handbook walks each read.
Issuance, the Paring, the Scoreline, the Tallage, Char and the Standing Rules — set down once, in full, so a careful reader can hold the contract up against them.
Every Notch waits its turn. Every Tallage takes the oldest one standing. And the figure it started at — 900,000 TALL — only ever gets smaller from there.