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(changelog): note that the Club USDC checkout now reaches wallets that refused to render it
overstepping0e472c230612
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 8c4c417ad..602e17b77 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -4,6 +4,10 @@Public history for [three.ws](https://three.ws), newest first. New pages come from `added` dates in data/pages.json; everything else is curated in data/changelog.json. Also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml), live at [three.ws/changelog](https://three.ws/changelog).+## 2026-09-24++- **Paying the Club cover in USDC works in wallets that refused to show the request**: Some visitors paying the Club cover in USDC saw their wallet refuse to open the approval window, and the payment stopped with "Your wallet could not display this payment request". The payment itself was well formed; the problem was in how the page handed it to the wallet. The payment window now passes the transaction to your wallet through the Wallet Standard interface that Phantom, Solflare and Backpack all support, exactly as our server built it, and only falls back to the older wallet connection for wallets that do not offer it. Nothing was ever charged on a refused attempt. (`/club`) `[fix]`+## 2026-09-22- **Authorize the three-ws CLI** (`/cli/authorize`): Approve a sign-in started by npx three-ws in your terminal. Check the code matches, choose what the new API key may do (money-moving permissions are flagged and can be removed), and the CLI finishes setup on its own.diff --git a/data/changelog.json b/data/changelog.jsonindex 7ffbdc8be..4166b5830 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -28698,6 +28698,15 @@"infra","improvement"]+ },+ {+ "date": "2026-09-24",+ "title": "Paying the Club cover in USDC works in wallets that refused to show the request",+ "summary": "Some visitors paying the Club cover in USDC saw their wallet refuse to open the approval window, and the payment stopped with \"Your wallet could not display this payment request\". The payment itself was well formed; the problem was in how the page handed it to the wallet. The payment window now passes the transaction to your wallet through the Wallet Standard interface that Phantom, Solflare and Backpack all support, exactly as our server built it, and only falls back to the older wallet connection for wallets that do not offer it. Nothing was ever charged on a refused attempt.",+ "tags": [+ "fix"+ ],+ "link": "/club"}]}diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex b08914404..51d924ebc 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,14 +1,24 @@{- "generated_at": "2026-09-24T06:25:11.639Z",+ "generated_at": "2026-09-24T06:31:21.519Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3751,+ "total": 3752,"complete": false,"full_feed": "/changelog.json","entries": [+ {+ "date": "2026-09-24",+ "type": "update",+ "title": "Paying the Club cover in USDC works in wallets that refused to show the request",+ "summary": "Some visitors paying the Club cover in USDC saw their wallet refuse to open the approval window, and the payment stopped with \"Your wallet could not display this payment request\". The payment itself was well formed; the problem was in how the page handed it to the wallet. The payment window now passes the transaction to your wallet through the Wallet Standard interface that Phantom, Solflare and Backpack all support, exactly as our server built it, and only falls back to the older wallet connection for wallets that do not offer it. Nothing was ever charged on a refused attempt.",+ "link": "/club",+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-22","type": "launch",@@ -1599,17 +1609,6 @@"improvement","fix"]- },- {- "date": "2026-09-09",- "type": "update",- "title": "The Oracle reference now reads the model it is describing",- "summary": "The complete Oracle documentation at /oracle/docs described version 2 of the conviction model while production had moved on to version 3, and the difference was not cosmetic. Version 3 changed the question the score answers: earlier versions ranked the odds of a spike, and version 3 ranks the odds of a spike that holds, counting a launch as a hit only if a holder who bought at first sight is still up. A coin that ran 3x and gave it all back was a success under the old target and is a miss under the new one, which is why the base rate underneath every figure on the page is far lower than it used to be. The page had the old target, the old tier probabilities and the old holdout numbers throughout, and its roadmap still promised fitted weights and calibration that had already shipped. Every model figure on the page is now read live from the published model card when you open it, because the engine refits itself every six hours behind a promotion gate and any number typed into a document goes stale on a clock. When that read fails the page says so, shows the values it was published with, explains that they may trail production, and offers a retry rather than a blank space. Two public endpoints that existed but were undocumented are now in the reference: the one that publishes the whole scoring machine, weights and holdout curve and the record of every fit ever refused, and the one that publishes the realized win rate per conviction band from real fills. The tier ladder used to truncate its own evidence, cutting off the sample counts on every band below the top, and now gives each band a full line. In light mode the tier names were near-white on a white card and the strongest bands were invisible; they now have their own ramp.",- "link": "/oracle/docs",- "tags": [- "docs",- "fix"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex c6ccc65ae..0f1328a83 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,11 +1,21 @@{- "generated_at": "2026-09-24T06:25:11.616Z",+ "generated_at": "2026-09-24T06:31:21.495Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},"entries": [+ {+ "date": "2026-09-24",+ "type": "update",+ "title": "Paying the Club cover in USDC works in wallets that refused to show the request",+ "summary": "Some visitors paying the Club cover in USDC saw their wallet refuse to open the approval window, and the payment stopped with \"Your wallet could not display this payment request\". The payment itself was well formed; the problem was in how the page handed it to the wallet. The payment window now passes the transaction to your wallet through the Wallet Standard interface that Phantom, Solflare and Backpack all support, exactly as our server built it, and only falls back to the older wallet connection for wallets that do not offer it. Nothing was ever charged on a refused attempt.",+ "link": "/club",+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-22","type": "launch",diff --git a/public/changelog.xml b/public/changelog.xmlindex 93b1173fb..c7170afda 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -6,6 +6,14 @@<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/><description>What's new on three.ws: features, improvements, and releases, newest first.</description><language>en</language>+ <item>+ <title>Paying the Club cover in USDC works in wallets that refused to show the request</title>+ <link>https://three.ws/club</link>+ <guid isPermaLink="false">2026-09-24:Paying the Club cover in USDC works in wallets that refused to show the request</guid>+ <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Some visitors paying the Club cover in USDC saw their wallet refuse to open the approval window, and the payment stopped with "Your wallet could not display this payment request". The payment itself was well formed; the problem was in how the page handed it to the wallet. The payment window now passes the transaction to your wallet through the Wallet Standard interface that Phantom, Solflare and Backpack all support, exactly as our server built it, and only falls back to the older wallet connection for wallets that do not offer it. Nothing was ever charged on a refused attempt.</description>+ </item><item><title>Authorize the three-ws CLI</title><link>https://three.ws/cli/authorize</link>