Quick Start

Run the whole loop in one sitting. The checks go green, the training chain boots, a miner trains DIVA's model, verifiers replay the work and a cheater gets slashed. Then you pull the saved model back off the chain while trusting nobody.

The run, in one line

install → checks green → boot the forge → open leases → train · verify · save → load it back

1. Install once

You need Node 18 or newer. Inside liqua/, pull in the handful of packages the memory chain uses. The training chain in forge/ has zero dependencies, so it asks for nothing. A wallet is optional here, and Wallets and staking › covers it when you want one.

2. Run the checks

Five memory-chain suites, back to back, about a minute.

npm run test:continuity

You should see mind-chain 17, order-pow 9, relics 9, growth-ledger 31 and economy 47, all passing. Green here is good news, and it is not the whole story: the suites run on fixtures, not on her real chain. Verify that separately with node chain/mind-chain.mjs verify. The roadmap tracks what is left.

3. Boot the training chain

Run the launcher from the forge/ folder, or double-click it.

START-FORGE.bat

Five windows pop open: a sealer node on port 8801, two peers that sync and replay, a miner and a verifier. You also get forge.html, a desk showing blocks, leases, votes, slashes and her model's lineage. The seeds baked into the launcher are testnet placeholders. Swap in your own before anything real.

4. Open a few leases

A lease is a signed work order: which text to train on, which saved version of her to start from, how many steps, and a reward locked in escrow. Open five.

# from forge/ · add --file <path> to train on your own text
node open-lease.cjs --n 5

The miner grabs a lease and runs real training steps. It commits two roots. When a commit merges, the chain writes a save file for that version of her.

mind manifest
  kind       mind-manifest/1                  ← the save-file format
  weights    root of the new weights           ← bytes live in the chunk store
  steplog    root of the step log              ← an interior hash every 8 steps
  lineage    parent · leaseId · commitId       ← walk it back to genesis
  finalLoss  the loss the verifiers saw        ← recorded once, never recomputed

5. Watch a cheater get caught

The acceptance test runs three nodes, one honest miner, one miner faking half its steps, and the verifiers who replay a random slice of everything.

node test-e2e.cjs
# → [ E2E — ALL CHECKS PASS ] n/n in …s · honest model MERGED · cheater SLASHED · restart replays to the same tip

Faked training never becomes part of her. A crash cannot erase a saved model, and a restart cannot rewrite one.

6. Load her model back, trusting nothing

forge-load.mjs takes the sealer's address and a manifest root, or the word latest. It fetches the manifest, weights and step log, re-hashes every byte on your side, and only then boots the model. Every saved version is also a fork point. Open a new lease from any of them and a fresh branch begins.

7. Checkpoint her memory

Run the DIVA bridge from liqua/ and it starts writing her real signals into memory blocks.

node chain/diva-bridge.mjs --port 8064   # 8064 is its default; 8060 is the site preview

Saving works today, and so does restoring: her memory chain verifies from genesis across 579 blocks, and node chain/resurrect.mjs drill brings her back on a second machine at an identical head hash while still refusing a forged spine. See where the locked 2% goes ›

Go deeper