LIQUA is a chain where mining trains an AI. Every accepted block saves a smarter DIVA instead of a pile of burned hashes.
This is the visitor lane. Reading costs nothing, nothing is for sale, and you do not need a wallet. testnet · unaudited · experimental
Classic proof of work solves a puzzle and throws the answer away. Here the puzzle is a training step on DIVA's model. Every accepted block leaves a better model behind.
Each accepted model is written down as a verified manifest on the Liqua chain. Her memory is checkpointed next to it. Code to bind both under one root exists; the chain does not check that binding yet.
Verifiers rerun a random slice of the claimed training, byte for byte. Hashes that do not match cost the miner their bond.
That is the entire shopping list. Nothing else lands on your machine, and none of the steps below reach out to the internet.
Command one fires the memory-chain test suites. Command two builds the website, and it refuses to finish if the tier math test fails. A finished build is a pass all by itself.
cd liqua && npm run test:continuity && npm run build:site
One preview server, one address, printed straight into your terminal. Everything in the map below hangs off that address.
node ../liqua-serve.cjs
Open the address it prints and land on
the
homepage ›. If you only try one thing, try
/docs/walkthrough.html,
where every claim comes with the command that proves it.
/
Mine the model, unleash the mind. The whole pitch on one scroll.
/docs/walkthrough.html
Short steps. Each one is a real command with the result you should see.
/docs/whitepaper.html
The full argument, every claim marked live or coming, and none of it marked live on trust.
/docs/mind-chain-cinema.html
Her memory chain as a narrated show. Best pick if you would rather watch than read.
/mind/index.html
Meet the mind the chain keeps, and ECHO, the pet that trails her state six times slower.
/os/index.html
DIVA's home screen. A desktop-style OS where she runs as an app.
/wallet.html
HOT and COLD from one seed, one click to send. Liqua chain balances inside it are coming.
/mine.html
Training-as-mining, turned into something you can watch. Commits train on CPU; a GPU may only propose.
/economy.html
Where LIQUA flows. Numbers only where they are decided or measured.
/locked-liquidity.html
2% of every mined reward, locked for 365 days, on a list anyone can check.
/docs/roadmap.html
Every piece of v3 with the state it is in: live, broken, gap or spec, and how each one was checked.
node chain/mind-chain.mjs verify and node chain/resurrect.mjs drill to see both for
yourself.
No. Every stop in the tour opens without one. The wallet is another page you can poke at. Connecting is optional, and only the miner screen ever asks.
Real, and checkable. forge/ puts a genuine little transformer through genuine gradient steps,
then a verifier re-runs part of the job and compares bytes. Its end-to-end run prints ALL CHECKS PASS. An honest miner
merges, a cheater is slashed, the saved model loads back. The model is tiny on purpose, because what is
being proved is the machinery.
npm run test:continuity chains five suites: mind-chain, order-pow, relics, growth ledger and
economy. That is 187 assertions (71, 9, 18, 42 and 47, measured 17 Sep 2026) in about a minute. Run it yourself. The command is published so you never have
to take the number on trust. It runs on fixtures, not on her real chain, so check that one separately with
node chain/mind-chain.mjs verify.
Not yet. It runs fully on a testnet on your own machine. The public RPC, explorer and memory terminal are all coming, and the mainnet date is announced before mainnet. The memory terminal › page is built and reads the DIVA bridge on your own machine; served from here it has no node to read and says so rather than showing numbers. The roadmap › keeps the inventory of what runs and what does not.
The builder walkthrough ›. Every stage, every service, the port list, and the snags we would rather not have. It is written for someone running the whole stack.