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): tell holders about the deadline sweep and the retries behind it
nirholasc3a632cd4e41
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 1da21949e..3b877cc8c 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-08-28++- **Photo uploads, avatar saves, launches and team tasks fail fast instead of hanging**: A handful of steps still had no time limit on the outside service they called. When that service accepted the connection and then went quiet, the request sat there until the platform killed it, and you got a spinner that ended in nothing: a photo-to-avatar upload that never came back, a saved model that never finished downloading, a coin launch stuck fetching its own thumbnail, an ordinals order whose status never loaded, a team task where one hired agent held up the whole run. Each of those now has a deadline and a clear answer when it is missed, and the ones that are safe to repeat retry once first. Anything that spends money or starts a generation is never repeated: it is bounded and then reported, so no upload is billed twice and no hire is paid twice. Saving a model from a link is also checked more tightly now, against the address it actually connects to and with the size limit applied while it downloads. `[improvement, fix, infra]`+## 2026-08-27- **three.ws for Seeker** (`/seeker`): The home screen of the three.ws app on Solana Seeker: one-tap Seed Vault sign-in, selfie to avatar, your agents, the marketplace, and Seeker Genesis Token verification.@@ -12,6 +16,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Agent pages, embeds and the camera tools keep working when a CDN or gateway is down**: The parts of the site that load files from someone else's server used to have exactly one place to get them. If that one host was slow, blocked by a corporate network, or rate-limiting the visitor, the result was a blank box with no explanation: an agent page with no avatar, a 3D preview that never appeared, mocap and sign-language input that refused to start, a deposit QR that showed a broken image. Each of those now tries every equivalent source in turn. Agent avatars retry across all four IPFS gateways, on-chain reads rotate through every public node for the chain, the 3D viewer loads its decoders from our own servers, the camera tools ship their code with the page, and a QR code that cannot be drawn falls back to text you can still copy. `[improvement, fix]`- **Every official three.ws account and address, listed in one place**: The community page now carries the complete list of channels three.ws operates: the X account we post from, the Telegram release channel and the community group, the GitHub repo, the support address, and the one $THREE contract on Solana with a copy button so nobody retypes it by hand. It is there so any account, link or "new contract" claiming to be us can be checked in about five seconds. Two things are worth committing to memory: we never message you first and nobody from three.ws will ask for a seed phrase, a private key or a wallet signature, and we never launch a second token, so any migrated or replacement $THREE contract is a theft whatever it is posted under. One change behind the list: the founder's personal X account, @nichxbt, has been unavailable since August 27, 2026, so nothing posted under that handle is us while it is down. Announcements carry on exactly as before through @trythreews, the Telegram channel, and this changelog, which publishes itself straight from the deploy. (`/community`) `[security, improvement]`- **Every outside data source now has a backup**: Prices, DeFi stats, token data, pump.fun feeds, RPC reads and 3D generation providers all had single points of failure: one rate limit or outage upstream turned into a blank section or an error page. Every one of those reads now has a deadline, retries only on transient faults, a second and third source where one exists, and keeps serving the last good value (marked as stale) when everything upstream is down. In the browser, API calls time out instead of spinning forever, script and model loads try mirror CDNs, and payment flows report a failed confirmation with the transaction signature instead of showing nothing. `[improvement, fix, infra]`+- **Every outside service the site talks to now has a time limit and a plan B**: A follow-up sweep across the whole codebase, not just the pages that had already broken. Every call to an outside service is now bounded by a deadline, which a build check enforces from here on, so one slow provider can no longer hold a page or a scheduled job open until it is killed. Reads that used to get a single attempt now retry the failures worth retrying: launch pages and share cards during a busy mint, token names, bounty lookups, agent search, Telegram alerts and trade signals. Prices for ETH now come from four independent feeds instead of one. A wallet history scan that could not reach a block explorer used to report the wallet as having never transacted, which quietly affected airdrop eligibility; it now says which chains it could not read. Risk reports are pointedly not cached, since an old verdict on a token that has since changed hands is worse than none. `[improvement, infra]`- **Every tap target on the marketplace and your agents pages now fits a thumb**: On phones, the hearts, tags, author links and the write-with-agent button on marketplace cards were as small as 18 pixels tall, so browsing on a Seeker or any Android phone meant a lot of missed taps. All of them, plus the walk-companion controls and footer links, now sit inside 44 pixel tap areas without changing how the cards look. Measured on a real phone profile: the marketplace went from 1,352 undersized controls to zero. (`/marketplace`) `[improvement]`- **Prices, wallets, search and speech keep answering when a data provider goes down**: A single slow or rate-limited provider used to be enough to blank a page. Token pages, portfolios and dashboards now fall back to other market sources and, failing that, to the last good reading, clearly marked with when it was taken instead of passed off as live. Wallet and checkout pages survive a Solana node outage: a payment can still be built, a balance reads as unknown rather than zero, and a temporary outage says retry shortly instead of failing outright. Image understanding skips a provider that is rate-limiting instead of waiting on it, so it answers from a working one. Text-to-speech falls through to a second voice engine rather than failing. Agent search still returns keyword matches when the search index is unreachable. Ticker availability is the one thing deliberately never answered from cache, because a name claimed minutes ago has to show up as taken. `[improvement, infra]`- **Seeker app: stay signed in across restarts, and a submission path that matches today's dApp Store**: On Solana Seeker, the three.ws app now remembers your Seed Vault session when Android restarts the app in the background, so reopening it no longer asks you to approve again; a revoked session is dropped cleanly instead of failing every signature. The My Agents home-screen shortcut opens your own agents instead of the public index. Behind the scenes the store submission tooling was rebuilt for the Publisher Portal that Solana Mobile now uses, and the listing copy was rewritten to describe only what the app really does. (`/my-agents`) `[improvement, fix, infra]`diff --git a/data/changelog.json b/data/changelog.jsonindex c14299f42..ce76736fa 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,25 @@{"$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-08-27",+ "title": "Every outside service the site talks to now has a time limit and a plan B",+ "summary": "A follow-up sweep across the whole codebase, not just the pages that had already broken. Every call to an outside service is now bounded by a deadline, which a build check enforces from here on, so one slow provider can no longer hold a page or a scheduled job open until it is killed. Reads that used to get a single attempt now retry the failures worth retrying: launch pages and share cards during a busy mint, token names, bounty lookups, agent search, Telegram alerts and trade signals. Prices for ETH now come from four independent feeds instead of one. A wallet history scan that could not reach a block explorer used to report the wallet as having never transacted, which quietly affected airdrop eligibility; it now says which chains it could not read. Risk reports are pointedly not cached, since an old verdict on a token that has since changed hands is worse than none.",+ "tags": [+ "improvement",+ "infra"+ ]+ },+ {+ "date": "2026-08-28",+ "title": "Photo uploads, avatar saves, launches and team tasks fail fast instead of hanging",+ "summary": "A handful of steps still had no time limit on the outside service they called. When that service accepted the connection and then went quiet, the request sat there until the platform killed it, and you got a spinner that ended in nothing: a photo-to-avatar upload that never came back, a saved model that never finished downloading, a coin launch stuck fetching its own thumbnail, an ordinals order whose status never loaded, a team task where one hired agent held up the whole run. Each of those now has a deadline and a clear answer when it is missed, and the ones that are safe to repeat retry once first. Anything that spends money or starts a generation is never repeated: it is bounded and then reported, so no upload is billed twice and no hire is paid twice. Saving a model from a link is also checked more tightly now, against the address it actually connects to and with the size limit applied while it downloads.",+ "tags": [+ "improvement",+ "fix",+ "infra"+ ]+ },{"date": "2026-08-27","title": "Every official three.ws account and address, listed in one place",diff --git a/public/changelog.json b/public/changelog.jsonindex 5cbdade26..925d2846b 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,11 +1,23 @@{- "generated_at": "2026-08-27T15:35:48.113Z",+ "generated_at": "2026-08-28T00:50:10.235Z","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-08-28",+ "type": "update",+ "title": "Photo uploads, avatar saves, launches and team tasks fail fast instead of hanging",+ "summary": "A handful of steps still had no time limit on the outside service they called. When that service accepted the connection and then went quiet, the request sat there until the platform killed it, and you got a spinner that ended in nothing: a photo-to-avatar upload that never came back, a saved model that never finished downloading, a coin launch stuck fetching its own thumbnail, an ordinals order whose status never loaded, a team task where one hired agent held up the whole run. Each of those now has a deadline and a clear answer when it is missed, and the ones that are safe to repeat retry once first. Anything that spends money or starts a generation is never repeated: it is bounded and then reported, so no upload is billed twice and no hire is paid twice. Saving a model from a link is also checked more tightly now, against the address it actually connects to and with the size limit applied while it downloads.",+ "link": null,+ "tags": [+ "improvement",+ "fix",+ "infra"+ ]+ },{"date": "2026-08-27","type": "launch",@@ -70,6 +82,17 @@"infra"]},+ {+ "date": "2026-08-27",+ "type": "update",+ "title": "Every outside service the site talks to now has a time limit and a plan B",+ "summary": "A follow-up sweep across the whole codebase, not just the pages that had already broken. Every call to an outside service is now bounded by a deadline, which a build check enforces from here on, so one slow provider can no longer hold a page or a scheduled job open until it is killed. Reads that used to get a single attempt now retry the failures worth retrying: launch pages and share cards during a busy mint, token names, bounty lookups, agent search, Telegram alerts and trade signals. Prices for ETH now come from four independent feeds instead of one. A wallet history scan that could not reach a block explorer used to report the wallet as having never transacted, which quietly affected airdrop eligibility; it now says which chains it could not read. Risk reports are pointedly not cached, since an old verdict on a token that has since changed hands is worse than none.",+ "link": null,+ "tags": [+ "improvement",+ "infra"+ ]+ },{"date": "2026-08-27","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 3d328895b..1540e8f85 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>Photo uploads, avatar saves, launches and team tasks fail fast instead of hanging</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-08-28:Photo uploads, avatar saves, launches and team tasks fail fast instead of hanging</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>A handful of steps still had no time limit on the outside service they called. When that service accepted the connection and then went quiet, the request sat there until the platform killed it, and you got a spinner that ended in nothing: a photo-to-avatar upload that never came back, a saved model that never finished downloading, a coin launch stuck fetching its own thumbnail, an ordinals order whose status never loaded, a team task where one hired agent held up the whole run. Each of those now has a deadline and a clear answer when it is missed, and the ones that are safe to repeat retry once first. Anything that spends money or starts a generation is never repeated: it is bounded and then reported, so no upload is billed twice and no hire is paid twice. Saving a model from a link is also checked more tightly now, against the address it actually connects to and with the size limit applied while it downloads.</description>+ </item><item><title>three.ws for Seeker</title><link>https://three.ws/seeker</link>@@ -54,6 +62,14 @@<category>improvement</category><description>Prices, DeFi stats, token data, pump.fun feeds, RPC reads and 3D generation providers all had single points of failure: one rate limit or outage upstream turned into a blank section or an error page. Every one of those reads now has a deadline, retries only on transient faults, a second and third source where one exists, and keeps serving the last good value (marked as stale) when everything upstream is down. In the browser, API calls time out instead of spinning forever, script and model loads try mirror CDNs, and payment flows report a failed confirmation with the transaction signature instead of showing nothing.</description></item>+ <item>+ <title>Every outside service the site talks to now has a time limit and a plan B</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-08-27:Every outside service the site talks to now has a time limit and a plan B</guid>+ <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>A follow-up sweep across the whole codebase, not just the pages that had already broken. Every call to an outside service is now bounded by a deadline, which a build check enforces from here on, so one slow provider can no longer hold a page or a scheduled job open until it is killed. Reads that used to get a single attempt now retry the failures worth retrying: launch pages and share cards during a busy mint, token names, bounty lookups, agent search, Telegram alerts and trade signals. Prices for ETH now come from four independent feeds instead of one. A wallet history scan that could not reach a block explorer used to report the wallet as having never transacted, which quietly affected airdrop eligibility; it now says which chains it could not read. Risk reports are pointedly not cached, since an old verdict on a token that has since changed hands is worse than none.</description>+ </item><item><title>Every tap target on the marketplace and your agents pages now fits a thumb</title><link>https://three.ws/marketplace</link>diff --git a/public/features.json b/public/features.jsonindex 6c61c54cf..2eb6d5511 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-27T15:35:48.096Z",+ "generated_at": "2026-08-28T00:50:10.214Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",