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(backlog): restore the 2026-09-02 BSC re-verification and the replacement deployer address

nirholasf3d4a44c2827
diff --git a/contracts/DEPLOYMENTS.md b/contracts/DEPLOYMENTS.md
index c1c81e677..dc0289e98 100644
--- a/contracts/DEPLOYMENTS.md
+++ b/contracts/DEPLOYMENTS.md
@@ -225,13 +225,43 @@ and was re-checked from scratch, not carried over: shell env, `.env`,
`.env.local`, the `three-ws-api` Cloud Run service env, and Secret Manager all
hold no funded chain-97 key, and three programmatic faucet endpoints
(bnbchain's API, Stakely, Triangle) refuse or are retired. A throwaway deployer
-now exists at `0xC4e63FdF188D94059C877b957866726A888e1240`, written to the
-gitignored `contracts/.env`; it holds 0 tBNB and needs one human faucet run.
+was written to the gitignored `contracts/.env` at
+`0xC4e63FdF188D94059C877b957866726A888e1240`; that key no longer exists on this
+machine (see the 2026-09-02 note below for the address that replaced it, and do
+not fund the retired one).
[`scripts/bnb-testnet-deploy-prove.mjs`](../scripts/bnb-testnet-deploy-prove.mjs)
is the single command for the rest: a signature-free preflight by default, and
with `--broadcast` it deploys both contracts and then proves the live sender,
reader, and ghost paths against what it just deployed.
+**Re-verified 2026-09-02, and the deployer address changed.** Everything above
+was re-measured against the current tree rather than carried forward:
+
+- Both dry runs simulate green against the live BSC testnet RPC at exactly the
+ same gas as before: `DeployWorldMoves` 566,068 gas and `DeployGreenfieldVault`
+ 1,711,362 gas, both at 0.1 gwei (0.0000566068 and 0.0001711362 BNB).
+- `forge test` is 19/19 on WorldMoves and 41/41 on GreenfieldVault (the vault
+ suite has grown by 7 cases since the 2026-08-02 note's 34).
+- All four BSC testnet RPC lanes in `api/_lib/bnb/chains.js` answer chainId
+ `0x61` today, so the lane list is no longer one rung thin.
+- **The deployer is now `0x1C4918894dfA5eE11cfF9629B458b5169Cfa3871`.** The
+ 2026-08-02 throwaway key was not preserved across sessions, and its address
+ holds 0 tBNB, so nothing was stranded by replacing it. The new key is
+ testnet-only, lives in the gitignored `contracts/.env` at mode 600, and has
+ never held and must never hold mainnet value.
+- The faucet still has no agent path: `testnet.bnbchain.org/faucet-smart` serves
+ its reCAPTCHA page rather than a claim API, and the Stakely endpoint is gone.
+ Funding remains one human action.
+- The full `--broadcast` path was re-validated end to end against a local
+ `anvil --chain-id 97` before asking for funds, so a funded run will not be the
+ first time this code executes: 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, zero reader errors), with `createGhostTracker` holding 1 ghost
+ interpolating `{x:1110, z:-445}` toward its `{x:1500, z:-250}` target and
+ dropping to 0 on `Left`. Local addresses are deliberately not recorded here;
+ they are anvil-local and mean nothing on the public chain.
+
**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
@@ -414,8 +444,9 @@ testnet RPC at 1,695,618 total gas (1,226,903 of it the constructor) at 0.1
gwei = 0.0001695618 BNB, and `forge test` is still 34/34. The ~1.16M/~0.000170
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 note in the WorldMoves section for the full re-check and for
-the throwaway deployer address now waiting on the faucet.
+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.
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 5ee114d57..67485c0de 100644
--- a/prompts/finish/backlog-00-INDEX.md
+++ b/prompts/finish/backlog-00-INDEX.md
@@ -40,9 +40,9 @@ observable health, so 01 to 03 come first.
| # | Work order | Blocked on | Owner action needed |
|---|---|---|---|
-| 01 | [x402 settle: clear `fee_runway_exhausted`](backlog-01-x402-settle-runway.md) | nothing (config-only updates are pre-approved) | one `gcloud auth login` if auth is dead |
+| 01 | [x402 settle: clear `fee_runway_exhausted`](backlog-01-x402-settle-runway.md) | capital, and nothing else (every code and config line shipped 2026-09-02) | SOL to the economy master; the config levers are already applied |
| 05 | [R2 bucket CORS: verify, then fix at the origin](backlog-05-r2-bucket-cors.md) | one credential | mint an R2 admin token |
-| 07 | [BNB testnet: deploy the two finished contracts](backlog-07-bnb-testnet-deploys.md) | one funded EOA | fund a throwaway testnet key |
+| 07 | [BNB testnet: deploy the two finished contracts](backlog-07-bnb-testnet-deploys.md) | one funded EOA | send tBNB to `0x1C4918894dfA5eE11cfF9629B458b5169Cfa3871` (faucet is reCAPTCHA-gated) |
| 08 | [OKX chat bot: move off the codespace](backlog-08-okx-chat-bot-always-on.md) | nothing | one email OTP login |
| 09 | [Telegram bots: durable hosting for both feeds](backlog-09-telegram-bots-durability.md) | nothing | none |
| 10 | [x402scan listing: finish the last three steps](backlog-10-x402scan-listing.md) | one PAT or one comment | classic PAT, or the owner comments |
@@ -62,11 +62,16 @@ metering audit, the opt-in paid mirror, corrected docs). Their files are readabl
history; the evidence per line is in [PROGRESS.md](backlog-PROGRESS.md) under 2026-09-01.
State of what remains, measured the same day: 01 is code-complete but its outcome line is
-false (settle 5.9%, sponsor wallet under its SOL floor; capital is the owner's), and the
-dry-run reclaim plan still reports sealed wallets as reclaimable. 05 waits on one R2 admin
-token. 07 needs a new funded deployer key: the throwaway key generated on 2026-08-02 no
-longer exists on this machine, so funding the old address would strand the tokens. 08's
-worker is built and committed but has never reported a heartbeat, so it is not running
+false (settle 5.9%, sponsor wallet under its SOL floor; capital is the owner's). The dry-run
+reclaim plan that reported sealed wallets as reclaimable was fixed on 2026-09-02 (`afd349790`):
+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
+the retired 2026-08-02 one.
+08's worker is built and committed but has never reported a heartbeat, so it is not running
anywhere. 09's deliverables live in a sibling repository that is not checked out in this
workspace, so nothing here can verify them. 10's remaining external step resolved on its own
(the upstream pull request merged 2026-08-11 and the live discovery endpoint matches it);
diff --git a/prompts/finish/production-100-PROGRESS.md b/prompts/finish/production-100-PROGRESS.md
index 330413924..16d52372f 100644
--- a/prompts/finish/production-100-PROGRESS.md
+++ b/prompts/finish/production-100-PROGRESS.md
@@ -85,3 +85,43 @@ now carries its numbers (56 of 151 routes mechanically clean, 95 with a measured
none retirable on mechanical evidence) and the state of the four sweeps and the roadmap
slice. Probe artifacts stayed in the session scratchpad; the reproducible method is in
`docs/ops/swarm-100-audit.md`.
+
+## 2026-09-02: OWNER-ACTIONS re-measured, and the audit that would have lied about row 3
+
+Measured, not carried over: production still `ad7b54c16` (2026-08-28, revision 00404-ph7)
+against a `main` that has moved to **143 commits ahead** (`git rev-list --count
+ad7b54c16..HEAD`); healthz `x402_settle` down at 5.9% (3 of 51 paid attempts, 3 hours,
+`cause: sponsor_floor`, 329 `no_solana_accept`) with the sponsor wallet holding
+**0.001568 SOL** read straight off mainnet `getBalance`; `gcloud run services list` still
+refusing with "Reauthentication failed. cannot prompt during non-interactive execution";
+the `three-ws` GitHub organization and its `examples` repository both 404; the x402
+discovery endpoint live with 100 resources; the testnet deployer
+`0x1C4918894dfA5eE11cfF9629B458b5169Cfa3871` present in `contracts/.env` at balance 0,
+nonce 0.
+
+Found and fixed a defect that would have made row 3 worse than unanswered. Running
+`scripts/audit-custodial-key-health.mjs` here, where `.env.local` carries only
+`DATABASE_URL`, produced a fully confident report: **725 of 725 wallets undecryptable,
+8.57 SOL stranded, 7.29 SOL of it customer money**, followed by the escalation banner. Every
+number was an artifact of the script having no decryption key at all, and it is off by more
+than an order of magnitude from the real incident (8 wallets, 0.49 SOL). It is the same
+class of false certainty the script already guards against for unread balances. The audit
+now calls `secretBoxKeyCandidates()` before it touches the database and exits 3 with the
+places to find the key when the list is empty, and when a key is configured but opens
+nothing it says a fleet-wide 100% failure is one wrong key rather than a mass customer
+incident (`3a8000267`). `scripts/gcp-triage.mjs` skips on the structured error code instead
+of matching prose, and `docs/ops/wallet-key-migration.md` records the blind spot beside the
+two it already documents (`7335810ec`).
+
+Did: rewrote rows 1, 2, 3, 8, 9, 15 and 16 of OWNER-ACTIONS from those measurements, and
+put row 18 back in numeric order. Three premises had rotted. Row 8 asked for a GitHub PAT
+that nothing needs any more (the upstream pull request merged 2026-08-11) and was filed
+against backlog 09, which needs nothing; it now asks for the origin registration that is
+actually left, against backlog 10. Row 9 asked the owner to generate a deployer key that
+already exists and named no address to fund; it now names the address, the measured gas
+cost, and the retired address not to fund. Row 3 gained the finding above: the brief it
+waits on cannot be written from this workspace at all, because the wallet list needs
+`WALLET_ENCRYPTION_KEY` off the service env, which makes row 15 the gate on four rows.
+
+Left: no row was cleared, because none of them is an agent's to clear. Row 15 is now the
+highest-leverage one on the board.