ozem
abstract: The layers, the chain of custody, and the checks. A slice of every eruption is bought into an account with no exit, each purchase writes a hashed layer, and this page recomputes the whole chain in your browser as you read it.
note: all four verifications run on load and rerun each minute.
the absence
A slice of every eruption is used to buy the token and deposit it into an account for which the program defines no withdrawal. This is bedrock. It holds across layers, and both figures can only rise. Most floors are promises, and promises have signers. Bedrock is an absence: there is nothing to trust, because there is nothing anyone can do.
the layer chain
Each compaction writes a layer record: epoch, amount locked, and a hash equal to sha256 of the previous hash, the epoch, and the amount. The first layer uses thirty two zero bytes as its previous hash. The layers form a single chain of custody from genesis to now; alter any historical layer and every later hash disagrees with what the chain stores. The construction is explained plainly in the docs, and it is checked live, below, on every load.
the layers
table 5. the layers of bedrock.
| epoch | amount locked | slot | stored hash | chained |
|---|---|---|---|---|
| Layers appear with the first compaction. | ||||
four checks, performed as you read
This page performs its checks in your browser. First, the layer chain: every hash is recomputed from raw bytes and compared, and the result is printed below. Second, the split: the three outputs of the most recent eruption are summed from its transaction logs and compared to the drained total. Third, the accounting identity: the sum of all unwithdrawn position amounts must equal the stack vault's token balance exactly. Fourth, monotonicity: the current locked total must equal the sum of all layer amounts.
why a floor with no door
Why lock value where no one can reach it? Because the machine's credibility is measured in what it has permanently refused to give back. Bedrock converts a fraction of every eruption into history, and history, unlike a balance, cannot be spent. The byte layout of a layer record is printed in the docs, and the two rpc calls that fetch the whole chain are printed beside it.
disclosure
This site reads public chain state, Birdeye, and public price data, and holds nothing. It is informational and is not financial advice or an invitation to acquire any asset. The program's flow paths carry no admin key. Burial, withdrawal, and venting are user signed actions with network fees, and users retain full responsibility for them. Where this document and the chain disagree, the chain is correct.