Files

Night 1 private testnet (sim-testnet)

A 3-node testnet-only fixture on poweredge-r350. It is reachable on the LAN only, and uses the Docker project wikideck-night.

node URL
node-a http://192.168.1.32:3101
node-b http://192.168.1.32:3102
node-c http://192.168.1.32:3103
  • compose.lan.yaml overrides only the published ports (bound to 192.168.1.32, never 0.0.0.0) and PUBLIC_ORIGIN. It changes nothing in consensus or the image.
  • mine.ts is a multi-worker native RandomX miner. It runs inside the wikideck:testnet image, which ships the native engine, so the host needs no cmake.
    • It mines to 4 disposable wallets (alice, bob, carol, dave) and writes chain-bound encrypted browser backups to $STATE_DIR/wallets/.
    • It never changes consensus code. Speed comes from the protocol's own testnet parameters: the initial target accepts 1/16 of hashes, and each 10-block retarget at most quadruples the difficulty.
    • Each template costs several Wikipedia API calls, and Wikipedia rate-limits our egress IP. The miner therefore paces templates (MIN_GAP, default 45 s) and backs off exponentially on failure.
  • compose.lan.yaml also sets, per node:
    • WIKIDECK_USER_AGENT, a Wikimedia-policy UA with a project URL (#19). Without it, Wikipedia returned 429 to our egress and templates failed.
    • the game-mode env from #22: A = classic and trending, B = draft, C = all three.
  • autodeploy.sh follows the integration branch. Run it from a dedicated detached worktree: git worktree add --detach ../deploy-src origin/night/2026-11-17 && cd ../deploy-src && deploy/night/autodeploy.sh. It polls the Gitea API every 3 min and redeploys whenever the head moves.
  • testnet.sh has up, mine N [workers], status and down. Run it from the repo root on a checkout of the integration branch. up rebuilds the image from that checkout; the ledgers persist in the named volumes.

Never point this at mainnet or the live wikideck namespace.