invariants
what an invariant is
An invariant is a relation that should hold after every replayed event. The browser checks each line on every poll. A failed line prints its compared values in the error accent.
Replaying twice gives the same codeword hash guards determinism. The same ordered transactions must produce the same bytes. A mismatch means the replay depends on something outside its inputs.
The sum of hits equals flips guards event counting. Every ordinary transfer increments one symbol hit and one flip. Their totals must remain equal.
invariants reading: —
how they are checked
Credit spent plus credit left equals total sent to the incinerator and burns guards burn accounting. Each repair spends one fixed cost. All remaining burned value stays as credit.
Sealed never goes from true to false guards permanence. The replay only changes the flag from false to true. No later event clears it.
Errors stay at or below 16 unless sealed guards the correction boundary. A recoverable word cannot report more than 16 positions. Failure beyond that point records 17 and requires sealing.
invariants reading: —
what a failure means
The decoder self-test passes line guards the local Reed–Solomon implementation. It encodes a fixed vector and corrects 16 altered symbols. The result must recover the original bytes.
The holder balance sum equals total supply minus burned guards token accounting. the incinerator and burns are excluded from holders. Their received value is removed from the holder side of the equation.
A failing relation means the displayed reconstruction is internally inconsistent. It does not change public transactions. It marks the reader result as untrusted.
invariants reading: —
what is out of reach
The reader does not control transfers, token supply, or slot production. It reads the token log from the configured first slot. Missing history leaves replay values unavailable.
Pool labels come only from configured wallets. They do not change balance or damage calculations. the incinerator and burns never appear as holders.
The token has no solomon contract or hook. These rules run in the reader. Anyone replaying the same ordered transactions can check the same result.
invariants reading: —