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.

fix(x402-modal): stop reporting a server-side payment refusal as a wallet cancel

ni3a4617fc5337a6
diff --git a/CHANGELOG.md b/CHANGELOG.md
index ba7171250..6cc83226b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -22,6 +22,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Five new skills teach any Claude to build on three.ws, and three standalone repos to install them from**: Until now the skills we hand out taught Claude the 3D lanes and the wallet, and stopped at the platform itself: nothing explained how to create an agent, give it a capability, put a price on it, or hire someone else's. Five new skills cover exactly that, each written against the real endpoints with the real request bodies and the real failure responses: create an agent (body, custodial Solana wallet, persona, live page), author a four-file in-app skill bundle and test it, publish and price a skill per call in $THREE with metered free trials, hire another agent under per-call and daily spend caps, and connect Claude Code, Claude Desktop or any MCP client to the hosted servers starting with the free one. The pack is also published as three small standalone repos, so installing it no longer means cloning a 60-directory monorepo: everything, the crypto-free 3D subset, or the agent-economy set. The repos are generated from the same folders the platform ships, so a copy can never drift from the original. (`/docs/agent-skills`) `[feature, sdk, docs]`
- **Light mode on the market pages now clears the contrast floor**: Every green number in a market table, and the coloured score badges on the exchange pages, were being drawn in the same hue used for chart fills. On white that reads at around 3:1, under the 4.5:1 the platform holds itself to, so gains in a table and the figures inside a trust badge were harder to read than they should have been for anyone with low vision or a bright screen. They now use the darker text shade of the same colours, which the design system already carried for exactly this. Dark mode is unchanged. Checked with the same automated WCAG rule sets the site gates on: the perpetual markets table, the new contract page, the exchange rankings and an exchange profile all report zero violations in both themes. (`/derivatives`) `[fix, improvement]`
- **Paid $THREE purchases say what is wrong instead of failing silently**: Every $THREE-priced purchase is sealed into one signed quote before you pay. If the platform side of that rail is not fully configured, the quote now comes back with a clear, retryable message and a named reason rather than an opaque internal error, and the platform status page reports the condition itself. Nobody has to be mid-checkout for the problem to be visible. (`/status`) `[fix, infra]`
+- **Paying the Club cover charge in $THREE works now**: The Club door quotes its cover in USDC or in $THREE, but every attempt to pay in $THREE failed at the last step, and the payment window wrongly said you had cancelled in your wallet when you had just approved. The cause was on our side: $THREE is issued under Solana's newer token standard (Token-2022) and our payment rail only knew how to build and check transfers for the older one, so a $THREE payment could never be verified. The rail now reads which standard a token uses and handles both, in the step that builds your transaction and in the step that verifies it. Nothing was ever charged on a failed attempt. The payment window also now shows the real reason when a payment is refused instead of blaming a cancel. (`/club`) `[fix]`
- **Put any token's 3D scene on your own site, keyed by the pair address you already have**: Token in 3D is now embeddable anywhere with a single iframe, and it accepts two identifiers instead of one. Chart terminals, launchpads and wallets name a market by its pair (pool) address, while three.ws keys tokens by mint, so /coin3d now takes ?pair= as well as ?mint= and resolves the rest itself through a new public endpoint, /api/coin/pair. Add ?embed=1 and the scene drops the chrome your own page owns, keeps one attribution link, and sends its links to a new tab instead of navigating your frame. Free, keyless, and no account: paste the iframe and it renders the live medallion, holder galaxy, graduation ring and real trade tape for that market. (`/docs/coin3d-embed`) `[feature, sdk]`
- **Queued posts can quote an earlier post**: A post in the @trythreews content queue can now name an earlier post to quote, so a follow-up can add the detail the original left out instead of repeating it. The first use quotes the $THREE token MCP announcement with the numbers behind the MCP Tool Catalog: 321 tools across 42 servers, 293 of them free, and 215 whose read-only label is checked against the source on every build. (`/mcp-tools`) `[improvement]`
- **The @trythreews account now posts three times a day, every day**: The reviewed content queue that runs the @trythreews account moved to three posts a day, eight hours apart, on every day of the week including weekends. It used to hold its flagship slot for weekdays and pack all three posts into an eight-hour afternoon window, which meant a weekend could only ever carry two. Three posts went out under the new cadence today: the $THREE token MCP server, Forge Max, and the free object library. The Forge Max post also gained a check that proves the high-quality tier is a real, gated lane before it can be published, rather than only proving its page loads. (`/changelog`) `[improvement]`
diff --git a/data/changelog.json b/data/changelog.json
index d8535f067..942dc8c87 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -28567,6 +28567,15 @@
"improvement"
],
"link": "/three"
+ },
+ {
+ "date": "2026-09-20",
+ "title": "Paying the Club cover charge in $THREE works now",
+ "summary": "The Club door quotes its cover in USDC or in $THREE, but every attempt to pay in $THREE failed at the last step, and the payment window wrongly said you had cancelled in your wallet when you had just approved. The cause was on our side: $THREE is issued under Solana's newer token standard (Token-2022) and our payment rail only knew how to build and check transfers for the older one, so a $THREE payment could never be verified. The rail now reads which standard a token uses and handles both, in the step that builds your transaction and in the step that verifies it. Nothing was ever charged on a failed attempt. The payment window also now shows the real reason when a payment is refused instead of blaming a cancel.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/club"
}
]
}
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index 1eedd244f..747e63595 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,11 +1,11 @@
{
- "generated_at": "2026-09-20T19:56:28.901Z",
+ "generated_at": "2026-09-20T20:16:26.999Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 3733,
+ "total": 3734,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
@@ -178,6 +178,16 @@
"infra"
]
},
+ {
+ "date": "2026-09-20",
+ "type": "update",
+ "title": "Paying the Club cover charge in $THREE works now",
+ "summary": "The Club door quotes its cover in USDC or in $THREE, but every attempt to pay in $THREE failed at the last step, and the payment window wrongly said you had cancelled in your wallet when you had just approved. The cause was on our side: $THREE is issued under Solana's newer token standard (Token-2022) and our payment rail only knew how to build and check transfers for the older one, so a $THREE payment could never be verified. The rail now reads which standard a token uses and handles both, in the step that builds your transaction and in the step that verifies it. Nothing was ever charged on a failed attempt. The payment window also now shows the real reason when a payment is refused instead of blaming a cancel.",
+ "link": "/club",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-09-20",
"type": "update",
@@ -1608,17 +1618,6 @@
"tags": [
"feature"
]
- },
- {
- "date": "2026-09-09",
- "type": "update",
- "title": "The Windows 11 widget draws its card again, and a new check keeps the board honest",
- "summary": "The Agent glance widget on the Windows 11 widgets board renders an Adaptive Card, and the board fills that card in with its own expression engine rather than with JavaScript. Our card asked for the three stat rows the way JavaScript reads an array, which that engine treats as a syntax error, and it refuses the whole card rather than skipping the one line: a pinned widget came up empty with nothing to show for it anywhere else. The card now uses the syntax the board expects, and there is a new check that fills it in with the board's own engine before anything ships, alongside checks that the manifest, the service worker and the two endpoints still agree with each other. The board is the one surface we cannot open from a build machine, so the checks that stand in for it are the ones that have to be real.",
- "link": "/glance",
- "tags": [
- "fix",
- "infra"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index 51b664d06..fe36f8abe 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-20T19:56:28.610Z",
+ "generated_at": "2026-09-20T20:16:26.856Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -175,6 +175,16 @@
"infra"
]
},
+ {
+ "date": "2026-09-20",
+ "type": "update",
+ "title": "Paying the Club cover charge in $THREE works now",
+ "summary": "The Club door quotes its cover in USDC or in $THREE, but every attempt to pay in $THREE failed at the last step, and the payment window wrongly said you had cancelled in your wallet when you had just approved. The cause was on our side: $THREE is issued under Solana's newer token standard (Token-2022) and our payment rail only knew how to build and check transfers for the older one, so a $THREE payment could never be verified. The rail now reads which standard a token uses and handles both, in the step that builds your transaction and in the step that verifies it. Nothing was ever charged on a failed attempt. The payment window also now shows the real reason when a payment is refused instead of blaming a cancel.",
+ "link": "/club",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-09-20",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 143bca169..1ceb54ccf 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -134,6 +134,14 @@
<category>fix</category>
<description>Every $THREE-priced purchase is sealed into one signed quote before you pay. If the platform side of that rail is not fully configured, the quote now comes back with a clear, retryable message and a named reason rather than an opaque internal error, and the platform status page reports the condition itself. Nobody has to be mid-checkout for the problem to be visible.</description>
</item>
+ <item>
+ <title>Paying the Club cover charge in $THREE works now</title>
+ <link>https://three.ws/club</link>
+ <guid isPermaLink="false">2026-09-20:Paying the Club cover charge in $THREE works now</guid>
+ <pubDate>Sun, 20 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The Club door quotes its cover in USDC or in $THREE, but every attempt to pay in $THREE failed at the last step, and the payment window wrongly said you had cancelled in your wallet when you had just approved. The cause was on our side: $THREE is issued under Solana's newer token standard (Token-2022) and our payment rail only knew how to build and check transfers for the older one, so a $THREE payment could never be verified. The rail now reads which standard a token uses and handles both, in the step that builds your transaction and in the step that verifies it. Nothing was ever charged on a failed attempt. The payment window also now shows the real reason when a payment is refused instead of blaming a cancel.</description>
+ </item>
<item>
<title>Put any token's 3D scene on your own site, keyed by the pair address you already have</title>
<link>https://three.ws/docs/coin3d-embed</link>
diff --git a/public/features.json b/public/features.json
index 6e915428e..0558d0f21 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-20T19:56:28.508Z",
+ "generated_at": "2026-09-20T20:16:26.791Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/public/x402.js b/public/x402.js
index c5a7febaf..79d9eb667 100644
--- a/public/x402.js
+++ b/public/x402.js
@@ -2270,7 +2270,17 @@ function retryAfterSeconds(res, result, fallback = 6) {
function friendlyError(err) {
const msg = err?.shortMessage || err?.message || String(err);
// Trim ethers/viem long stacks, Phantom's RPC-error verbosity.
- if (/user rejected|user denied|reject/i.test(msg)) return 'cancelled in wallet';
+ // Only a wallet's own refusal counts as a cancel: EIP-1193 code 4001, ethers'
+ // ACTION_REJECTED, or the phrasing wallets use for it. A bare /reject/ also
+ // matched the merchant's "payment rejected: <reason>", so a server-side verify
+ // failure was shown as the buyer cancelling a transaction they had just signed.
+ if (
+ err?.code === 4001 ||
+ err?.code === 'ACTION_REJECTED' ||
+ /user (rejected|denied|cancell?ed|declined)|(rejected|denied|cancell?ed) by (the )?user|^(transaction|request|signature) (was )?(rejected|declined|cancell?ed)/i.test(msg)
+ ) {
+ return 'cancelled in wallet';
+ }
// Upstream throttles (e.g. a generator's create-prediction rate limit) often
// arrive as raw provider text that names the merchant's internal billing or
// credit state. Never relay that to the buyer: the payment isn't settled until
diff --git a/x402-modal-sdk/src/x402-modal.js b/x402-modal-sdk/src/x402-modal.js
index 74820d15d..343edeeea 100644
--- a/x402-modal-sdk/src/x402-modal.js
+++ b/x402-modal-sdk/src/x402-modal.js
@@ -1271,7 +1271,17 @@ function retryAfterSeconds(res, result, fallback = 6) {
function friendlyError(err) {
const msg = err?.shortMessage || err?.message || String(err);
- if (/user rejected|user denied|reject/i.test(msg)) return 'cancelled in wallet';
+ // Only a wallet's own refusal counts as a cancel: EIP-1193 code 4001, ethers'
+ // ACTION_REJECTED, or the phrasing wallets use for it. A bare /reject/ also
+ // matched the merchant's "payment rejected: <reason>", so a server-side verify
+ // failure was shown as the buyer cancelling a transaction they had just signed.
+ if (
+ err?.code === 4001 ||
+ err?.code === 'ACTION_REJECTED' ||
+ /user (rejected|denied|cancell?ed|declined)|(rejected|denied|cancell?ed) by (the )?user|^(transaction|request|signature) (was )?(rejected|declined|cancell?ed)/i.test(msg)
+ ) {
+ return 'cancelled in wallet';
+ }
// Upstream throttles often arrive as raw provider text that names the
// merchant's internal billing or credit state. Never relay that to the buyer:
// the payment isn't settled until the merchant call succeeds.
diff --git a/x402-payment-modal/src/index.js b/x402-payment-modal/src/index.js
index abef448ae..1f79df5ad 100644
--- a/x402-payment-modal/src/index.js
+++ b/x402-payment-modal/src/index.js
@@ -1883,7 +1883,17 @@ function retryAfterSeconds(res, result, fallback = 6) {
function friendlyError(err) {
const msg = err?.shortMessage || err?.message || String(err);
// Trim ethers/viem long stacks, Phantom's RPC-error verbosity.
- if (/user rejected|user denied|reject/i.test(msg)) return 'cancelled in wallet';
+ // Only a wallet's own refusal counts as a cancel: EIP-1193 code 4001, ethers'
+ // ACTION_REJECTED, or the phrasing wallets use for it. A bare /reject/ also
+ // matched the merchant's "payment rejected: <reason>", so a server-side verify
+ // failure was shown as the buyer cancelling a transaction they had just signed.
+ if (
+ err?.code === 4001 ||
+ err?.code === 'ACTION_REJECTED' ||
+ /user (rejected|denied|cancell?ed|declined)|(rejected|denied|cancell?ed) by (the )?user|^(transaction|request|signature) (was )?(rejected|declined|cancell?ed)/i.test(msg)
+ ) {
+ return 'cancelled in wallet';
+ }
// Upstream throttles (e.g. a generator's create-prediction rate limit) often
// arrive as raw provider text that names the merchant's internal billing or
// credit state. Never relay that to the buyer: the payment isn't settled until