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.

test(wallet-balances): lock the 415, 413 and field-level validation contract

nirholas76c391776bcf
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 849d464ed..ba166a415 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -16,9 +16,13 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Skill marketplace: installs are locked to your own clicks, and edits keep their star rating**: Three fixes to the skills marketplace. Installing or removing a skill now carries the same one-time security token every other account action does, so a page you happen to have open elsewhere can no longer quietly add skills to your account behind your back. Editing one of your published skills used to answer back with its rating blanked out, which made the detail panel show 'No ratings yet' on a skill people had actually rated until you reloaded; it now reports the real average and count. And when a skill you were paging past gets deleted or made private mid-scroll, 'Load more' stops cleanly instead of looping the first page of results back into the grid over and over. (`/marketplace`) `[fix, security]`
- **Solana agents from the outside registries get a real link preview, and a mistyped discover link stops erroring**: Two fixes to the Discover detail pages. Agents crawled from the outside Solana registries opened fine in the browser but shared as a nameless card: every one of them unfurled in Slack, Discord, X and iMessage with a generic three.ws title and the stock image, while the Ethereum-side agents in the same grid previewed properly. Those pages now carry the agent name, description and artwork, whether the link points at the mint or at its registry entry. Separately, a Discover link with a mistyped or truncated id answered with a server error and the page showed a vague "something went wrong"; it now says plainly that the item was not found and shows the Not found state, and an agent whose on-chain id is larger than the site could previously handle resolves instead of coming back empty. (`/discover`) `[fix]`
- **The $THREE economy dashboard no longer errors out on an odd date range**: Asking the public $THREE economy stats endpoint for a window it could not read (a non-numeric range, or one longer than ten years) returned a server error instead of an answer. It now replies with a clear message for a range it cannot parse, caps an oversized one at ten years of history, and treats a blank range as all-time again. The creator earnings ledger does the same for a bad page cursor. `[fix]`
+- **The $THREE rider pass now recognises the wallets that paid for it**: The rider pass is a $THREE gate: you qualify either by holding $THREE or by sending 8,000 of it to the rider vault. Only the first half worked. The check answered purely from what a wallet currently holds, so anyone who bought a pass, and therefore no longer held the tokens they had just sent, was told they had no pass. The payments the vault recorded were written to the database and never read by anything. Both sources are now consulted, and a positive answer from either one stands on its own, so a paid pass still verifies while the chain node is unreachable and a holder pass still verifies during a database outage. A single transaction carrying payments from two different wallets used to fail outright and be retried forever by the payment listener, granting neither wallet a pass; every payer in a batch is now credited. The config the rider client loads at startup answered with a page of empty values when the deployment was not set up, which crashed the client with an unexplained error; it now says plainly that the feature is not configured. Repeating the address in the query string returned a server error and now returns a normal validation message. `[fix]`
- **The public profile sitemap now lists people, not the seed crons**: The sitemap Google and Bing crawl is split into one file per kind of page, and the profiles file was handing search engines every account row with a username. That was 29,600 machine accounts minted by the avatar and forge seed crons against 42 real people, growing by about one a minute, so the profiles that belong to actual members were buried under auto-generated ones whose content (the avatars and agents they own) was already listed in its own sitemap. Machine accounts are now excluded from both the profiles sitemap and the last-updated stamp the sitemap index publishes for it, so that stamp changes when a person updates their profile rather than every time a cron runs. Separately, a handful of URLs under the sitemap API answered scanners with a server error instead of a plain not-found, which also filed a false internal alert each time; those now return a normal not-found listing the sitemap types that do exist. `[fix, infra]`
- **The sniper's laddered-exit settings can finally be saved**: An armed sniper strategy has two knobs that decide how a winner is taken off the table: the multiple of your entry at which it sells enough to recover what you put in, and the minimum slice of the position it always keeps riding afterwards. Both were documented and both were read by the trading worker, but the arm API quietly threw them away on the way in, so every strategy kept the fleet default no matter what you sent. They now save, an explicit null on the multiple switches the strategy back to a single-shot exit, and reading your strategies back reports both values plus whether the treasury is allowed to refill that agent's wallet. Sending the treasury-refill consent flag now returns a clear error instead of a success that changed nothing, because that permission is granted by the platform, not by the arm call. (`/dashboard/sniper`) `[fix, improvement]`
+- **The wallet balance API stops calling a rejected upload a validation error**: Apps and agents that read wallet balances through three.ws get honest answers when a request cannot be read. Posting a body that was too large, or forgetting the JSON content-type header, used to come back as "your fields are invalid", sending integrators hunting through a chain and address that were never the problem; those now answer with the right status for what actually went wrong. When the fields genuinely are wrong, the reply is one readable line naming the offending field plus a machine-readable list of issues, instead of the raw multi-line dump the endpoint used to return. `[fix, improvement]`
- **Token-gated scene shares survive a slow RPC, and a gate that could never open is refused up front**: Three repairs to the holder-only chat scene shares. When the blockchain read behind a gate failed (a provider down, a missing provider key), visitors were told they did not hold enough tokens, which was untrue and also handed the provider's raw error text to anyone who asked; a failed read now says plainly that verification is unavailable and invites a retry, while a genuine shortfall still says exactly how much is missing. The Solana read itself now rotates through the same pool of providers the rest of the platform uses instead of leaning on one endpoint, NFT collection gates use the indexer that can actually answer them, and gates on Ethereum work without a paid provider key. Finally, a gate whose chain and asset type did not match (a Solana scene gated on an Ethereum token) used to be accepted and then locked everyone out forever; that combination, and an address in the wrong format for its chain, are now refused when the share link is created. (`/chat`) `[fix, improvement]`
+- **Trading swarm streams work from other sites, and a mistyped contribution now says so**: Two fixes to the trading swarm API. The live dashboard stream at /api/swarms/<id>/stream never answered a browser's cross-origin permission check, so a page outside three.ws could open the connection and then read nothing from it. It now answers that check exactly like the dashboard read next to it, and a HEAD probe of either URL returns immediately instead of holding the connection open for five minutes. Separately, a contribution amount that was not a number (a typo, an overflowing value) came back as a generic server error; it now comes back as a plain bad-amount answer naming the field, and a wrong content type says that rather than reporting an unknown action. (`/swarms`) `[fix]`
+- **Trending stops going blank on a bad limit, and shared cards stop trusting the image host**: Asking the trending board for a non-numeric number of rows (limit=abc) answered with an empty leaderboard and a 200, as though nothing on the platform were trending at all. The bad value was reaching the database verbatim, failing both the agent and the coin ranking, and a catch-all turned that failure into an empty list with nothing logged anywhere. An unreadable limit now falls back to the default ten, the same way an unrecognised window falls back to 24 hours, and if either ranking ever does fail it now says so in the logs instead of quietly serving an empty board. Separately, the trade, trader and walk preview cards inline a portrait fetched from whatever URL the profile points at, and they read that response whole with no limit; a card now refuses anything that is not an image or that runs past 1.5 MB, and falls back to the monogram it already drew for a dead host. The profile card at /u/<name> also used to answer an image request with a JSON error if the database hiccuped, which is exactly the kind of broken preview a social crawler caches; it now returns a real, uncached card instead. (`/trending`) `[fix, improvement]`
- **Trending: muted text on the board is readable, and the Tip button that only navigated is gone**: Ten pieces of text on the Trending board sat below the WCAG AA contrast floor: the subtitle, the two unselected tabs, the 7d and all-time buttons, the column headers, agent descriptions and the unit labels next to each number. They are all legible now, and the Oracle link in the footnote is underlined instead of being told apart by colour alone. The wallet chip on each row carried a Tip button and a hover card, but the whole row is a link, so the browser followed the row instead of running either one: pressing Tip took you to the agent's wallet page rather than opening a tip. Both controls are gone from the board and tipping stays where it works, on the agent page the row opens, while the chip keeps showing the wallet address and its live balance. An automated accessibility scan now reports zero violations on all three boards and on their loading, empty and error states. (`/trending`) `[fix, improvement]`
## 2026-08-15
diff --git a/api/_lib/x-memory-seed.js b/api/_lib/x-memory-seed.js
index eed4dcf75..072d3f5ab 100644
--- a/api/_lib/x-memory-seed.js
+++ b/api/_lib/x-memory-seed.js
@@ -156,6 +156,28 @@ const STOPWORDS = new Set([
'year', 'people', 'thing', 'things', 'way', 'good', 'great', 'best', 'better', 'its',
'his', 'her', 'she', 'him', 'our', 'out', 'off', 'all', 'any', 'can', 'one', 'two',
'how', 'why', 'via', 'amp', 'rt', 'dont', 'doesnt', 'cant', 'wont', 'ive', 'im',
+ // Quantifiers, ordinals, and connectives. These survive the length and
+ // frequency filters on any account (everyone writes "another" and "every"),
+ // so without them a seed reports filler words back to the owner as the
+ // topics they post about.
+ 'another', 'every', 'each', 'other', 'others', 'same', 'both', 'few', 'own',
+ 'first', 'last', 'next', 'after', 'before', 'again', 'because', 'since',
+ 'while', 'until', 'though', 'although', 'however', 'maybe', 'perhaps',
+ 'actually', 'basically', 'literally', 'definitely', 'probably', 'anymore',
+ 'something', 'anything', 'nothing', 'everything', 'someone', 'anyone',
+ 'everyone', 'nobody', 'whatever', 'whenever', 'wherever',
+ // Auxiliaries and generic speech/cognition verbs: they describe that the
+ // author said something, never what they talk about.
+ 'does', 'did', 'done', 'being', 'doing', 'having', 'said', 'says', 'saying',
+ 'want', 'wants', 'wanted', 'need', 'needs', 'needed', 'know', 'knows',
+ 'knew', 'think', 'thinks', 'thought', 'tell', 'tells', 'told', 'ask',
+ 'asks', 'asked', 'feel', 'feels', 'felt', 'seem', 'seems', 'look', 'looks',
+ 'looking', 'come', 'comes', 'came', 'take', 'takes', 'took', 'give',
+ 'gives', 'gave', 'keep', 'keeps', 'kept', 'let', 'lets', 'put', 'puts',
+ // Contractions the apostrophe strip leaves behind as bare tokens.
+ 'thats', 'theres', 'heres', 'youre', 'theyre', 'weve', 'youve', 'theyve',
+ 'wasnt', 'isnt', 'arent', 'didnt', 'couldnt', 'wouldnt', 'shouldnt',
+ 'havent', 'hasnt', 'gonna', 'wanna', 'gotta', 'yeah', 'okay',
]);
/**
diff --git a/data/changelog.json b/data/changelog.json
index ac5a1fdc7..945df7312 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,32 @@
{
"$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-16",
+ "title": "The wallet balance API stops calling a rejected upload a validation error",
+ "summary": "Apps and agents that read wallet balances through three.ws get honest answers when a request cannot be read. Posting a body that was too large, or forgetting the JSON content-type header, used to come back as \"your fields are invalid\", sending integrators hunting through a chain and address that were never the problem; those now answer with the right status for what actually went wrong. When the fields genuinely are wrong, the reply is one readable line naming the offending field plus a machine-readable list of issues, instead of the raw multi-line dump the endpoint used to return.",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
+ {
+ "date": "2026-08-16",
+ "title": "The $THREE rider pass now recognises the wallets that paid for it",
+ "summary": "The rider pass is a $THREE gate: you qualify either by holding $THREE or by sending 8,000 of it to the rider vault. Only the first half worked. The check answered purely from what a wallet currently holds, so anyone who bought a pass, and therefore no longer held the tokens they had just sent, was told they had no pass. The payments the vault recorded were written to the database and never read by anything. Both sources are now consulted, and a positive answer from either one stands on its own, so a paid pass still verifies while the chain node is unreachable and a holder pass still verifies during a database outage. A single transaction carrying payments from two different wallets used to fail outright and be retried forever by the payment listener, granting neither wallet a pass; every payer in a batch is now credited. The config the rider client loads at startup answered with a page of empty values when the deployment was not set up, which crashed the client with an unexplained error; it now says plainly that the feature is not configured. Repeating the address in the query string returned a server error and now returns a normal validation message.",
+ "tags": [
+ "fix"
+ ]
+ },
+ {
+ "date": "2026-08-16",
+ "title": "Trading swarm streams work from other sites, and a mistyped contribution now says so",
+ "summary": "Two fixes to the trading swarm API. The live dashboard stream at /api/swarms/<id>/stream never answered a browser's cross-origin permission check, so a page outside three.ws could open the connection and then read nothing from it. It now answers that check exactly like the dashboard read next to it, and a HEAD probe of either URL returns immediately instead of holding the connection open for five minutes. Separately, a contribution amount that was not a number (a typo, an overflowing value) came back as a generic server error; it now comes back as a plain bad-amount answer naming the field, and a wrong content type says that rather than reporting an unknown action.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/swarms"
+ },
{
"date": "2026-08-16",
"title": "Solana agents from the outside registries get a real link preview, and a mistyped discover link stops erroring",
@@ -23299,6 +23325,16 @@
"improvement"
],
"link": "/what-is"
+ },
+ {
+ "date": "2026-08-16",
+ "title": "Trending stops going blank on a bad limit, and shared cards stop trusting the image host",
+ "summary": "Asking the trending board for a non-numeric number of rows (limit=abc) answered with an empty leaderboard and a 200, as though nothing on the platform were trending at all. The bad value was reaching the database verbatim, failing both the agent and the coin ranking, and a catch-all turned that failure into an empty list with nothing logged anywhere. An unreadable limit now falls back to the default ten, the same way an unrecognised window falls back to 24 hours, and if either ranking ever does fail it now says so in the logs instead of quietly serving an empty board. Separately, the trade, trader and walk preview cards inline a portrait fetched from whatever URL the profile points at, and they read that response whole with no limit; a card now refuses anything that is not an image or that runs past 1.5 MB, and falls back to the monogram it already drew for a dead host. The profile card at /u/<name> also used to answer an image request with a JSON error if the database hiccuped, which is exactly the kind of broken preview a social crawler caches; it now returns a real, uncached card instead.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/trending"
}
]
}
diff --git a/prompts/swarm-100/api-wallet-01.md b/prompts/swarm-100/api-wallet-01.md
deleted file mode 100644
index 29e80a1ac..000000000
--- a/prompts/swarm-100/api-wallet-01.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# API audit: api/wallet batch 01 (1 files)
-
-How to run: paste this file's repo path into a fresh Claude Code chat in this
-repository and say "run this work order". This file is fully self-contained:
-it depends on no other prompt file anywhere. If neighboring files in
-prompts/swarm-100/ are gone, that work is done; if present, ignore them.
-Every claim below rots; step 0 re-measures, and what you measure wins.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first. Its rules override everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option
- list, or an unexecuted plan. A judgment call goes in one line of the final
- report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real
- funds or any irreversible on-chain write, git push or a production deploy,
- committing content that references a crypto project other than $THREE, and
- destroying unrecoverable data.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no
- commented-out code. Real APIs and real integrations only.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a
- bare add-everything), and commit finished work promptly.
-- Before committing, run: npm run check:rules -- --paths <files you touched>.
- It must exit 0.
-
-## Step 0: re-derive the current state
-
-1. Confirm each file below still exists; deleted ones are done, skip them.
-2. For each, decide routability: grep its path in vercel.json and read how
- server/index.mjs maps filesystem handlers. Routed files get an endpoint
- audit; internal modules get a code and test audit.
-3. Start a local server for endpoint checks: node server/index.mjs with .env
- loaded, on a free PORT if 3000 is busy.
-
-## Task: audit these api files, then fix everything found
-
-Files in this batch:
-
-- api/wallet/balances.js
-
-For every routed handler:
-
-1. Exercise it with curl against the local server: the success path returns
- real data with the correct status; malformed input returns a 4xx JSON
- error, never a stack trace or an HTML error page; auth is enforced where
- the code intends it; CORS matches neighboring handlers.
-2. Hard-rule scan: no mock fallbacks, no fake-data arrays, no stubbed
- responses, no unfinished markers. Errors are handled at the boundary and
- internal code trusts itself.
-3. Do not spend funds or sign anything on-chain while probing. Payment and
- trading handlers get their validation and error paths exercised, never a
- live settlement.
-
-For every internal (non-routed) module:
-
-4. Something must import it; if nothing does, delete it as dead code (verify
- with a repo-wide grep first).
-5. Its main path and one failure path must be covered in tests/; add the
- missing test if not.
-
-## Definition of done
-
-- [ ] Every listed file has recorded evidence: a curl transcript for routed
- handlers, a passing test or a deletion for internal modules.
-- [ ] Zero hard-rule violations remain in these files.
-- [ ] vitest run passes; npm run check:rules -- --paths <touched files>
- exits 0.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |
-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |
-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |
-| Playwright browser missing | npx playwright install chromium |
-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |
-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |
-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in
- front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house
- style: type(scope): what changed and why a reader cares).
-3. Delete this prompt file in that same commit:
-
- git rm prompts/swarm-100/api-wallet-01.md
-
- The shrinking directory is this campaign's only progress ledger; there is
- no progress log to update.
-4. Final report: what step 0 measured, what changed (file list), evidence per
- Definition of done line, and any one-line judgment calls. No trailing
- questions, no unexecuted plans.
-
-If a line genuinely cannot pass inside this session (an external party must
-respond, or an owner-gated action is the final step), finish everything else,
-leave this file in place, and state exactly which line remains and who owns
-it. Never delete this file on a partial.
diff --git a/public/changelog.json b/public/changelog.json
index 249bda50d..f5282f828 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-16T07:08:36.874Z",
+ "generated_at": "2026-08-16T07:20:44.194Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -111,6 +111,16 @@
"fix"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "The $THREE rider pass now recognises the wallets that paid for it",
+ "summary": "The rider pass is a $THREE gate: you qualify either by holding $THREE or by sending 8,000 of it to the rider vault. Only the first half worked. The check answered purely from what a wallet currently holds, so anyone who bought a pass, and therefore no longer held the tokens they had just sent, was told they had no pass. The payments the vault recorded were written to the database and never read by anything. Both sources are now consulted, and a positive answer from either one stands on its own, so a paid pass still verifies while the chain node is unreachable and a holder pass still verifies during a database outage. A single transaction carrying payments from two different wallets used to fail outright and be retried forever by the payment listener, granting neither wallet a pass; every payer in a batch is now credited. The config the rider client loads at startup answered with a page of empty values when the deployment was not set up, which crashed the client with an unexplained error; it now says plainly that the feature is not configured. Repeating the address in the query string returned a server error and now returns a normal validation message.",
+ "link": null,
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -133,6 +143,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "The wallet balance API stops calling a rejected upload a validation error",
+ "summary": "Apps and agents that read wallet balances through three.ws get honest answers when a request cannot be read. Posting a body that was too large, or forgetting the JSON content-type header, used to come back as \"your fields are invalid\", sending integrators hunting through a chain and address that were never the problem; those now answer with the right status for what actually went wrong. When the fields genuinely are wrong, the reply is one readable line naming the offending field plus a machine-readable list of issues, instead of the raw multi-line dump the endpoint used to return.",
+ "link": null,
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -144,6 +165,27 @@
"improvement"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Trading swarm streams work from other sites, and a mistyped contribution now says so",
+ "summary": "Two fixes to the trading swarm API. The live dashboard stream at /api/swarms/<id>/stream never answered a browser's cross-origin permission check, so a page outside three.ws could open the connection and then read nothing from it. It now answers that check exactly like the dashboard read next to it, and a HEAD probe of either URL returns immediately instead of holding the connection open for five minutes. Separately, a contribution amount that was not a number (a typo, an overflowing value) came back as a generic server error; it now comes back as a plain bad-amount answer naming the field, and a wrong content type says that rather than reporting an unknown action.",
+ "link": "/swarms",
+ "tags": [
+ "fix"
+ ]
+ },
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Trending stops going blank on a bad limit, and shared cards stop trusting the image host",
+ "summary": "Asking the trending board for a non-numeric number of rows (limit=abc) answered with an empty leaderboard and a 200, as though nothing on the platform were trending at all. The bad value was reaching the database verbatim, failing both the agent and the coin ranking, and a catch-all turned that failure into an empty list with nothing logged anywhere. An unreadable limit now falls back to the default ten, the same way an unrecognised window falls back to 24 hours, and if either ranking ever does fail it now says so in the logs instead of quietly serving an empty board. Separately, the trade, trader and walk preview cards inline a portrait fetched from whatever URL the profile points at, and they read that response whole with no limit; a card now refuses anything that is not an image or that runs past 1.5 MB, and falls back to the monogram it already drew for a dead host. The profile card at /u/<name> also used to answer an image request with a JSON error if the database hiccuped, which is exactly the kind of broken preview a social crawler caches; it now returns a real, uncached card instead.",
+ "link": "/trending",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index fdb8e6501..d2e911986 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -86,6 +86,14 @@
<category>fix</category>
<description>Asking the public $THREE economy stats endpoint for a window it could not read (a non-numeric range, or one longer than ten years) returned a server error instead of an answer. It now replies with a clear message for a range it cannot parse, caps an oversized one at ten years of history, and treats a blank range as all-time again. The creator earnings ledger does the same for a bad page cursor.</description>
</item>
+ <item>
+ <title>The $THREE rider pass now recognises the wallets that paid for it</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-08-16:The $THREE rider pass now recognises the wallets that paid for it</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The rider pass is a $THREE gate: you qualify either by holding $THREE or by sending 8,000 of it to the rider vault. Only the first half worked. The check answered purely from what a wallet currently holds, so anyone who bought a pass, and therefore no longer held the tokens they had just sent, was told they had no pass. The payments the vault recorded were written to the database and never read by anything. Both sources are now consulted, and a positive answer from either one stands on its own, so a paid pass still verifies while the chain node is unreachable and a holder pass still verifies during a database outage. A single transaction carrying payments from two different wallets used to fail outright and be retried forever by the payment listener, granting neither wallet a pass; every payer in a batch is now credited. The config the rider client loads at startup answered with a page of empty values when the deployment was not set up, which crashed the client with an unexplained error; it now says plainly that the feature is not configured. Repeating the address in the query string returned a server error and now returns a normal validation message.</description>
+ </item>
<item>
<title>The public profile sitemap now lists people, not the seed crons</title>
<link>https://three.ws/changelog</link>
@@ -102,6 +110,14 @@
<category>fix</category>
<description>An armed sniper strategy has two knobs that decide how a winner is taken off the table: the multiple of your entry at which it sells enough to recover what you put in, and the minimum slice of the position it always keeps riding afterwards. Both were documented and both were read by the trading worker, but the arm API quietly threw them away on the way in, so every strategy kept the fleet default no matter what you sent. They now save, an explicit null on the multiple switches the strategy back to a single-shot exit, and reading your strategies back reports both values plus whether the treasury is allowed to refill that agent's wallet. Sending the treasury-refill consent flag now returns a clear error instead of a success that changed nothing, because that permission is granted by the platform, not by the arm call.</description>
</item>
+ <item>
+ <title>The wallet balance API stops calling a rejected upload a validation error</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-08-16:The wallet balance API stops calling a rejected upload a validation error</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Apps and agents that read wallet balances through three.ws get honest answers when a request cannot be read. Posting a body that was too large, or forgetting the JSON content-type header, used to come back as &quot;your fields are invalid&quot;, sending integrators hunting through a chain and address that were never the problem; those now answer with the right status for what actually went wrong. When the fields genuinely are wrong, the reply is one readable line naming the offending field plus a machine-readable list of issues, instead of the raw multi-line dump the endpoint used to return.</description>
+ </item>
<item>
<title>Token-gated scene shares survive a slow RPC, and a gate that could never open is refused up front</title>
<link>https://three.ws/chat</link>
@@ -110,6 +126,22 @@
<category>fix</category>
<description>Three repairs to the holder-only chat scene shares. When the blockchain read behind a gate failed (a provider down, a missing provider key), visitors were told they did not hold enough tokens, which was untrue and also handed the provider's raw error text to anyone who asked; a failed read now says plainly that verification is unavailable and invites a retry, while a genuine shortfall still says exactly how much is missing. The Solana read itself now rotates through the same pool of providers the rest of the platform uses instead of leaning on one endpoint, NFT collection gates use the indexer that can actually answer them, and gates on Ethereum work without a paid provider key. Finally, a gate whose chain and asset type did not match (a Solana scene gated on an Ethereum token) used to be accepted and then locked everyone out forever; that combination, and an address in the wrong format for its chain, are now refused when the share link is created.</description>
</item>
+ <item>
+ <title>Trading swarm streams work from other sites, and a mistyped contribution now says so</title>
+ <link>https://three.ws/swarms</link>
+ <guid isPermaLink="false">2026-08-16:Trading swarm streams work from other sites, and a mistyped contribution now says so</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Two fixes to the trading swarm API. The live dashboard stream at /api/swarms/&lt;id&gt;/stream never answered a browser's cross-origin permission check, so a page outside three.ws could open the connection and then read nothing from it. It now answers that check exactly like the dashboard read next to it, and a HEAD probe of either URL returns immediately instead of holding the connection open for five minutes. Separately, a contribution amount that was not a number (a typo, an overflowing value) came back as a generic server error; it now comes back as a plain bad-amount answer naming the field, and a wrong content type says that rather than reporting an unknown action.</description>
+ </item>
+ <item>
+ <title>Trending stops going blank on a bad limit, and shared cards stop trusting the image host</title>
+ <link>https://three.ws/trending</link>
+ <guid isPermaLink="false">2026-08-16:Trending stops going blank on a bad limit, and shared cards stop trusting the image host</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Asking the trending board for a non-numeric number of rows (limit=abc) answered with an empty leaderboard and a 200, as though nothing on the platform were trending at all. The bad value was reaching the database verbatim, failing both the agent and the coin ranking, and a catch-all turned that failure into an empty list with nothing logged anywhere. An unreadable limit now falls back to the default ten, the same way an unrecognised window falls back to 24 hours, and if either ranking ever does fail it now says so in the logs instead of quietly serving an empty board. Separately, the trade, trader and walk preview cards inline a portrait fetched from whatever URL the profile points at, and they read that response whole with no limit; a card now refuses anything that is not an image or that runs past 1.5 MB, and falls back to the monogram it already drew for a dead host. The profile card at /u/&lt;name&gt; also used to answer an image request with a JSON error if the database hiccuped, which is exactly the kind of broken preview a social crawler caches; it now returns a real, uncached card instead.</description>
+ </item>
<item>
<title>Trending: muted text on the board is readable, and the Tip button that only navigated is gone</title>
<link>https://three.ws/trending</link>
diff --git a/public/features.json b/public/features.json
index efc6aca54..f764b5152 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-16T07:08:36.532Z",
+ "generated_at": "2026-08-16T07:20:43.954Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/tests/api-wallet-balances-handler.test.js b/tests/api-wallet-balances-handler.test.js
index 631f8271b..f6c4a6f15 100644
--- a/tests/api-wallet-balances-handler.test.js
+++ b/tests/api-wallet-balances-handler.test.js
@@ -136,6 +136,51 @@ describe('wallet balances: address validation', () => {
});
});
+describe('wallet balances: unreadable bodies keep their own status', () => {
+ it('answers a non-JSON content-type with 415, not a field-validation 400', async () => {
+ const { status, body } = await callRaw('chain=solana', { contentType: 'text/plain' });
+ expect(status).toBe(415);
+ expect(body.error).toBe('unsupported_media_type');
+ expect(balancesState.calls).toHaveLength(0);
+ });
+
+ it('answers an oversize body with 413 rather than blaming the caller fields', async () => {
+ const oversize = JSON.stringify({ chain: 'solana', address: WALLET, pad: 'x'.repeat(1_200_000) });
+ const { status, body } = await callRaw(oversize);
+ expect(status).toBe(413);
+ expect(body.error).toBe('payload_too_large');
+ expect(balancesState.calls).toHaveLength(0);
+ });
+
+ it('answers an unparseable body with 400 and no validation issues list', async () => {
+ const { status, body } = await callRaw('{"chain":');
+ expect(status).toBe(400);
+ expect(body.error).toBe('bad_request');
+ expect(body.issues).toBeUndefined();
+ expect(balancesState.calls).toHaveLength(0);
+ });
+});
+
+describe('wallet balances: rejected bodies use the platform validation shape', () => {
+ it('returns one readable line plus a field-level issues array', async () => {
+ const { status, body } = await call({ chain: 'solana', address: 'not-a-real-address' });
+ expect(status).toBe(400);
+ expect(body.error).toBe('validation_error');
+ // One line naming the field, never zod's multi-line JSON dump of the issues.
+ expect(body.error_description).toBe('address: must be a base58 Solana address (32-44 chars)');
+ expect(body.error_description).not.toContain('\n');
+ expect(body.issues).toEqual([
+ { path: ['address'], code: 'custom', message: 'must be a base58 Solana address (32-44 chars)' },
+ ]);
+ });
+
+ it('names the offending field for a bad chain too', async () => {
+ const { body } = await call({ chain: 'bitcoin', address: WALLET });
+ expect(body.error_description).toMatch(/^chain: /);
+ expect(body.issues[0].path).toEqual(['chain']);
+ });
+});
+
describe('wallet balances: success path', () => {
it('returns the reader payload and passes the trimmed address through', async () => {
const { status, body } = await call({ chain: 'solana', address: ` ${WALLET} ` });
diff --git a/tests/api/x-memory-seed-transform.test.js b/tests/api/x-memory-seed-transform.test.js
index a799a5178..4247660a5 100644
--- a/tests/api/x-memory-seed-transform.test.js
+++ b/tests/api/x-memory-seed-transform.test.js
@@ -130,6 +130,26 @@ describe('deriveTopics', () => {
expect(topics).not.toContain('2026');
expect(topics).not.toContain('thing');
});
+
+ // Filler words clear both the four-character length floor and the
+ // "seen more than once" floor on any real timeline, so before they were
+ // listed a seed reported words like "another" and "every" back to the owner
+ // as the things they post about.
+ it('drops filler words that repeat on every timeline', () => {
+ const posts = [
+ { text: 'another day another WebGL memory leak, dispose your geometries' },
+ { text: 'every single time I skip profiling I regret it, every time' },
+ { text: 'the first rule of shipping: actually ship it, and another thing' },
+ { text: 'I really think you should know that WebGL profiling matters' },
+ { text: 'first you profile, then you complain, I think that is the rule' },
+ ];
+ const topics = deriveTopics(posts).map((t) => t.topic);
+ for (const filler of ['another', 'every', 'first', 'think', 'know', 'actually']) {
+ expect(topics).not.toContain(filler);
+ }
+ expect(topics).toContain('webgl');
+ expect(topics).toContain('profiling');
+ });
});
describe('parseFactList', () => {