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(three-token): show zero dollars as $0.00 on the token dashboard and log the burn-to-buyback correction

Nicholasc07107768bdc
diff --git a/CHANGELOG.md b/CHANGELOG.md
index ad3dd4f1d..02196da07 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-16
- **Docs · The /launch launchpad** (`/docs/launchpad`): How three.ws/launch launches a pump.fun coin for a 3D agent: agent-linked metadata, the 1% dev-buy fee, v0 lookup-table and Solana transaction v1 formats, claiming creator rewards on three.ws, and the API behind it.
+- **$THREE pages now show the real buyback ledger instead of a burn estimate**: The $THREE live page and the token dashboard used to show a "$THREE burned" total that was estimated from the number of agents on the platform, not read from the blockchain. The platform does not burn $THREE, so that number is gone. Both pages now show what the protocol actually commits to: the share of revenue set aside to buy $THREE on the open market, how much has been bought, and whether the buyback engine is running. The AWS page also no longer says Marketplace usage is billed to your AWS invoice; the subscription is free and usage is paid per call. (`/three-live`) `[fix]`
- **A cleaner launchpad for your 3D agent's coin, with rewards you claim right here**: three.ws/launch is rebuilt around one flow: pick one of your 3D agents, name the coin, and launch it on pump.fun from your wallet or from the agent's own wallet. The coin's metadata links your agent's page and 3D body, a live preview and cost panel show exactly what you will pay (including a 1% three.ws fee on the dev buy), and a new My coins tab shows unclaimed creator rewards and claims them in one click, no pump.fun app needed. Launches now fit in a single transaction thanks to pump.fun's lookup table, and larger ones, like USDC-paired coins with a dev buy, use Solana transaction v1 automatically when your wallet supports it. This also fixes launches that were failing because an on-chain buyback program stopped accepting new agents. (`/launch`) `[feature, improvement, fix]`
## 2026-09-15
diff --git a/data/changelog.json b/data/changelog.json
index 0706581dd..3ad8d710f 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,15 @@
{
"$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-16",
+ "title": "$THREE pages now show the real buyback ledger instead of a burn estimate",
+ "summary": "The $THREE live page and the token dashboard used to show a \"$THREE burned\" total that was estimated from the number of agents on the platform, not read from the blockchain. The platform does not burn $THREE, so that number is gone. Both pages now show what the protocol actually commits to: the share of revenue set aside to buy $THREE on the open market, how much has been bought, and whether the buyback engine is running. The AWS page also no longer says Marketplace usage is billed to your AWS invoice; the subscription is free and usage is paid per call.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/three-live"
+ },
{
"date": "2026-09-16",
"title": "A cleaner launchpad for your 3D agent's coin, with rewards you claim right here",
diff --git a/docs/three-thesis.md b/docs/three-thesis.md
index 414772df8..abfaa50bb 100644
--- a/docs/three-thesis.md
+++ b/docs/three-thesis.md
@@ -464,7 +464,7 @@ A thesis that hides the risks is a pitch. These are the risks the three.ws docum
1. **Most holder perks are Planned, not Live.** Only two of seven registered gated features (`forge.high`, `forge.gameready`) are enforced today. The compute discount and quota multiplier are live. The `enforced` flag exists precisely so the platform never promises an unwired perk, but a holder buying for `worlds.private` or `names.first_dibs` is buying a roadmap.
-2. **The burn policy is internally inconsistent.** `api/_lib/token/config.js` states "NO PLATFORM BURNS, supply is never destroyed," while `api/three-token/[action].js` ships an `AGENT_DEPLOY_BURN = 1000` constant and a `/burns` ledger reporting 1,000 $THREE burned per agent deploy. Blog posts from May and June 2026 describe a "planned buyback-and-burn." No document reconciles these. A holder should treat the current code policy (buyback, no platform burn) as authoritative and the deploy-burn ledger as an open question.
+2. **The burn policy was internally inconsistent, and is now reconciled.** `api/_lib/token/config.js` states "NO PLATFORM BURNS, supply is never destroyed," while until 2026-09-16 `api/three-token/[action].js` shipped an `AGENT_DEPLOY_BURN = 1000` constant, and `/api/three-token/burns`, `/three-live`, and `/dashboard/three-token` reported a "burned" total computed as agent count times 1,000 with no on-chain burn behind it. That derived figure is gone: the burns endpoint now answers `policy: "no_platform_burns"` with an empty ledger, and both surfaces show the real buyback ledger instead. Blog posts from May and June 2026 still describe a "planned buyback-and-burn"; the code policy (buyback, no platform burn) is authoritative.
3. **Older blog claims predate current mechanics.** The May 2026 listing and CoinMarketCap posts describe buyback-and-burn and the Rider VR gate as the token's utility; the current code implements buyback-without-burn plus the tier ladder. The direction of travel is toward more utility, but the public record has drift.
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index 04c90a967..c9f6f74fb 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,11 +1,11 @@
{
- "generated_at": "2026-09-16T16:41:04.225Z",
+ "generated_at": "2026-09-16T16:58:37.768Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 3684,
+ "total": 3685,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
@@ -19,6 +19,16 @@
"launch"
]
},
+ {
+ "date": "2026-09-16",
+ "type": "update",
+ "title": "$THREE pages now show the real buyback ledger instead of a burn estimate",
+ "summary": "The $THREE live page and the token dashboard used to show a \"$THREE burned\" total that was estimated from the number of agents on the platform, not read from the blockchain. The platform does not burn $THREE, so that number is gone. Both pages now show what the protocol actually commits to: the share of revenue set aside to buy $THREE on the open market, how much has been bought, and whether the buyback engine is running. The AWS page also no longer says Marketplace usage is billed to your AWS invoice; the subscription is free and usage is paid per call.",
+ "link": "/three-live",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-09-16",
"type": "update",
@@ -1607,17 +1617,6 @@
"fix",
"infra"
]
- },
- {
- "date": "2026-09-07",
- "type": "update",
- "title": "A payment we cannot read now comes back with the price list, not a bare error",
- "summary": "When an agent pays one of our x402 endpoints and the payment header arrives mangled (truncated in transit, double-encoded, wrapped by a proxy), the answer used to be a plain 400 error with no prices in it, so the agent had nothing left to work from and no way to retry. Every rejected payment now returns the ordinary 402 with the full list of accepted rails, tokens and amounts attached, exactly as it does when a payment is simply missing. That is what the x402 spec and the OKX seller SDK both do, and it means a paying agent can always read the quote again and try once more. Only a real server fault answers without a quote.",
- "link": "/docs/okx-marketplace",
- "tags": [
- "fix",
- "improvement"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index 73752db5e..aaad1116c 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-16T16:41:04.189Z",
+ "generated_at": "2026-09-16T16:58:37.736Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -16,6 +16,16 @@
"launch"
]
},
+ {
+ "date": "2026-09-16",
+ "type": "update",
+ "title": "$THREE pages now show the real buyback ledger instead of a burn estimate",
+ "summary": "The $THREE live page and the token dashboard used to show a \"$THREE burned\" total that was estimated from the number of agents on the platform, not read from the blockchain. The platform does not burn $THREE, so that number is gone. Both pages now show what the protocol actually commits to: the share of revenue set aside to buy $THREE on the open market, how much has been bought, and whether the buyback engine is running. The AWS page also no longer says Marketplace usage is billed to your AWS invoice; the subscription is free and usage is paid per call.",
+ "link": "/three-live",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-09-16",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 1430b7372..2f3aabd98 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -14,6 +14,14 @@
<category>launch</category>
<description>How three.ws/launch launches a pump.fun coin for a 3D agent: agent-linked metadata, the 1% dev-buy fee, v0 lookup-table and Solana transaction v1 formats, claiming creator rewards on three.ws, and the API behind it.</description>
</item>
+ <item>
+ <title>$THREE pages now show the real buyback ledger instead of a burn estimate</title>
+ <link>https://three.ws/three-live</link>
+ <guid isPermaLink="false">2026-09-16:$THREE pages now show the real buyback ledger instead of a burn estimate</guid>
+ <pubDate>Wed, 16 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The $THREE live page and the token dashboard used to show a &quot;$THREE burned&quot; total that was estimated from the number of agents on the platform, not read from the blockchain. The platform does not burn $THREE, so that number is gone. Both pages now show what the protocol actually commits to: the share of revenue set aside to buy $THREE on the open market, how much has been bought, and whether the buyback engine is running. The AWS page also no longer says Marketplace usage is billed to your AWS invoice; the subscription is free and usage is paid per call.</description>
+ </item>
<item>
<title>A cleaner launchpad for your 3D agent's coin, with rewards you claim right here</title>
<link>https://three.ws/launch</link>
diff --git a/src/dashboard-next/pages/three-token.js b/src/dashboard-next/pages/three-token.js
index ece68bb8f..12f30e2d5 100644
--- a/src/dashboard-next/pages/three-token.js
+++ b/src/dashboard-next/pages/three-token.js
@@ -28,6 +28,7 @@ let THREE_MINT = 'FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump';
function fmtUsd(n) {
if (n == null || !Number.isFinite(+n)) return '—';
const v = +n;
+ if (v === 0) return '$0.00';
if (v >= 1_000_000) return '$' + (v / 1_000_000).toFixed(2) + 'M';
if (v >= 1_000) return '$' + (v / 1_000).toFixed(2) + 'K';
if (v >= 1) return '$' + v.toFixed(2);