Mining here trains DIVA's model, and a verifier replays a random slice to catch the fakes. Saved models load byte for byte, with her memory checkpointed beside them. Locked liquidity, the asset bridge desk and two wallets sit around that. Every folder is one click away.
Where DIVA's memory gets saved. The bridge mines her checkpoints, a hash tree sits behind them, and the economy keeps the books. Verifying her real chain reports CONTINUOUS across 579 blocks, 0 gaps, 0 forks.
Builds block 0 from public inputs only. Same inputs, same block, on anyone's machine.
Finding peers and talking to them privately. Blocks pass around, then get replayed so everyone agrees.
Accounts, transactions, block production and the Solidity suite. Every contract here is unaudited testnet code.
Reads answer. Writes come back with an honest error. The single liqua_* endpoint for the Liqua chain is still being built. See the RPC page ›
The hash-grinding miner from before v3. It still boots. Its work trains nothing, so it is off the launch plan, and the validator nodes and tests are being reused for rotating sealers.
Native staking that hands out nothing for free, with the escrow and claim gate behind payouts. It runs on the older testnet. Staking inside the wallets is coming.
Bring value in from 18 lanes, take it back out with a signed request. node bridge/test-asset-bridge.mjs prints 83 passed, and receipts survive a restart. Custody is a key roster with separate mint and payout thresholds (bridge/.custody/roster.json). No roster ships, so until the operator writes one the bridge issues no deposit address and pays nothing out.
2% of every mined reward auto-locks into the pool for 365 days, and the lock list is published so anyone can check it. The hybrid order-book DEX beside it passes its tests. It has not opened.
A zero-dependency bot for the channel: status posts and group moderation. It needs your own token before it can speak.
One path through everything: start here → mine → store → stake → bridge → explore → build.
The public pages and the brand pack. One command assembles a site you can deploy.
| Service | Port | Source | Docs |
|---|---|---|---|
| Forge sealer · the training chain | 8801 | forge/START-FORGE.bat | READ |
| DIVA bridge · memory chain | 8064 | chain/diva-bridge.mjs | READ |
| Site preview | 8060 | liqua-serve.cjs | READ |
| Asset bridge API · 18 lanes | 8070 | bridge/asset-bridge-node.mjs | DESK |
| Staking pool · older testnet | 8030 | pool/server.mjs | READ |
| Peer node dashboard | 8040 | node/server.mjs | READ |
| Order-book DEX relayer | 8080 | orderbook-dex/relayer | not opened |
The DIVA bridge listens on 8064 by default, so it no longer clashes with the site preview on 8060. The forge wants 8801–8803, which two other local apps also want.
npm run test:continuitycopynpm run asset-bridge:testcopynode chain/diva-bridge.mjscopynode evm/locker-demo.mjscopynpm run build:sitecopy# also: test:tiers · audit · filetreeforge: START-FORGE.batcopyforge: node open-lease.cjs --n 5copyforge: node test-e2e.cjscopydex: npm run chaincopydex: npx hardhat testcopy# the forge is where v3 mining livesAll of this runs on an experimental testnet. It is unaudited, and the tokens are worth nothing. The mainnet date is announced before mainnet, with no year and no countdown. What is done, broken and planned lives in the , and the keeps the running inventory.