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.

docs(changelog): note that the feed seeder now pays only what the fee budget covers

nirholasce7365b4006c
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 2b3880b47..1ea6c7c74 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-29
+
+- **The platform's own payments stop crowding out the data it pays for**: Every two minutes a background job sends a batch of tiny tips to keep the payment feed moving, and three.ws pays the network fee on each one. It sent 60 at a time whether or not the day's fee budget could cover them, so about 95% were turned away after the work of preparing them, and the few that got through used up the budget the health, price and volume checks needed. The job now sends only what the budget can pay for and leaves room for those checks first. The status page also flags this pattern if it ever comes back, instead of reporting payments as healthy. (`/status`) `[fix, infra]`
+
## 2026-09-28
- **The Pole Club floor comes alive: a crowd, money on the stages, and tipping from inside the room**: Walking into the Club used to land you in an empty room. Now a crowd stands around the three stages, and every tip turns into $0.001 bills. When you tip, a clump of bills flies from where you are standing and flutters down onto her stage. When someone else tips, bills drop from the lights above her pole. The bills stay where they land, so each stage keeps a pile for the night, sized from that dancer's real tips today. You can tip without leaving the scene: every dancer has a tag over her head, and clicking her or her pole opens a picker for her routine. A tip from another visitor now puts her through the routine they paid for on your screen too, and the people at her stage cheer. Tips paid by three.ws platform agents are labelled as agent tips in the feed, drop a single violet bill, and never start a routine, and each dancer's card now says how many of today's tips came from people and how many from agents. (`/club`) `[feature, improvement]`
diff --git a/data/changelog.json b/data/changelog.json
index 3b75e72e8..026e726f7 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -28756,6 +28756,16 @@
"improvement"
],
"link": "/club"
+ },
+ {
+ "date": "2026-09-29",
+ "title": "The platform's own payments stop crowding out the data it pays for",
+ "summary": "Every two minutes a background job sends a batch of tiny tips to keep the payment feed moving, and three.ws pays the network fee on each one. It sent 60 at a time whether or not the day's fee budget could cover them, so about 95% were turned away after the work of preparing them, and the few that got through used up the budget the health, price and volume checks needed. The job now sends only what the budget can pay for and leaves room for those checks first. The status page also flags this pattern if it ever comes back, instead of reporting payments as healthy.",
+ "tags": [
+ "fix",
+ "infra"
+ ],
+ "link": "/status"
}
]
}
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index 5fedd3e82..b825b88a3 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,14 +1,25 @@
{
- "generated_at": "2026-09-28T03:03:43.032Z",
+ "generated_at": "2026-09-29T06:45:44.845Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 3758,
+ "total": 3759,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
+ {
+ "date": "2026-09-29",
+ "type": "update",
+ "title": "The platform's own payments stop crowding out the data it pays for",
+ "summary": "Every two minutes a background job sends a batch of tiny tips to keep the payment feed moving, and three.ws pays the network fee on each one. It sent 60 at a time whether or not the day's fee budget could cover them, so about 95% were turned away after the work of preparing them, and the few that got through used up the budget the health, price and volume checks needed. The job now sends only what the budget can pay for and leaves room for those checks first. The status page also flags this pattern if it ever comes back, instead of reporting payments as healthy.",
+ "link": "/status",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-09-28",
"type": "update",
@@ -1597,17 +1608,6 @@
"fix",
"improvement"
]
- },
- {
- "date": "2026-09-09",
- "type": "update",
- "title": "The health page for our paid 3D services now checks that a payment could actually be collected",
- "summary": "Every agent that buys a 3D generation from us on the OKX.AI marketplace can read a free health page first, and one of the lines on it says whether payment settlement is working. That line only ever checked that a settlement route was configured, not that it could run: the account that broadcasts a buyer's already-signed payment onto the chain pays the network fee for it, and if that account runs out of fee balance the page still read green while a paid call would have failed after the buyer had committed. The page now reports the fee balance it actually measured, and marks the payment lane down when nothing can settle, so the problem shows up on a free page before anyone pays rather than as a failure afterwards.",
- "link": "/docs/okx-marketplace",
- "tags": [
- "fix",
- "improvement"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index f50d828f2..e810c3e21 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,11 +1,22 @@
{
- "generated_at": "2026-09-28T03:03:43.010Z",
+ "generated_at": "2026-09-29T06:45:44.824Z",
"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-29",
+ "type": "update",
+ "title": "The platform's own payments stop crowding out the data it pays for",
+ "summary": "Every two minutes a background job sends a batch of tiny tips to keep the payment feed moving, and three.ws pays the network fee on each one. It sent 60 at a time whether or not the day's fee budget could cover them, so about 95% were turned away after the work of preparing them, and the few that got through used up the budget the health, price and volume checks needed. The job now sends only what the budget can pay for and leaves room for those checks first. The status page also flags this pattern if it ever comes back, instead of reporting payments as healthy.",
+ "link": "/status",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-09-28",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index a4975d2f4..f48fe26e8 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>The platform's own payments stop crowding out the data it pays for</title>
+ <link>https://three.ws/status</link>
+ <guid isPermaLink="false">2026-09-29:The platform's own payments stop crowding out the data it pays for</guid>
+ <pubDate>Tue, 29 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Every two minutes a background job sends a batch of tiny tips to keep the payment feed moving, and three.ws pays the network fee on each one. It sent 60 at a time whether or not the day's fee budget could cover them, so about 95% were turned away after the work of preparing them, and the few that got through used up the budget the health, price and volume checks needed. The job now sends only what the budget can pay for and leaves room for those checks first. The status page also flags this pattern if it ever comes back, instead of reporting payments as healthy.</description>
+ </item>
<item>
<title>The Pole Club floor comes alive: a crowd, money on the stages, and tipping from inside the room</title>
<link>https://three.ws/club</link>