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
test(solana): pin the per-mint token program resolution behind $THREE transfers
nirholascef294f8681e
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex e8f2dec24..1db2ad6ec 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -27,6 +27,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Live stage hosts stop swallowing hyphens, and only confirmed tippers get greeted by name**: Two repairs to the Living Stages host. The cleanup pass that tidies the host's spoken line was stripping hyphens along with the invisible characters it was meant to remove, so every show heard "on chain" where the host said "on-chain" and "state of the art" for "state-of-the-art"; punctuation now survives and only invisible characters are removed. Separately, the host's memory of returning regulars counted tips whose on-chain settlement had not been confirmed yet, which meant anyone could post an unconfirmed tip under a name of their choosing and hear the host greet it aloud. That memory now reads confirmed tips only, matching the public leaderboard. Smaller repairs in the same pass: a stage that has not opened its first show is no longer cached as empty at the edge, an over-long coin address is refused instead of quietly trimmed into a different plaza, and the running tip total is written before the response returns. (`/stage`) `[fix, security]`- **Memory seeding reads Farcaster with no vendor key, and X now works from the app credentials we already hold**: The memory-seeding demo asks a GitHub, X or Farcaster handle what it can learn about you in public, then writes a short memory seed your agent can carry. Two of those three connectors were showing a "connector not configured" card to everyone, because each insisted on a vendor key nobody had set. Farcaster now reads through the same failover the rest of the platform uses: an indexer when a key exists, and a public Farcaster hub with no key at all otherwise, so it returns real profiles and casts on any deployment. Anything the keyless lane genuinely cannot know, such as follower counts, is now shown as unknown instead of zero. The X connector accepts the app key and secret the platform already stores, exchanging them for a read-only token itself, so it no longer needs a separate token provisioned by hand. A mistyped Farcaster name now comes back as not found rather than as an upstream outage, and all four endpoints are documented in the API reference for the first time. (`/demos/memory-seed`) `[fix, improvement, docs]`- **Mistyped filters on the revenue, checkout and ring endpoints answer plainly instead of failing**: The public revenue feed, the checkout SKU API and the ring report all took values straight from the URL into the database. A timestamp that was not a timestamp, a checkout id that was not an id, and the query fell over: the caller got an opaque "something went wrong" with a support reference, and our own alerting logged a fault that was only ever a typo. All three now say what was wrong, in words, with the right status code. The ring report also stops treating an unrecognised period as "show me everything", which quietly answered the wrong question and ran the most expensive query it has. The revenue feed now echoes back the endpoint filter it actually applied rather than the raw text it was sent, and the paid-call lookup only accepts something shaped like a real transaction signature. (`/x402-revenue`) `[fix]`+- **Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed**: Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic. (`/credits`) `[fix]`- **Prompt polish keeps its quotes out of your model, and a busy Forge says so plainly**: Three fixes across the Forge endpoints. The Enhance button, which rewrites your rough idea into the prompt the generator actually draws from, stopped removing the quotation marks the writing model wraps around its answer: those quotes were being handed straight to the image step as if you had asked for them to be drawn. Both plain and curly quotes are stripped again. Second, when you ask the studio to change a model you already made and the generator is saturated, you now get an honest "busy, try again in a moment" with a wait time instead of a vague failure that blamed the wording of your request. Third, the self-hosted generator panel now tells a caller which input was missing rather than reporting the whole feature as unconfigured, and its status light no longer claims nothing is set up when the only problem was the address you typed. (`/forge`) `[fix, improvement]`- **Robinhood Chain worlds survive a hiccup in the live feed instead of going dark**: The in-world trading terminal inside a Robinhood Chain world polls the chain feed every five seconds, and the Worlds lobby lists those coins from the same feed. A single event that arrived without its payload, or with a timestamp the chain wrote in an unexpected format, took both requests down with a server error: the terminal showed a dead tape, and the lobby's Robinhood Chain tab quietly emptied with nothing on screen to say why. Bad events are now skipped and the rest of the tape still renders, a price that is genuinely missing stays blank rather than printing as a real $0 trade, and a launch with no readable contract address no longer produces a card that leads nowhere. Asking for trades with an address that is not a contract address now gets a clear error back instead of an empty list that read as "this coin has never traded". (`/worlds`) `[fix]`- **Scrolling the activity feed past a bad cursor no longer breaks the whole feed**: An audit of the account endpoints found one real break and two smaller ones. The activity feed on /community and your personal feed ask for the next page of results by passing the last item’s timestamp back; if that value arrived malformed, from a hand-edited link or a stale bookmark, the database rejected it and the entire feed came back as a server error with nothing to act on. It now answers with a plain "that is not a timestamp" so the page can recover and reload from the top. The referral code editor stated its length rule with a typographic dash that read as a minus sign on some devices, and now spells it out. The purchase history endpoint also documented the wrong default view: it always merges your purchases and your sales, which is what the dashboard shows. (`/community`) `[fix]`diff --git a/prompts/swarm-100/cron-batch-10.md b/prompts/swarm-100/cron-batch-10.mddeleted file mode 100644index e3462f633..000000000--- a/prompts/swarm-100/cron-batch-10.md+++ /dev/null@@ -1,106 +0,0 @@-# Cron audit batch 10: /api/cron/unstoppable-tick and 7 more--How to run: paste this file's repo path into a fresh Claude Code chat in this-repository and say "run this work order". This file is fully self-contained:-it depends on no other prompt file anywhere. If neighboring files in-prompts/swarm-100/ are gone, that work is done; if present, ignore them.-Every claim below rots; step 0 re-measures, and what you measure wins.--## Operating clause (binding)--- Read CLAUDE.md first. Its rules override everything, including this file.-- Finish 100% in this session. Never end the turn with a question, an option- list, or an unexecuted plan. A judgment call goes in one line of the final- report; it never becomes a question that halts work.-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real- funds or any irreversible on-chain write, git push or a production deploy,- committing content that references a crypto project other than $THREE, and- destroying unrecoverable data.-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no- commented-out code. Real APIs and real integrations only.-- The em-dash and en-dash characters are banned in everything you write.-- Concurrent agents share this worktree: stage explicit paths only (never a- bare add-everything), and commit finished work promptly.-- Before committing, run: npm run check:rules -- --paths <files you touched>.- It must exit 0.--## Step 0: re-derive the current state--1. Confirm each cron below still exists in vercel.json crons; removed ones are- out of scope.-2. Scheduler truth (crons run on Cloud Scheduler, never in-process):-- export PATH="$HOME/google-cloud-sdk/bin:$PATH"- gcloud scheduler jobs list --project aerial-vehicle-466722-p5 --location us-central1 | grep -E 'unstoppable-tick|forge-seed-cron|sketchfab-showcase|avatar-thumbnail-render|avatar-thumbnail-backfill|forge-thumbnail-backfill|agent-avatar-backfill|coin-intel-observe'--3. Production behavior, last 72h, per cron:-- gcloud logging read 'resource.type="cloud_run_revision" resource.labels.service_name="three-ws-api" textPayload:"<cron name>"' --freshness=72h --limit 50 --project aerial-vehicle-466722-p5--## Task: verify and fix these scheduled jobs--Crons in this batch:--- /api/cron/unstoppable-tick-- /api/cron/forge-seed-cron-- /api/cron/sketchfab-showcase-- /api/cron/avatar-thumbnail-render-- /api/cron/avatar-thumbnail-backfill-- /api/cron/forge-thumbnail-backfill-- /api/cron/agent-avatar-backfill-- /api/cron/coin-intel-observe--For each cron:--1. Read the handler and its auth guard (crons authenticate; find the shared- pattern in api/_lib before invoking anything).-2. Invoke it once against a locally started server with the proper cron auth- from .env. It must complete without an unhandled error and be safe to run- twice (idempotent); if a local run would move real funds or write on-chain,- audit its dry-run or validation path instead and say so in the report.-3. Production logs from step 0: zero unhandled errors and evidence it actually- fires on schedule. A cron that exists in vercel.json but has no scheduler- job, or vice versa, is drift: fix it (npm run check:cron-drift helps).-4. Fix every failure at root: the handler, the schedule, or the env it needs.--## Definition of done--- [ ] Every cron in the batch has a scheduler job, a clean local invocation- (or an audited dry-run path for money-moving crons), and 72h of- production logs free of unhandled errors.-- [ ] npm run check:cron-drift and npm run check:cron-syntax pass.-- [ ] npm run check:rules -- --paths <touched files> exits 0; vitest passes if- code changed.--## Never blocked--| Blocker | Resolution (act, do not ask) |-|---|---|-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |-| Playwright browser missing | npx playwright install chromium |-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |--## Close out (required)--1. Verify every Definition of done line with the actual command output in- front of you. Never claim a line you did not verify.-2. Commit with explicit paths and a subject that describes the diff (house- style: type(scope): what changed and why a reader cares).-3. Delete this prompt file in that same commit:-- git rm prompts/swarm-100/cron-batch-10.md-- The shrinking directory is this campaign's only progress ledger; there is- no progress log to update.-4. Final report: what step 0 measured, what changed (file list), evidence per- Definition of done line, and any one-line judgment calls. No trailing- questions, no unexecuted plans.--If a line genuinely cannot pass inside this session (an external party must-respond, or an owner-gated action is the final step), finish everything else,-leave this file in place, and state exactly which line remains and who owns-it. Never delete this file on a partial.diff --git a/public/changelog.json b/public/changelog.jsonindex d5f11ee69..a748cf8b7 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T17:27:32.868Z",+ "generated_at": "2026-08-16T17:28:16.748Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -228,6 +228,16 @@"fix"]},+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed",+ "summary": "Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic.",+ "link": "/credits",+ "tags": [+ "fix"+ ]+ },{"date": "2026-08-16","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 9192a685a..8a82fc035 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -174,6 +174,14 @@<category>fix</category><description>The public revenue feed, the checkout SKU API and the ring report all took values straight from the URL into the database. A timestamp that was not a timestamp, a checkout id that was not an id, and the query fell over: the caller got an opaque "something went wrong" with a support reference, and our own alerting logged a fault that was only ever a typo. All three now say what was wrong, in words, with the right status code. The ring report also stops treating an unrecognised period as "show me everything", which quietly answered the wrong question and ran the most expensive query it has. The revenue feed now echoes back the endpoint filter it actually applied rather than the raw text it was sent, and the paid-call lookup only accepts something shaped like a real transaction signature.</description></item>+ <item>+ <title>Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed</title>+ <link>https://three.ws/credits</link>+ <guid isPermaLink="false">2026-08-16:Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic.</description>+ </item><item><title>Prompt polish keeps its quotes out of your model, and a busy Forge says so plainly</title><link>https://three.ws/forge</link>diff --git a/public/features.json b/public/features.jsonindex 4b3d3c1b4..d420e3dc8 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T17:27:32.742Z",+ "generated_at": "2026-08-16T17:28:16.659Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",