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
fix(ibm): let the partnership demos load their own payment script instead of reaching across origins
nirholas6cf18771dc10
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 20288f8eb..b5081661f 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,6 +7,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-09-04- **A knock now holds the money until you actually get a reply**: Paying to reach someone used to send your money the instant the payment cleared, which meant an owner could take every knock and answer none, and you had no way to get it back. A new Solana program makes the payment conditional: it sits in a vault that only the knock itself controls, and exactly three things can happen to it. The owner answers inside the reply window and gets paid, the owner declines and you are refunded in full with no fee taken, or the window closes and anyone at all can trigger your refund. There is no admin key that can move a knock that is parked, the fee is capped at 10% in the program itself, and the fee you agreed to when you knocked cannot be raised on money that is already in escrow. Your message never touches the chain: only a fingerprint of it is stored, so either side can later prove what was sent without publishing it. Ten invariants covering every one of those promises run against the real compiled program on every test run. `[feature, security]`+- **The IBM partnership demos arm wherever the page is opened**: The live demo pages loaded their own payment script across the network by full address, so on any address other than the main site (a preview, a local run, a copy published on a partner domain) the browser refused it and the paid demos never armed. Each page now loads the copy it ships with. The publish-once page IBM hosts got the opposite fix: every file it pulls now carries our full address, so its language switcher no longer looks for a file on the host's own domain and comes back empty. (`/ibm/hello`) `[fix]`## 2026-09-03diff --git a/data/changelog.json b/data/changelog.jsonindex ff83b8738..a959d87bd 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -2,13 +2,22 @@"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.","entries": [{- "date": "2026-09-04",- "title": "A knock now holds the money until you actually get a reply",- "summary": "Paying to reach someone used to send your money the instant the payment cleared, which meant an owner could take every knock and answer none, and you had no way to get it back. A new Solana program makes the payment conditional: it sits in a vault that only the knock itself controls, and exactly three things can happen to it. The owner answers inside the reply window and gets paid, the owner declines and you are refunded in full with no fee taken, or the window closes and anyone at all can trigger your refund. There is no admin key that can move a knock that is parked, the fee is capped at 10% in the program itself, and the fee you agreed to when you knocked cannot be raised on money that is already in escrow. Your message never touches the chain: only a fingerprint of it is stored, so either side can later prove what was sent without publishing it. Ten invariants covering every one of those promises run against the real compiled program on every test run.",- "tags": [- "feature",- "security"- ]+ "date": "2026-09-04",+ "title": "The IBM partnership demos arm wherever the page is opened",+ "summary": "The live demo pages loaded their own payment script across the network by full address, so on any address other than the main site (a preview, a local run, a copy published on a partner domain) the browser refused it and the paid demos never armed. Each page now loads the copy it ships with. The publish-once page IBM hosts got the opposite fix: every file it pulls now carries our full address, so its language switcher no longer looks for a file on the host's own domain and comes back empty.",+ "link": "/ibm/hello",+ "tags": [+ "fix"+ ]+ },+ {+ "date": "2026-09-04",+ "title": "A knock now holds the money until you actually get a reply",+ "summary": "Paying to reach someone used to send your money the instant the payment cleared, which meant an owner could take every knock and answer none, and you had no way to get it back. A new Solana program makes the payment conditional: it sits in a vault that only the knock itself controls, and exactly three things can happen to it. The owner answers inside the reply window and gets paid, the owner declines and you are refunded in full with no fee taken, or the window closes and anyone at all can trigger your refund. There is no admin key that can move a knock that is parked, the fee is capped at 10% in the program itself, and the fee you agreed to when you knocked cannot be raised on money that is already in escrow. Your message never touches the chain: only a fingerprint of it is stored, so either side can later prove what was sent without publishing it. Ten invariants covering every one of those promises run against the real compiled program on every test run.",+ "tags": [+ "feature",+ "security"+ ]},{"date": "2026-09-03",diff --git a/public/changelog.json b/public/changelog.jsonindex cac75898a..7c16b797c 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-04T01:36:21.284Z",+ "generated_at": "2026-09-04T01:47:50.604Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -17,6 +17,16 @@"security"]},+ {+ "date": "2026-09-04",+ "type": "update",+ "title": "The IBM partnership demos arm wherever the page is opened",+ "summary": "The live demo pages loaded their own payment script across the network by full address, so on any address other than the main site (a preview, a local run, a copy published on a partner domain) the browser refused it and the paid demos never armed. Each page now loads the copy it ships with. The publish-once page IBM hosts got the opposite fix: every file it pulls now carries our full address, so its language switcher no longer looks for a file on the host's own domain and comes back empty.",+ "link": "/ibm/hello",+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-03","type": "launch",diff --git a/public/changelog.xml b/public/changelog.xmlindex cedec157a..a0bbdf1ea 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -14,6 +14,14 @@<category>feature</category><description>Paying to reach someone used to send your money the instant the payment cleared, which meant an owner could take every knock and answer none, and you had no way to get it back. A new Solana program makes the payment conditional: it sits in a vault that only the knock itself controls, and exactly three things can happen to it. The owner answers inside the reply window and gets paid, the owner declines and you are refunded in full with no fee taken, or the window closes and anyone at all can trigger your refund. There is no admin key that can move a knock that is parked, the fee is capped at 10% in the program itself, and the fee you agreed to when you knocked cannot be raised on money that is already in escrow. Your message never touches the chain: only a fingerprint of it is stored, so either side can later prove what was sent without publishing it. Ten invariants covering every one of those promises run against the real compiled program on every test run.</description></item>+ <item>+ <title>The IBM partnership demos arm wherever the page is opened</title>+ <link>https://three.ws/ibm/hello</link>+ <guid isPermaLink="false">2026-09-04:The IBM partnership demos arm wherever the page is opened</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The live demo pages loaded their own payment script across the network by full address, so on any address other than the main site (a preview, a local run, a copy published on a partner domain) the browser refused it and the paid demos never armed. Each page now loads the copy it ships with. The publish-once page IBM hosts got the opposite fix: every file it pulls now carries our full address, so its language switcher no longer looks for a file on the host's own domain and comes back empty.</description>+ </item><item><title>Docs · Connect a home that is only on your network</title><link>https://three.ws/docs/home-relay</link>diff --git a/scripts/audit-console.mjs b/scripts/audit-console.mjsindex 0a72944a7..d9d446019 100644--- a/scripts/audit-console.mjs+++ b/scripts/audit-console.mjs@@ -29,6 +29,19 @@* dev server proxies /api/* to https://three.ws, so API calls hit real* endpoints — auth/payment-gated 4xx are classified "expected", never failures.*+ * That proxy also means an API finding measures PRODUCTION, not this working+ * tree: when production runs behind main, a handler that exists here answers 404+ * or 500 there and the page above it reads as broken code. To tell the two apart,+ * run the repo's own server and point the dev proxy at it:+ *+ * node --env-file-if-exists=.env --env-file-if-exists=.env.local server/index.mjs &+ * DEV_API_PROXY=http://localhost:8080 npx vite --port 3211 --strictPort &+ * AUDIT_BASE=http://localhost:3211 npm run audit:console+ *+ * A finding that clears under that run is deploy lag, not a defect. The reverse+ * also holds: endpoints whose credentials live only on the deployed service+ * answer `not_configured` locally, so judge those against the proxied default.+ ** Which API the pages talk to decides what a finding MEANS, so pick it on* purpose:*