Two deployments, for two different jobs.
| Keyless sandbox stack | Live testnet | |
|---|---|---|
| Command | docker compose up (or pnpm hosted + pnpm web) |
docker compose --profile testnet up |
| Chain | A fresh local NEAR sandbox, reset every hour | recourse.<owner>.testnet (the default pnpm deploy uses; --contract-id overrides it) |
| Model | Seed history replays genuine NEAR AI Cloud recordings; new hires from the UI use a deterministic dev model signed by the allow-listed sandbox key — no TEE, and those receipts say dev-fixture |
Live NEAR AI Cloud, attested with a fresh nonce |
| 1Click | Not used (Direct payouts on NEAR) | Live quotes with dry: true |
| Explorer links | None (no public explorer for a local chain) | NEXT_PUBLIC_EXPLORER_TX=https://testnet.nearblocks.io/txns/ |
| Needs | Docker | .env with accounts, function-call keys and NEARAI_API_KEY |
docker compose up --build
# API http://localhost:8080/health
# site http://localhost:3000stack runs scripts/hosted-sandbox.ts: it boots a sandbox, deploys the
Sputnik DAO council and the contract, seeds the cast, runs the seven demo scenarios so the site opens
with history (a slash, a rejected claim, an appeal, three bid rounds), then runs the worker (with the
sabotage switch), arbiter, keeper and three underwriter personas live, plus the indexer API. Every
HOSTED_RESET_MINUTES (default 60) it starts again from a fresh chain, which bounds any damage.
Run everything from the browser. The Demo page (/demo) shows the seven scenarios as they run, one
row each with PASS or FAIL and what happened. Its "Reset the chain and run all seven" button starts a
fresh chain and replays them (about 6 minutes). A reset affects every viewer, so it asks for
confirmation and is refused while a run is in progress or within 3 minutes of the last one.
web builds the Next.js app with NEXT_PUBLIC_API_URL (default http://localhost:8080; set
PUBLIC_API_URL to the VM's public API address when hosting).
On one small VM (2 vCPU, 4 GB): install Docker, clone, docker compose up -d, and put a reverse proxy
(Caddy or nginx) in front of :3000 and :8080 with TLS. The demo endpoints are rate-limited (10 actions
a minute per IP) and act through a server-side demo client, so visitors never need a wallet.
- Accounts and keys:
OWNER_ACCOUNT_ID/OWNER_PRIVATE_KEYon a laptop (never on the VM), and an account per service. See.env.exampleanddocs/services.md. - Deploy from the laptop:
pnpm run deploy:dao --network testnet --council-members you.testnet pnpm run deploy --network testnet --council-id council.<owner>.testnet pnpm run seed --network testnet # the full cast, about 257 NEAR pnpm seed:objective --network testnet # or a small one, about 13 NEAR, for scenario 03 pnpm setup-service-keys --network testnet pnpm register-tee-signer --network testnet --model "$NEARAI_MODEL_WORKER" pnpm register-tee-signer --network testnet --model "$NEARAI_MODEL_ARBITER"
- On the VM, with
.envholding only function-call keys andNEARAI_API_KEY:docker compose --profile testnet up -d
- Web on Vercel: root directory
apps/web, envNEXT_PUBLIC_API_URL=https://<vm>/,NEXT_PUBLIC_EXPLORER_TX=https://testnet.nearblocks.io/txns/,NEXT_PUBLIC_EXPLORER_ACCOUNT=https://testnet.nearblocks.io/address/.
The underwriters need full-access keys of dedicated accounts that only own their vaults, because
commit_bid attaches a deposit and function-call keys cannot.
restart: unless-stoppedon every service.- An uptime check on
GET /health(any monitor). - If the hosted demo goes down during judging,
pnpm demoneeds nothing hosted, and the video shows everything.