Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(contracts): re-verify the BNB testnet deploy and record that a faucet claim is still the only human step

nirholas54d1d5b32ac9
diff --git a/contracts/DEPLOYMENTS.md b/contracts/DEPLOYMENTS.md
index dc0289e98..18f66cbc3 100644
--- a/contracts/DEPLOYMENTS.md
+++ b/contracts/DEPLOYMENTS.md
@@ -262,6 +262,40 @@ was re-measured against the current tree rather than carried forward:
dropping to 0 on `Left`. Local addresses are deliberately not recorded here;
they are anvil-local and mean nothing on the public chain.
+**Re-verified 2026-09-04. Still one faucet claim away, nothing else.** Every
+line was re-measured against the current tree, not carried forward:
+
+- Both dry runs simulate green against the live chain-97 RPC at exactly the
+ same gas as the two previous re-reads: `DeployWorldMoves` 566,068 gas and
+ `DeployGreenfieldVault` 1,711,362 gas at 0.1 gwei (0.0000566068 and
+ 0.0001711362 BNB, 0.000227743 BNB for the pair).
+- `forge test` is 19/19 on WorldMoves and 41/41 on GreenfieldVault.
+- The deployer `0x1C4918894dfA5eE11cfF9629B458b5169Cfa3871` still holds
+ 0 tBNB, read independently on three RPC lanes
+ (`data-seed-prebsc-1-s1`, `bsc-testnet.drpc.org`,
+ `bsc-testnet-rpc.publicnode.com`), all answering chainId 97.
+- The `--broadcast` path was re-proven end to end against a local
+ `anvil --chain-id 97`, running the real
+ `scripts/bnb-testnet-deploy-prove.mjs --broadcast` rather than a
+ hand-assembled sequence: both contracts deployed, then 1 `join`, 3 `move`,
+ and 1 `leave` mined through the real `api/_lib/bnb/world-moves.js` sender,
+ decoded live by `src/bnb/world-presence-reader.js` (1 Joined, 3 Moved,
+ 1 Left), with `createGhostTracker` holding 1 ghost before the leave and 0
+ after. Local addresses are again deliberately not recorded: they are
+ anvil-local.
+- The faucet is still the only human step. Four claim paths were checked and
+ every one is captcha- or account-gated: the official
+ `testnet.bnbchain.org/faucet-smart` (its `/api/v1/faucet` path serves the
+ HTML page, not a claim API), ghostchain.io and faucet.zalalena.com (both
+ Cloudflare Turnstile / hCaptcha), and tokentool.bitbond.com (wallet connect
+ plus a completed third-party profile).
+- The wiring after funding is unblocked and was re-checked: `gcloud` is
+ authenticated in the workspace again, `WORLD_MOVES_ADDRESS_TESTNET` is
+ confirmed absent from the `three-ws-api` service env, and
+ `/api/bnb/world-config?network=testnet` answers live today with
+ `address: null, deployed: false`. Setting the var is a config-only
+ `--update-env-vars` call, which needs no further approval.
+
**Real broadcast proof — anvil fork of LIVE BSC testnet state** (per
00-CONTEXT's decision-default table: "if every faucet fails, finish ALL code +
tests against a local `anvil --chain-id 97` fork" — the same workaround
@@ -446,7 +480,9 @@ BNB figures above were the constructor-only measurement; the number that
matters for funding is the total. The funding blocker is unchanged; see the
re-verification notes in the WorldMoves section for the full re-check and for
the throwaway deployer address now waiting on the faucet. Re-measured again
-2026-09-02: same 1,711,362 total gas, and `forge test` is now 41/41.
+2026-09-02 and 2026-09-04: same 1,711,362 total gas both times, and `forge
+test` is 41/41. See the WorldMoves section's 2026-09-04 block for the full
+re-read, including the four faucet paths that are all human-gated.
Deploy (once funded), preferred, because it also proves the live paths in the
same run:
diff --git a/prompts/finish/backlog-00-INDEX.md b/prompts/finish/backlog-00-INDEX.md
index 425b87b0a..c67a3de99 100644
--- a/prompts/finish/backlog-00-INDEX.md
+++ b/prompts/finish/backlog-00-INDEX.md
@@ -24,7 +24,7 @@ Re-measure before you trust any number below. Commands are in each work order.
| Forge generation | 98% (48/49 finished, 6h) | same |
| Fact-check benchmark | `ran: true`, `source: "database"`, 40% (16/40), published 2026-08-10 | `curl -s https://three.ws/api/fact-check-benchmark` |
| Media CORS at the site edge | `access-control-allow-origin: *` | `curl -I -H 'Origin: https://example.org' https://three.ws/avatars/cesium-man.glb` |
-| `gcloud` auth | dead (token refresh fails non-interactively) | `gcloud run services list` |
+| `gcloud` auth | **live again** (re-read 2026-09-04; it was dead on 2026-09-01) | `gcloud run services describe three-ws-api --region us-central1` |
Two of these overturn text elsewhere in this pack: the benchmark is live from the database
(order 04's only remaining line closed with the 2026-08-28 deploy), and production is no
@@ -66,9 +66,10 @@ reclaim plan that reported sealed wallets as reclaimable was fixed on 2026-09-02
it now opens each planned wallet's key and lists the ones that will not decrypt under
`agent_reclaim.failed`, so a dry total of 0 means the owner has to send SOL. 05 waits on one R2 admin
token. 07 needs one faucet claim and nothing else: a deployer key now exists in the gitignored
-`contracts/.env` at `0x1C4918894dfA5eE11cfF9629B458b5169Cfa3871` (re-verified 2026-09-02,
-balance 0 tBNB), both dry runs simulate green against the live chain-97 RPC, and the
-`--broadcast` path is proven end to end on a local chain-97 node. Fund that address, not
+`contracts/.env` at `0x1C4918894dfA5eE11cfF9629B458b5169Cfa3871` (re-verified 2026-09-04,
+still 0 tBNB on three chain-97 lanes), both dry runs simulate green against the live chain-97
+RPC at unchanged gas, and the `--broadcast` path was re-proven end to end on a local chain-97
+node with the real `scripts/bnb-testnet-deploy-prove.mjs --broadcast`. Fund that address, not
the retired 2026-08-02 one.
08's worker is built and committed; on 2026-09-02 it beat for the first time, from this
codespace, so `/api/healthz` now carries the `okx_chat_bot` subsystem and reports it as the