Not a promise. A running network.

A block height is supposed to only ever go up. On this chain it has gone down four times, and we would rather you heard that from us than found it by comparing two screenshots.

Chain 48555 is sealed by a single validator on a single machine with no peers. When that process is killed instead of stopped, it loses the state it was holding in memory, and on restart it repairs itself by rewinding the head back to the last state it can prove. There is no second node to re-sync the missing blocks from, because there is not yet a second node. Every occurrence:

This table is read from the published ledger when the page loads. The figures printed here without the script are what that ledger held on 2026-08-08.

Highest block this machine has ever observed: 106,191 as of 2026-08-08. Rewinds recorded: 4. If the current block above is lower than the highest observed, that is a rewind in progress of being re-sealed.

What this does not touch. No gift has ever been recorded on chain 48555. Every recorded gift is an ERC-20 transfer on Ethereum mainnet, a chain Bremo does not operate and cannot rewind, and each one is linked to its Etherscan transaction on the transparency page. The identity of this chain is also unchanged by a rewind: genesis hash 0x9e8fd355d206271d30bce81b5afa36491c6ad6273ac0fcabd1a0142498a3a1b4, chain ID 48555, one signer, all of which you can check against the published genesis rather than take from us.

What it does mean. Do not treat chain 48555 as a durable ledger today. It is a live network you can read, query and reproduce, and it is not yet a permanent record. Durability is what independent validators buy, and that gate is openly unmet on the roadmap.

The full machine-readable ledger, including the node log lines each entry was built from, is at rewind-history.jsonl. It is rebuilt from the node log by chain/scripts/rewind-ledger.py, so anyone holding the log can reproduce it rather than trust it.