What shipped, and when.
The roadmap says what each piece of v3 is intended to do and what state it is in. It carries no dates. This page does. Every entry here is written after the work is finished and carries the command that proves it.
This log starts on 16 September 2026. There is a year of work behind it, and none of it has been given a date here, because those dates were not recorded at the time and inventing them would make this page worth less than nothing. What came before is on the roadmap, which records state rather than history.
2026
-
16 Sep 2026
Her memory chain verifies end to end again
The order-seal grinder shipped a seal claiming nonce 0 while carrying the chronological order, which is not the order nonce 0 derives. Verification refused it, correctly, at block 576, and restore refuses any chain that will not verify. The grinder now ships the order nonce 0 really produces. Three historical blocks, 576 to 578, pass under an exception that is closed at height 578 and checks three things: the seal claims no work, it carries the chronological order, and its score matches the recomputed score of that exact order. Saving and restoring both work.
prove it ·
node chain/mind-chain.mjs verify --file .diva-mindchain.jsonl→ CONTINUOUS · 579 blocks · 0 gaps · 0 forks ·node chain/resurrect.mjs drill→ PASS, and a forged spine is still refused -
16 Sep 2026
Five local services stopped trusting the network
The server hub started processes from an unauthenticated request while bound to every interface, which on a shared network is remote code execution. The mind bridge accepted mint and transfer calls that named the acting account in the request body, with cross-origin reads allowed, so any page open in the operator's browser could spend on their behalf. Both are now bound to this machine and refuse a request that carries a foreign origin. The bridge custody file is created owner-only, and its path is no longer handed out by the parameters endpoint. The exchange relayers refuse to start with a well-known development key against anything but a local node.
prove it ·
RPC_URL=https://example node scripts/self-mine-relayer.js→ refuses to start and names the variable to set -
16 Sep 2026
The zero-work seal exception can no longer apply to a new block
The exception that lets the three historical blocks verify was written without a height bound, which would have made a seal claiming no work valid forever. It is now closed at 578, and the height comes from the block rather than the seal, because seals of that vintage do not carry one.
prove it ·
node chain/order-pow.mjs test→ 9 passed · 0 failed -
16 Sep 2026
The L8 OS ledger stopped reporting tampering that never happened
Only the last 500 blocks are kept, and the check started at the zero hash carried by block 0. Once block 0 was dropped, every later check failed permanently, telling an instance that had done nothing wrong that its history had been rewritten. Pruning now keeps an anchor, block numbers count the pruned blocks so no number is reused, and the result says how many blocks it no longer holds. A tampered block is still caught.
prove it ·
node os/verify-logic.mjs→ the ledger section now walks past the 500-block boundary and back -
16 Sep 2026
The homepage shows measured figures instead of five slots reading "offline"
The five headline numbers all read from a chain RPC that is not live yet, so every public visitor saw five failures in a row. They now carry figures the code prints today, each one command away and dated, and the two that a live node can honestly answer still upgrade to live values the moment one does.
prove it · the commands are on the quick start, and the strip names the date it was measured
-
16 Sep 2026
Two pages that talked to Ethereum mainnet no longer ship
A price playground whose own banner said every number on it was invented, and an ownership-renounce desk, both carried a live mainnet token address on a site that says everywhere else that LIQUA is on testnet and is worth nothing. Whatever the disclaimers said, the pair read as a contradiction. They stay in the repository as operator tools and are no longer part of the public site.
prove it · neither page appears in
liqua/dist/or in the sitemap -
16 Sep 2026
The link check covers the whole site, and the site has no broken links
The checker read the site root and the docs folder only, which is 35 of the pages that ship, and reported zero problems while the exchange, wallet, brand and mind pages loaded stylesheets from outside the web root. It now walks the whole bundle, ignores markup that a page is only showing to the reader, and reads anchors from the untouched page. Every path it found has been repaired.
prove it ·
node chain/audit.mjs→ every page inliqua/dist/walked · NO BROKEN LINKS
How this page is kept
One entry per change that a reader outside the project would care about. Written after the work, never before. The date is the day it landed. If an entry cannot name a command, a file, or a test that shows it is true, it does not go on this page.