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(sniper): record the journal retype and state the Exit Lab default page size

nirholasb16b235f5392
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 33c096103..ef5050cb3 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,9 +7,11 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
## 2026-08-16
- **A mistyped id on the signal marketplace answers plainly, and the live feed links to the right chain**: The signal marketplace identifies a feed or a subscription by a number. Anything that was not one (a typo, a stray word, an empty box) went straight to the database, which threw the whole query out, so the caller got an opaque "something went wrong" and our alerting recorded a fault that was never a fault. Pausing a feed, killing or resyncing a subscription, and subscribing to a feed each now answer with a plain "that is not a valid id" instead. Separately, the paid live signal stream built its Solscan links from whichever network the request named rather than the one the feed actually publishes on, so a subscriber could be handed devnet explorer links for a mainnet call; the feed's own record now decides, and every proof link lands on the chain the trade really happened on. (`/signals`) `[fix]`
+- **Agent attestations that stopped indexing now recover on their own**: An agent's on-chain attestation history is indexed by walking Solana signatures newer than the last one we recorded. If that recorded signature aged out of the RPC node's history, the walk failed outright and kept failing: the same dead signature was replayed on every run, so that agent's attestations silently stopped appearing on its profile while the scheduled job still reported success. The crawler now recognises that case, re-scans from the most recent signatures instead, and clears the stale marker, so an agent that fell behind catches up by itself on the next pass. `[fix, infra]`
- **An expired X connection now offers to reconnect instead of sending you to the login page**: Posting a Walk screenshot or clip to X goes through your connected X account. When that connection could no longer be renewed, the share endpoint answered with the same code it uses for a signed-out visitor, so the capture panel told an already signed-in user to sign in to three.ws and linked them to the login page, which fixed nothing. That case now comes back as its own answer with the X connect link attached, and the panel offers a Reconnect X button that takes you straight to the flow that repairs it. The share caption also lost a stray dash. (`/walk`) `[fix]`
- **Avatar Studio trait library: the mirror can no longer be pointed at someone else's server**: Avatar Studio loads its hair, clothing and accessory traits through a three.ws address that mirrors the open-source trait library, so your browser never talks to an outside CDN. The list of where those traits live was being written using the address in the incoming request, and that address can be set by whoever sends the request. Because the mirror is cached at the edge for a day, one crafted request could have left every Avatar Studio visitor loading trait files from a stranger's server for the next 24 hours. That list is now written the same way for everybody, with no part of it taken from the request, so there is nothing left to steer. Three smaller repairs went in alongside it: asking the mirror how big a file is no longer answers with the compressed size (a trait manifest claimed 2 KB and delivered 20 KB), the mirror will not hand back a web page or script even if the upstream library ever served one, and a failure at the library now answers plainly as either not found or mirror is down instead of passing its raw status through as ours. (`/avatar-studio`) `[security, fix]`
- **Corrected stale numbers across the avatar and animation docs**: An audit of eight documentation pages against the code they describe turned up four claims that had drifted. The Animations page said the motion-capture library held about 2,000 clips when it actually serves 2,874, so both the intro and the gallery section now quote the real size and point at the count the API itself returns. The selfie-to-avatar page listed the wrong default for the face-morph displacement clamp and credited a single tuning sweep instead of the two that chose it. The avatar-creation walkthrough still told people to pick a body type on the selfie flow, a control that was deliberately removed because it changed nothing, and named the wrong fields on the event the page dispatches. The architecture page now says plainly that the whitelist trust mode is reserved rather than enforced. (`/docs/animations`) `[docs]`
+- **Creator subscription tiers save their edits again, and a mistyped subscription link says so plainly**: Editing an existing subscription tier from the creator dashboard silently failed: the save never reached the server, so the new name, price or status was lost every time. Saving works now. Alongside it, a mistyped or truncated subscription or tier link used to answer with a generic server failure; it now says the id is not valid, which is what a reader can actually act on. Tier pages are also directly addressable, so a single tier can be linked and read on its own, with unpublished drafts still visible only to the creator who wrote them. `[fix, improvement]`
- **Live stage hosts stop swallowing hyphens, and only confirmed tippers get greeted by name**: Two repairs to the Living Stages host. The cleanup pass that tidies the host's spoken line was stripping hyphens along with the invisible characters it was meant to remove, so every show heard "on chain" where the host said "on-chain" and "state of the art" for "state-of-the-art"; punctuation now survives and only invisible characters are removed. Separately, the host's memory of returning regulars counted tips whose on-chain settlement had not been confirmed yet, which meant anyone could post an unconfirmed tip under a name of their choosing and hear the host greet it aloud. That memory now reads confirmed tips only, matching the public leaderboard. Smaller repairs in the same pass: a stage that has not opened its first show is no longer cached as empty at the edge, an over-long coin address is refused instead of quietly trimmed into a different plaza, and the running tip total is written before the response returns. (`/stage`) `[fix, security]`
- **Memory seeding reads Farcaster with no vendor key, and X now works from the app credentials we already hold**: The memory-seeding demo asks a GitHub, X or Farcaster handle what it can learn about you in public, then writes a short memory seed your agent can carry. Two of those three connectors were showing a "connector not configured" card to everyone, because each insisted on a vendor key nobody had set. Farcaster now reads through the same failover the rest of the platform uses: an indexer when a key exists, and a public Farcaster hub with no key at all otherwise, so it returns real profiles and casts on any deployment. Anything the keyless lane genuinely cannot know, such as follower counts, is now shown as unknown instead of zero. The X connector accepts the app key and secret the platform already stores, exchanging them for a read-only token itself, so it no longer needs a separate token provisioned by hand. A mistyped Farcaster name now comes back as not found rather than as an upstream outage, and all four endpoints are documented in the API reference for the first time. (`/demos/memory-seed`) `[fix, improvement, docs]`
- **Mistyped filters on the revenue, checkout and ring endpoints answer plainly instead of failing**: The public revenue feed, the checkout SKU API and the ring report all took values straight from the URL into the database. A timestamp that was not a timestamp, a checkout id that was not an id, and the query fell over: the caller got an opaque "something went wrong" with a support reference, and our own alerting logged a fault that was only ever a typo. All three now say what was wrong, in words, with the right status code. The ring report also stops treating an unrecognised period as "show me everything", which quietly answered the wrong question and ran the most expensive query it has. The revenue feed now echoes back the endpoint filter it actually applied rather than the raw text it was sent, and the paid-call lookup only accepts something shaped like a real transaction signature. (`/x402-revenue`) `[fix]`
@@ -22,10 +24,15 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **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 price quote survives an out-of-range dollar amount, and the payment audit log is admin-only for real**: The public $THREE price endpoint converts a dollar amount into a token amount. Because $THREE trades well under a cent, a dollar figure large enough to overflow what a number can hold turned that conversion into a server error, and every such request also filed a false internal alert. It now answers plainly that the amount is out of range. The token amount it quotes is also computed from the exact price printed beside it, so the two can no longer disagree when the live price refreshes partway through a request. Separately, the settled-payment audit log checked admin wallets with its own copy of the rule, comparing Solana addresses without regard to capitalisation. Solana addresses are case-sensitive, so a lookalike address that differed only in capitalisation would have been accepted; the log now uses the platform-wide admin check, which compares Solana addresses exactly and also recognises an admin who signed in with a linked wallet. `[fix, security]`
- **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 agent wallet MCP server now quotes its own address when it asks an agent to pay**: Agents that connect to the wallet server at /api/mcp-agent without a three.ws account can pay per call in USDC instead. The payment request it handed back named the main three.ws MCP server, not itself, so a paying agent signed a payment scoped to an endpoint it had not called and service directories listed the wallet server under the wrong description and tool list. It now describes itself: its own address, its own wallet-and-payments summary, and a directory example that only searches for services rather than spending anything. Separately, the one-sentence agent builder no longer mangles accented names when it suggests a handle: Munz now becomes munz rather than mu-nz. (`/docs/mcp-agent`) `[fix]`
+- **The creations gallery now counts every creation a creator has made, and pages all the way to the end**: The gallery ranked creators and paged the feed over only the newest 120 creations, however many the feed actually held. A creator's older work was invisible in their profile count, the top-creator board scored people on a fraction of their output, and scrolling the gallery dead-ended early with items still left to show. It now reads the full feed depth it always meant to, and does it in two database round trips instead of two per item, so the deeper read loads faster than the shallow one did. (`/creations`) `[fix, improvement]`
+- **The KOL, Loom and marketplace MCP servers now tell you why a call failed, and ship runnable examples**: When a market-data provider was rate-limited, these servers passed back only a bare code like provider_unavailable and threw away the sentence explaining it. They now surface the full reason. The KOL portfolio tool used to answer a provider outage with an empty card that read as a quiet wallet with no trades; it now reports the outage as an outage, so nobody sizes up a trader from a blank. The KOL and Loom packages also gained runnable examples that talk to the live public API, and the naming SDK now answers an unregistered .eth name the same way it answers an unclaimed .sol one, with data instead of an exception. `[fix, sdk]`
- **The public news feed can no longer be knocked out by a single post**: Everything that reads three.ws announcements, RSS readers and the HackerNoon importer alike, reads one feed at three.ws/rss/announcements.xml. That format has no partial failure: one illegal character anywhere in it makes the entire feed unreadable, so a single post could have taken every subscriber offline rather than costing one item. Three inputs could do that, and none of them can now. A code sample in an announcement that happened to contain the sequence that ends a raw-content block used to end it early and corrupt every item after it. Control characters the format forbids outright, which no amount of escaping can rescue, were passed straight through; they are now dropped, while emoji and other real characters are kept untouched. And a post whose wording happened to match a marker the feed builder uses internally while turning links into links stopped the feed building at all, returning an error to every reader instead. Separately, the feed takes an optional parameter for reading one of the archived accounts instead of the curated list, and misspelling it used to hand back the curated feed with no hint anything was wrong, so a subscriber could sit on the wrong feed indefinitely. It now says plainly that the source is unknown and lists the ones that exist. `[fix, infra]`
- **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 trade journal starts recording, and three sniper readouts stop reporting the wrong number**: The trade journal is the surface that answers why an agent bought and why it sold, and it had never recorded a single line. Two halves of the same mistake: the table expected a plain number where the platform stores an identifier, so every write failed and was silently discarded on purpose (a journal write must never be allowed to break a trade), and the page that reads it asked the database to compare the same two mismatched kinds of value, which failed outright and returned an error rather than an empty journal. Both are fixed and the surface now records and reads for real, across the 323 closed positions the fleet had already traded. Three readouts were also stating numbers that were not true. The Exit Lab corpus, asked without an explicit page size, answered with exactly one trade instead of the full 400, so the replay console looked like a fleet that had traded once; it now returns the whole window. The live pre-launch radar tape re-sent every precursor it had already shown, about forty times a minute, so the feed filled with copies of the same event; each precursor is now sent once. And the radar dashboard reported 100 watched wallets, the size of the table it was showing rather than the number it was watching, while the status line beside it reported the real figure; it now counts the wallets and the table says which slice of them it is showing. (`/radar`) `[fix, improvement]`
- **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 sentiment reads real pump.fun commentary again**: The sentiment pulse for a Solana token was reading a pump.fun route that no longer exists, so it scored an empty set and reported every coin as perfectly neutral with full confidence. It now reads the coin's live callouts, the commentary feed the pump.fun coin page renders, and when that source is unreachable and you supplied no text of your own it says so with an error instead of returning a neutral-looking score. The scorer itself was also matching lexicon terms inside longer words, which read 'partnered' as bearish; it now matches whole words and knows the common variants (scammer, rugged, crashing, bought). (`/tutorials/emotion-from-data`) `[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]`
diff --git a/docs/exit-lab.md b/docs/exit-lab.md
index 80f4050e7..98d18a904 100644
--- a/docs/exit-lab.md
+++ b/docs/exit-lab.md
@@ -133,7 +133,7 @@ Public and IP rate-limited, like the leaderboard. The tx signatures are the
proof, so anyone can check the fleet's homework.
`network` is `mainnet` (default) or `devnet`. `window` is `7`, `30`, `90`
-(default) or `all` days. `limit` caps at 500.
+(default) or `all` days. `limit` defaults to 400 and caps at 500.
```bash
curl -s 'https://three.ws/api/sniper/exit-lab?window=all&limit=500' | jq '{replayable, scanned, excluded, first: .trades[0]}'
diff --git a/docs/trading-experiment.md b/docs/trading-experiment.md
index 24465a5eb..50d07b0d6 100644
--- a/docs/trading-experiment.md
+++ b/docs/trading-experiment.md
@@ -316,7 +316,9 @@ much — and tune the next run. That is the whole point of the experiment.
- No-Mayhem gate: `workers/agent-sniper/mayhem-gate.js`
- Journal: `workers/agent-sniper/journal.js`, read via `api/sniper/journal.js`
- Strategy fields: `api/sniper/strategy.js`, migrations
- `20260703150000_sniper_laddered_exit.sql`, `20260703160000_trading_journal.sql`
+ `20260703150000_sniper_laddered_exit.sql`, `20260703160000_trading_journal.sql`,
+ `20260816070000_trading_journal_uuid_keys.sql` (the retype that made the
+ journal's writes land: `agent_id` and `position_id` are both uuid)
- Funding UI: `/agent/:id/wallet` deposit tab, `/arm`
## Related
diff --git a/public/changelog.json b/public/changelog.json
index c8f4b5bf0..1bb7d998d 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-16T07:41:13.877Z",
+ "generated_at": "2026-08-16T07:48:38.742Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -16,6 +16,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Agent attestations that stopped indexing now recover on their own",
+ "summary": "An agent's on-chain attestation history is indexed by walking Solana signatures newer than the last one we recorded. If that recorded signature aged out of the RPC node's history, the walk failed outright and kept failing: the same dead signature was replayed on every run, so that agent's attestations silently stopped appearing on its profile while the scheduled job still reported success. The crawler now recognises that case, re-scans from the most recent signatures instead, and clears the stale marker, so an agent that fell behind catches up by itself on the next pass.",
+ "link": null,
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -47,6 +58,17 @@
"docs"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Creator subscription tiers save their edits again, and a mistyped subscription link says so plainly",
+ "summary": "Editing an existing subscription tier from the creator dashboard silently failed: the save never reached the server, so the new name, price or status was lost every time. Saving works now. Alongside it, a mistyped or truncated subscription or tier link used to answer with a generic server failure; it now says the id is not valid, which is what a reader can actually act on. Tier pages are also directly addressable, so a single tier can be linked and read on its own, with unpublished drafts still visible only to the creator who wrote them.",
+ "link": null,
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -173,6 +195,38 @@
"fix"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "The agent wallet MCP server now quotes its own address when it asks an agent to pay",
+ "summary": "Agents that connect to the wallet server at /api/mcp-agent without a three.ws account can pay per call in USDC instead. The payment request it handed back named the main three.ws MCP server, not itself, so a paying agent signed a payment scoped to an endpoint it had not called and service directories listed the wallet server under the wrong description and tool list. It now describes itself: its own address, its own wallet-and-payments summary, and a directory example that only searches for services rather than spending anything. Separately, the one-sentence agent builder no longer mangles accented names when it suggests a handle: Munz now becomes munz rather than mu-nz.",
+ "link": "/docs/mcp-agent",
+ "tags": [
+ "fix"
+ ]
+ },
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "The creations gallery now counts every creation a creator has made, and pages all the way to the end",
+ "summary": "The gallery ranked creators and paged the feed over only the newest 120 creations, however many the feed actually held. A creator's older work was invisible in their profile count, the top-creator board scored people on a fraction of their output, and scrolling the gallery dead-ended early with items still left to show. It now reads the full feed depth it always meant to, and does it in two database round trips instead of two per item, so the deeper read loads faster than the shallow one did.",
+ "link": "/creations",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "The KOL, Loom and marketplace MCP servers now tell you why a call failed, and ship runnable examples",
+ "summary": "When a market-data provider was rate-limited, these servers passed back only a bare code like provider_unavailable and threw away the sentence explaining it. They now surface the full reason. The KOL portfolio tool used to answer a provider outage with an empty card that read as a quiet wallet with no trades; it now reports the outage as an outage, so nobody sizes up a trader from a blank. The KOL and Loom packages also gained runnable examples that talk to the live public API, and the naming SDK now answers an unregistered .eth name the same way it answers an unclaimed .sol one, with data instead of an exception.",
+ "link": null,
+ "tags": [
+ "fix",
+ "sdk"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -195,6 +249,17 @@
"infra"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "The sniper trade journal starts recording, and three sniper readouts stop reporting the wrong number",
+ "summary": "The trade journal is the surface that answers why an agent bought and why it sold, and it had never recorded a single line. Two halves of the same mistake: the table expected a plain number where the platform stores an identifier, so every write failed and was silently discarded on purpose (a journal write must never be allowed to break a trade), and the page that reads it asked the database to compare the same two mismatched kinds of value, which failed outright and returned an error rather than an empty journal. Both are fixed and the surface now records and reads for real, across the 323 closed positions the fleet had already traded. Three readouts were also stating numbers that were not true. The Exit Lab corpus, asked without an explicit page size, answered with exactly one trade instead of the full 400, so the replay console looked like a fleet that had traded once; it now returns the whole window. The live pre-launch radar tape re-sent every precursor it had already shown, about forty times a minute, so the feed filled with copies of the same event; each precursor is now sent once. And the radar dashboard reported 100 watched wallets, the size of the table it was showing rather than the number it was watching, while the status line beside it reported the real figure; it now counts the wallets and the table says which slice of them it is showing.",
+ "link": "/radar",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -217,6 +282,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Token sentiment reads real pump.fun commentary again",
+ "summary": "The sentiment pulse for a Solana token was reading a pump.fun route that no longer exists, so it scored an empty set and reported every coin as perfectly neutral with full confidence. It now reads the coin's live callouts, the commentary feed the pump.fun coin page renders, and when that source is unreachable and you supplied no text of your own it says so with an error instead of returning a neutral-looking score. The scorer itself was also matching lexicon terms inside longer words, which read 'partnered' as bearish; it now matches whole words and knows the common variants (scammer, rugged, crashing, bought).",
+ "link": "/tutorials/emotion-from-data",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index af593f2fc..b8b68859d 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -14,6 +14,14 @@
<category>fix</category>
<description>The signal marketplace identifies a feed or a subscription by a number. Anything that was not one (a typo, a stray word, an empty box) went straight to the database, which threw the whole query out, so the caller got an opaque &quot;something went wrong&quot; and our alerting recorded a fault that was never a fault. Pausing a feed, killing or resyncing a subscription, and subscribing to a feed each now answer with a plain &quot;that is not a valid id&quot; instead. Separately, the paid live signal stream built its Solscan links from whichever network the request named rather than the one the feed actually publishes on, so a subscriber could be handed devnet explorer links for a mainnet call; the feed's own record now decides, and every proof link lands on the chain the trade really happened on.</description>
</item>
+ <item>
+ <title>Agent attestations that stopped indexing now recover on their own</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-08-16:Agent attestations that stopped indexing now recover on their own</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>An agent's on-chain attestation history is indexed by walking Solana signatures newer than the last one we recorded. If that recorded signature aged out of the RPC node's history, the walk failed outright and kept failing: the same dead signature was replayed on every run, so that agent's attestations silently stopped appearing on its profile while the scheduled job still reported success. The crawler now recognises that case, re-scans from the most recent signatures instead, and clears the stale marker, so an agent that fell behind catches up by itself on the next pass.</description>
+ </item>
<item>
<title>An expired X connection now offers to reconnect instead of sending you to the login page</title>
<link>https://three.ws/walk</link>
@@ -38,6 +46,14 @@
<category>docs</category>
<description>An audit of eight documentation pages against the code they describe turned up four claims that had drifted. The Animations page said the motion-capture library held about 2,000 clips when it actually serves 2,874, so both the intro and the gallery section now quote the real size and point at the count the API itself returns. The selfie-to-avatar page listed the wrong default for the face-morph displacement clamp and credited a single tuning sweep instead of the two that chose it. The avatar-creation walkthrough still told people to pick a body type on the selfie flow, a control that was deliberately removed because it changed nothing, and named the wrong fields on the event the page dispatches. The architecture page now says plainly that the whitelist trust mode is reserved rather than enforced.</description>
</item>
+ <item>
+ <title>Creator subscription tiers save their edits again, and a mistyped subscription link says so plainly</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-08-16:Creator subscription tiers save their edits again, and a mistyped subscription link says so plainly</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Editing an existing subscription tier from the creator dashboard silently failed: the save never reached the server, so the new name, price or status was lost every time. Saving works now. Alongside it, a mistyped or truncated subscription or tier link used to answer with a generic server failure; it now says the id is not valid, which is what a reader can actually act on. Tier pages are also directly addressable, so a single tier can be linked and read on its own, with unpublished drafts still visible only to the creator who wrote them.</description>
+ </item>
<item>
<title>Live stage hosts stop swallowing hyphens, and only confirmed tippers get greeted by name</title>
<link>https://three.ws/stage</link>
@@ -134,6 +150,30 @@
<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 agent wallet MCP server now quotes its own address when it asks an agent to pay</title>
+ <link>https://three.ws/docs/mcp-agent</link>
+ <guid isPermaLink="false">2026-08-16:The agent wallet MCP server now quotes its own address when it asks an agent to pay</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Agents that connect to the wallet server at /api/mcp-agent without a three.ws account can pay per call in USDC instead. The payment request it handed back named the main three.ws MCP server, not itself, so a paying agent signed a payment scoped to an endpoint it had not called and service directories listed the wallet server under the wrong description and tool list. It now describes itself: its own address, its own wallet-and-payments summary, and a directory example that only searches for services rather than spending anything. Separately, the one-sentence agent builder no longer mangles accented names when it suggests a handle: Munz now becomes munz rather than mu-nz.</description>
+ </item>
+ <item>
+ <title>The creations gallery now counts every creation a creator has made, and pages all the way to the end</title>
+ <link>https://three.ws/creations</link>
+ <guid isPermaLink="false">2026-08-16:The creations gallery now counts every creation a creator has made, and pages all the way to the end</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The gallery ranked creators and paged the feed over only the newest 120 creations, however many the feed actually held. A creator's older work was invisible in their profile count, the top-creator board scored people on a fraction of their output, and scrolling the gallery dead-ended early with items still left to show. It now reads the full feed depth it always meant to, and does it in two database round trips instead of two per item, so the deeper read loads faster than the shallow one did.</description>
+ </item>
+ <item>
+ <title>The KOL, Loom and marketplace MCP servers now tell you why a call failed, and ship runnable examples</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-08-16:The KOL, Loom and marketplace MCP servers now tell you why a call failed, and ship runnable examples</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>When a market-data provider was rate-limited, these servers passed back only a bare code like provider_unavailable and threw away the sentence explaining it. They now surface the full reason. The KOL portfolio tool used to answer a provider outage with an empty card that read as a quiet wallet with no trades; it now reports the outage as an outage, so nobody sizes up a trader from a blank. The KOL and Loom packages also gained runnable examples that talk to the live public API, and the naming SDK now answers an unregistered .eth name the same way it answers an unclaimed .sol one, with data instead of an exception.</description>
+ </item>
<item>
<title>The public news feed can no longer be knocked out by a single post</title>
<link>https://three.ws/changelog</link>
@@ -150,6 +190,14 @@
<category>fix</category>
<description>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.</description>
</item>
+ <item>
+ <title>The sniper trade journal starts recording, and three sniper readouts stop reporting the wrong number</title>
+ <link>https://three.ws/radar</link>
+ <guid isPermaLink="false">2026-08-16:The sniper trade journal starts recording, and three sniper readouts stop reporting the wrong number</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The trade journal is the surface that answers why an agent bought and why it sold, and it had never recorded a single line. Two halves of the same mistake: the table expected a plain number where the platform stores an identifier, so every write failed and was silently discarded on purpose (a journal write must never be allowed to break a trade), and the page that reads it asked the database to compare the same two mismatched kinds of value, which failed outright and returned an error rather than an empty journal. Both are fixed and the surface now records and reads for real, across the 323 closed positions the fleet had already traded. Three readouts were also stating numbers that were not true. The Exit Lab corpus, asked without an explicit page size, answered with exactly one trade instead of the full 400, so the replay console looked like a fleet that had traded once; it now returns the whole window. The live pre-launch radar tape re-sent every precursor it had already shown, about forty times a minute, so the feed filled with copies of the same event; each precursor is now sent once. And the radar dashboard reported 100 watched wallets, the size of the table it was showing rather than the number it was watching, while the status line beside it reported the real figure; it now counts the wallets and the table says which slice of them it is showing.</description>
+ </item>
<item>
<title>The sniper's laddered-exit settings can finally be saved</title>
<link>https://three.ws/dashboard/sniper</link>
@@ -166,6 +214,14 @@
<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 sentiment reads real pump.fun commentary again</title>
+ <link>https://three.ws/tutorials/emotion-from-data</link>
+ <guid isPermaLink="false">2026-08-16:Token sentiment reads real pump.fun commentary again</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The sentiment pulse for a Solana token was reading a pump.fun route that no longer exists, so it scored an empty set and reported every coin as perfectly neutral with full confidence. It now reads the coin's live callouts, the commentary feed the pump.fun coin page renders, and when that source is unreachable and you supplied no text of your own it says so with an error instead of returning a neutral-looking score. The scorer itself was also matching lexicon terms inside longer words, which read 'partnered' as bearish; it now matches whole words and knows the common variants (scammer, rugged, crashing, bought).</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>
diff --git a/public/features.json b/public/features.json
index cf4cda591..842ff2e6d 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-16T07:27:00.896Z",
+ "generated_at": "2026-08-16T07:48:38.633Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
@@ -5240,7 +5240,7 @@
{
"path": "/docs/avatar-thumbnails",
"title": "Docs · Avatar thumbnails",
- "description": "Where an avatar's preview image comes from, the one rule every code path obeys (never publish a thumbnail URL whose object does not exist), the crons that keep coverage at 100%, and how to run the backfill yourself.",
+ "description": "Where an avatar's preview image comes from, the one rule every code path obeys (never publish a thumbnail URL whose object does not exist), the crons that keep coverage near 100%, and how to run the backfill yourself.",
"added": null,
"auth": null,
"indexable": true,