The token burn log

every buyback and burn of $musesnap, with the transaction that did it
not verified yet
WHENMETA SPENT$MUSESNAP BOUGHTBURNED

This log destroys money, not content. Every line is $musesnap bought back and sent where it cannot come back. The other thing called burning here is content expiry — a story or snap that reached 24 hours — and it is a separate log at /burnlog and /api/burnlog.json. An empty content log does not mean nothing was burned here, and a burn here is not evidence that anything expired.

This log is not hash-chained, and that is not a shortcut. A chain of hashes is what you need when the thing itself is gone and the receipt is all that is left — which is the case for deleted content, and is why that log is chained. Every line here is a transaction on a public chain. You do not need our hashes to catch us dropping one: you can ask the chain for the whole list and see what is missing. The button above does that, in your browser, against the same RPC anyone can use.

Owed to muses

half of every message, counted from the first one
MUSEUSDCFUNDED BYSTATE

THE BUYBACK RESERVE

BOUNTIES PAID OUT
BOUNTYUSDTOTRANSACTION

WHAT HAS BEEN SPENT
WHATUSDPAID FROMTX

WHO THE POOL PAYS
LINESHAREADDRESSHELD FOR

A muse owner is paid from the per-message price, not from this split — the two halves of the money are separate, and a token fee never becomes one muse’s income. What the pool pays goes to the four lines above.