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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(money): record the $THREE quote signing key as live and the two receiver wallets as awaiting the owner
nirholasa0aef5bb84b8
diff --git a/docs/money-map.md b/docs/money-map.mdindex dd80431e4..d41dca222 100644--- a/docs/money-map.md+++ b/docs/money-map.md@@ -34,11 +34,39 @@ to these two wallets by the buyer's own transaction. Both are **required inproduction and fail closed**: unset, `/api/token/quote` answers `503treasury_unavailable` and no purchase can be priced at all.-| Env var | Role | Value |-| ------- | ---- | ----- |-| `THREE_TREASURY_WALLET` | Platform cut of every split; the pot the buyback lane buys into | `wwwwwDxFWRn7grgr3Esrsg5C6NvDoDHSA4gaCffccrU` (the x402 receiver, `holdsTokens`) |-| `THREE_REWARDS_WALLET` | Holder reflections pool, distributed pro-rata by the `rewards-distribute` cron | `WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW` (the economy master, which `REWARDS_DISTRIBUTOR_SECRET` signs as) |-| `THREE_QUOTE_SECRET` | HMAC key that seals a quote's amount, split and destinations | Secret Manager (`three-quote-secret`) |+| Env var | Role | Production state (2026-09-30) |+| ------- | ---- | ----------------------------- |+| `THREE_TREASURY_WALLET` | Platform cut of every split; the pot the buyback lane buys into | **Unset, awaiting the owner's address.** Candidate: `wwwwwDxFWRn7grgr3Esrsg5C6NvDoDHSA4gaCffccrU` (the x402 receiver) |+| `THREE_REWARDS_WALLET` | Holder reflections pool, planned pro-rata by the `rewards-distribute` cron | **Unset, awaiting the owner's address.** Candidate: `WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW` (the economy master), with the conflict below |+| `THREE_QUOTE_SECRET` | HMAC key that seals a quote's amount, split and destinations | **Set.** Secret Manager `three-quote-secret` (48 random bytes, base64url), `three-ws@` has `secretAccessor`, wired as a secret reference since revision `three-ws-api-00466-85g` |++Neither wallet has ever been set on any `three-ws-api` revision (all 465 through+2026-09-30 were checked), so there is no prior value to restore. Both candidates+are ordinary system-owned mainnet accounts that can hold $THREE: the x402+receiver already holds a $THREE token account, the economy master has none yet+and the buyer's transaction creates it (`src/token-pay.js` adds an idempotent+ATA create for every leg). They are written here as candidates, not values,+because the wallets decide where every buyer's $THREE lands and the owner has+not named them. Setting them is one config-only command once the+owner confirms:++ gcloud run services update three-ws-api --region us-central1 --project aerial-vehicle-466722-p5 \+ --update-env-vars THREE_TREASURY_WALLET=<treasury>,THREE_REWARDS_WALLET=<rewards>++Setting them arms no transfer on its own. `rewards-distribute` only plans (it+never sends), and the buyback, micro-buy and fee-bridge lanes that sweep $THREE+into the treasury stay off until `THREE_BUYBACK_ENABLED`,+`THREE_MICROBUY_ENABLED` or `FEE_BRIDGE_ENABLED` is set, none of which is.++**The rewards candidate conflicts with the buyback signer.**+`THREE_BUYBACK_SECRET_KEY_B64` resolves to the economy master too, and the+micro-buy lane falls back to that key when `THREE_MICROBUY_SECRET_KEY_B64` is+unset. Both lanes "self-heal" by sweeping the signer's entire $THREE balance to+the treasury (`sweepStrandedThree`, `sweepMicrobuyThree`). With the rewards pool+on the economy master, arming either lane would move the whole holder-rewards+pool into the treasury. Before arming either lane, give the rewards pool its+own keypair (and point `REWARDS_DISTRIBUTOR_SECRET` at it), or give the buyback+and micro-buy lanes keys of their own.The rewards pool **must** be the wallet `REWARDS_DISTRIBUTOR_SECRET` resolves to,or the pool accrues into an address the distribution cron cannot sign for. Thediff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.mdindex 53fba947a..9ed91ed87 100644--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md@@ -9,7 +9,7 @@ it and, if that unblocks a work order, say which one in the owning pack's `produRows carry the date they were added so staleness is visible. Re-verify a row before actingon it; some resolve themselves as other work lands.-## Open rows (2026-09-29: row 19 re-measured after the agent-sniper deploy; 2026-09-09: row 19 added, and row 1 corrected because its outage premise no longer holds; rows 1, 2, 3, 9, 13, 15 and 16 re-measured 2026-09-04; the former row 18 was cleared that day and its number is not reused; the 2026-09-02 and 2026-08-09 passes are folded in below)+## Open rows (2026-09-30: row 23 added for the $THREE receiver wallets; 2026-09-29: row 19 re-measured after the agent-sniper deploy; 2026-09-09: row 19 added, and row 1 corrected because its outage premise no longer holds; rows 1, 2, 3, 9, 13, 15 and 16 re-measured 2026-09-04; the former row 18 was cleared that day and its number is not reused; the 2026-09-02 and 2026-08-09 passes are folded in below)| # | Action | Size | Unblocks | Detail lives in ||---|---|---|---|---|@@ -34,6 +34,7 @@ on it; some resolve themselves as other work lands.| 20 | **Clear the GCP billing hold on `aerial-vehicle-466722-p5`.** Every Vertex surface answers `403 Lightning dunning decision is deny for project: projects/93741856042`, confirmed 2026-09-09 both locally and in production's own logs (Vertex Imagen falling back at 05:33 UTC). This is not IAM and nothing in code routes around it: it takes out the Vertex Gemini anchor, Imagen, and `groundedSearch`, which is the fact-checker's ONLY working search rung (no Brave/Tavily/Exa/Serper key exists). With it down the chain falls to Wikipedia alone: a benchmark run that day saw 190 sources, 100% Wikipedia, and 15 of 38 claims had zero stance-bearing evidence. It is a billing/payment state on the account, so only the owner can clear it. | minutes, at the billing console | Grounded search, Vertex Gemini, Imagen, and publishing the fact-check accuracy run (04b) | [PROGRESS.md](production-100-PROGRESS.md), 2026-09-09 entry | **Re-confirmed 2026-09-10, and the blast radius is wider than this row said.** The denial covers the Generative Language API (`generativelanguage.googleapis.com`, the `GOOGLE_API_KEY` path) as well as Vertex, so there is no Google lane of any kind. It is also the real blocker behind **order 311's i18n translation**: that order names `gcloud auth login` as its owner action, but gcloud auth WORKS in this workspace, and the actual constraint is that every reachable free lane is throttled per key (NVIDIA about 27 keys/min per process and `429`s under parallelism, Groq capped at 200k tokens/day, OpenAI `billing_not_active`). Vertex is the only lane billed to the credit pool with no free-tier quota, so it is the only one that finishes 84 locales in one pass. Clearing this hold therefore unblocks **three** orders at once: 903, 907 and 311.| 21 | **Decide whether to rotate the lane credentials read on 2026-09-09.** Resolving the LLM chain for the fact-check benchmark printed secret material into an agent session transcript: the `vercel-inference@aerial-vehicle-466722-p5` service-account **private key** (`GCP_SERVICE_ACCOUNT_JSON`, key id `93be907a...`), plus `GROQ_API_KEY`, all five OpenRouter keys, `NVIDIA_API_KEY` and `OPENAI_API_KEY`. `INTERNAL_API_KEY` was used but never printed. Nothing indicates misuse and all of them remain valid; the exposure surface is whoever can read that transcript. Rotate or accept, and note that the OpenAI key is dead anyway (row 6) and OpenRouter key #1 is already revoked. | decision (+ minutes if rotating) | Closing out the exposure | [PROGRESS.md](production-100-PROGRESS.md), 2026-09-09 entry || 22 | **Decide whether to arm the three trading growth programs** (added 2026-09-29). Built, tested and disarmed: the big-win X poster (`BIG_WIN_X_ENABLED`, posts to @trythreews), the first-rug softener (`RUG_SOFTENER_ENABLED`, pays $THREE, default cap $25 per claim and $100 per day) and the early-leader bonus (`EARLY_LEADER_ENABLED`, pays $THREE, default 20 slots at $50 and $250 per week). Each is armed on its own. Steps: (1) `npm run db:status`, then `npm run db:migrate` for `20260929120000_growth_program_payouts.sql` (payout programs only); (2) set `THREE_PRIZE_PAYOUT_KEY` (unset on production as of 2026-09-29; the programs deliberately refuse the club treasury fallback, which is the economy master wallet) to a dedicated wallet holding the $THREE to cover the caps (payout programs only); (3) deploy; (4) read the dry run at `/api/ops/growth-programs`; (5) `gcloud run services update three-ws-api --region us-central1 --update-env-vars <FLAG>=1`. Measured 2026-09-29 against production data: nothing would be posted or paid today (no live win cleared the 0.1 SOL size gate, no first trade met the softener bar, no leader has a profitable 30-day record with followers). | one yes per program | Roadmap 917 items 3.8, 12.15, 13.4 | [docs/growth-programs.md](../../docs/growth-programs.md) |+| 23 | **Name the two $THREE receiver wallets** (added 2026-09-30). `/api/healthz` reports `three_token_rail` down and signed-in `POST /api/token/quote` answers `503 treasury_unavailable`, so no $THREE-priced purchase can be priced (Forge paid tiers, spins, scarcity mints, token marketplace sales, copy-trading fees). The quote signing key is done (`three-quote-secret`, wired on `three-ws-api-00466-85g`); only `THREE_TREASURY_WALLET` and `THREE_REWARDS_WALLET` remain. No revision ever held them, so there is nothing to restore. Candidates: treasury `wwwwwDxFWRn7grgr3Esrsg5C6NvDoDHSA4gaCffccrU` (x402 receiver, already holds a $THREE account), rewards `WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW` (the economy master, which `REWARDS_DISTRIBUTOR_SECRET` signs as). The rewards candidate is also the buyback signer, so arming `THREE_BUYBACK_ENABLED` or `THREE_MICROBUY_ENABLED` would sweep the whole rewards pool into the treasury; decide that before arming either lane. Setting the two vars moves no funds by itself: `gcloud run services update three-ws-api --region us-central1 --update-env-vars THREE_TREASURY_WALLET=<treasury>,THREE_REWARDS_WALLET=<rewards>`. | two addresses | The whole $THREE purchase rail | [docs/money-map.md](../../docs/money-map.md#three-split-receivers-inbound-three) |Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), whichdeclared itself "delete on reading" and had outlived that by three weeks.