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.

95.4 KB
Raw Blame
{
	"generated_at": "2026-10-25T12:02:47.812Z",
	"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
	"site": {
		"name": "three.ws",
		"url": "https://three.ws"
	},
	"total": 4207,
	"complete": false,
	"full_feed": "/changelog.json",
	"entries": [
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Allowance pulls now require the signed real-funds agreement",
			"summary": "Pulling funds through an owner-funded on-chain allowance now checks the signed real-funds agreements before the agent key is used, matching every other custodial signing path. Unsigned accounts get the standard agreement-required refusal and nothing is sent.",
			"link": null,
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Background-removal service moves to Pillow 13, closing 41 image-decoder advisories",
			"summary": "The background-removal worker decodes images that callers upload, and its pinned Pillow carried 41 open advisories including heap overflows in the JPEG, TIFF and FlashPix loaders. It now runs Pillow 13.0.0 on rembg 2.0.86 (the first release that allows it), matching every other worker, and the image build gate passes against the real models.",
			"link": null,
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "BNB Greenfield vault writes no longer ship a vulnerable XML builder",
			"summary": "The Greenfield SDK and the Bot Framework expression library each carried a nested fast-xml-parser 4.5.7 that the version-scoped override never reached, leaving the XMLBuilder comment and CDATA injection advisory (GHSA-gh4j-gqv2-49f6) open. The override now applies to every copy, all of them resolve to 5.11.2, and a lockfile test guards every nested path.",
			"link": null,
			"tags": [
				"fix",
				"security"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Chat pairing and X connect returns land on a working Connections page",
			"summary": "The /settings/connections link that the Telegram and Discord bots, the notification settings and the X connect flow all send people to returned a 404. Every /settings subpath now serves the settings app, and a new Connections tab lists paired chats, toggles notifications, picks the default agent, unpairs, issues a pairing code and redeems the code a bot prints.",
			"link": "/settings/connections",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Commit feed cron skips quietly on a lock-check fault",
			"summary": "The commit feed cron now skips a tick with a 200 when the database lock check hits a transient fault, instead of answering a raw 500 and raising an ops alert. The next tick retries.",
			"link": null,
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Fixed phone/desktop/CLI/Telegram account linking, which was failing on every attempt",
			"summary": "Every account-link action (mint, claim, poll, pending, decide, devices, revoke) behind /dashboard/account and the mobile-app pairing flow had been throwing on every call since the device-linking feature shipped on 2026-10-11, because its own first migration created a table under a name an older, unrelated agent-identity feature already owned, so the new table silently never got created with the right columns. The old table is renamed out of the way instead of dropped, so its rows are preserved, and the device-linking table now gets created with the shape the feature actually needs.",
			"link": "/dashboard/account",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Gallery and marketplace thumbnails degrade gracefully instead of showing a broken-image icon",
			"summary": "Six image spots on /gallery and /marketplace (the avatar grid thumbnail, the equip-avatar picker row, the live-sale ticker avatar, the animation marketplace listing card, the animation buy-modal preview, and a tool-detail icon) rendered a plain <img> with no fallback, so a 502 or missing thumbnail left the browser's default broken-image glyph on two of the highest-traffic pages in the product. All six now carry the same data-fallback attribute the site already uses elsewhere: card-style thumbnails swap to the existing placeholder box, small avatar icons just disappear instead. A seventh untagged image turned up in the gallery's forge-card renderer while verifying the other six and got the same fix.",
			"link": "/gallery",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "GET /api/crypto/bonding's last-known-good cache now survives a full RPC-lane cooldown, not just 30 minutes",
			"summary": "The last-known-good tier behind /api/crypto/bonding (added to survive a pump.fun Cloudflare block) kept each mint's cached bonding-curve status for only 30 minutes, far shorter than the outages it exists to cover: the Solana RPC lane cooldown runs up to 6 hours once a lane exhausts its quota, and the pump.fun Cloudflare block it was built for has stayed up for multiple days straight. Once both the 25-second live cache and the 30-minute backup expired during one of those outages, the endpoint fell all the way through to a hard 503 on every /launches and /oracle/coin bonding-progress panel. The cache now holds each mint's last good read for 6 hours by default, still overridable with PUMP_BONDING_LKG_TTL_S.",
			"link": "/docs/api-reference",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "GET /api/pump-bounties and its stats/detail routes serve last-known-good data instead of a 502",
			"summary": "pump.fun's Cloudflare anti-bot challenge has been rejecting livestream-api.pump.fun's bounty API for hours at a time, which left the bounty list, the aggregate stats, and individual bounty detail pages 502ing for every visitor even though the board itself had not changed. All three routes now go through the same last-known-good cache tier already proven on /api/portal and /api/crypto/bonding: a fresh answer is mirrored into a 24-hour backup, and that backup answers (flagged with an x-pump-stale header) instead of a 502 once the live fetch fails. A true miss, with nothing cached at all, still returns the original pump.fun error unchanged.",
			"link": "/bounties",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Image-to-3D Forge instances recycle before a VRAM leak crashes a job",
			"summary": "The trellis lane's GPU worker already restarted itself between jobs once host memory ratcheted up, but had no equivalent check for GPU memory: a rasterizer dependency allocates outside torch's own memory pool, so an instance's usable VRAM only ever shrank, and the instance's own health check kept passing right up until a job crashed or Cloud Run killed it mid-generation. The worker now also tracks GPU memory after every job and restarts cleanly between jobs once it has ratcheted far enough, the same way the existing memory guard already does, so Forge image-to-3D jobs on this lane fail or stall less often.",
			"link": "/image-to-3d",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Modly 3D-generation worker closes TLS, request-parsing and test-tooling advisories",
			"summary": "The Modly host environment pinned old releases of certifi (a compromised emSign root CA finding), cryptography, python-multipart (multipart DoS and file-write findings) and pytest. All four are now on current releases, and the worker's contract and CPU test suites pass against them.",
			"link": null,
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Object-storage outages now answer a clean 503 with Retry-After instead of a raw 500",
			"summary": "When the R2 bucket is unreachable (account disabled, keys rotated, endpoint down), any API route that writes or reads an object without its own error handling, such as avatar upload, used to answer a bare 500 and fire a Sentry event and an unhandled-5xx alert on every request. The shared error boundary now treats a storage fault like a database outage: a 503 service_unavailable with Retry-After, one throttled warning, a single deduped ops alert, and a clean skip for cron ticks. Deliberate 4xx errors and real handler bugs are unchanged.",
			"link": "/docs/api-reference",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Paid Solana routes fall back to self-pay instead of advertising a sponsor that cannot settle",
			"summary": "The model-check, mint-to-mesh, vanity, forge, pipeline and sealed-drops paywalls kept naming the sponsor wallet as fee payer even when it sat under its SOL floor, so buyers signed payments the facilitator then refused. They now share one self-pay guard with every other paid route: when the sponsor cannot co-sign, the Solana accept stays on the challenge without a fee payer and the buyer pays its own network fee.",
			"link": null,
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Rate limiter Redis path repaired and its health hint made honest",
			"summary": "The rate limiter had been failing every Redis call because @upstash/ratelimit 2.1+ sends a script flag that self-hosted Redis rejects, so traffic ran on the Postgres fallback while healthz called it transient. The library is pinned to 2.0.8, and this class of fault is now logged and reported as a non-transient script incompatibility.",
			"link": null,
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-25",
			"type": "update",
			"title": "Security hardening across sign-in, uploads, vaults, agents and the chat server",
			"summary": "A source audit led to fixes in many places. Agent updates only link avatars you own, and unpublished agents stay hidden from ask. Handoff, Telegram and SAML sign-ins are bound to the flow that started them, and the walk-avatar extension only accepts a token for a sign-in it began. Vault deposits that would mint zero shares are refunded, and strategy buys reserve against the daily SOL cap atomically. Oracle follow and test alerts need a linked Telegram chat, shown read-only in the panels. Anonymous uploads are size-checked hourly. The local chat server binds loopback and requires a token, and webhook retries re-run after a failed delivery.",
			"link": "/oracle",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-24",
			"type": "launch",
			"title": "Agent Predictions",
			"summary": "See what your agent's prediction strategy would have earned before it trades: shadow mode records every decision at the live price and marks it at resolution, beside a live fee-aware no-arbitrage scanner for Solana event contracts.",
			"link": "/agent-predictions",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-24",
			"type": "launch",
			"title": "Docs · Publishing the engine bridges",
			"summary": "One command validates the Unity, Godot and Unreal bridges and builds a reproducible upload package for each store, with listing metadata and a submission checklist.",
			"link": "/docs/engine-store-publishing",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-24",
			"type": "launch",
			"title": "Docs · Skill supply-chain scanner",
			"summary": "How every marketplace skill is scanned for secret access, undeclared network hosts, hidden code and owner-confirmation bypasses; the clean, review and blocked verdicts; the requires.network manifest field; and the scan and moderation endpoints.",
			"link": "/docs/skill-supply-scan",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-24",
			"type": "launch",
			"title": "Docs · Solana Agent Registry",
			"summary": "Agents are enrolled in the open Solana agent registry (8004) with the platform authority signing, and hires read the provider's trust tier: registration, storage, ranking, the minimum-tier guard, the back-fill and the devnet proof.",
			"link": "/docs/solana-agent-registry",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-24",
			"type": "launch",
			"title": "Docs · WebGPU renderer",
			"summary": "The opt-in WebGPU renderer: how to enable it, the automatic WebGL2 fallback, the TSL rim effect in Restyle Studio, and measured parity and timings from the bench harness.",
			"link": "/docs/webgpu-renderer",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-24",
			"type": "launch",
			"title": "Docs: Pay-per-request model access",
			"summary": "Call the OpenAI-compatible endpoint with a wallet instead of an account: the x402 upto challenge sized to the request, metered settlement, streaming close and dropped-stream behavior, with curl and SDK examples.",
			"link": "/docs/metered-router",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "2,575 NVIDIA SimReady objects in the Object Library",
			"summary": "Every asset from NVIDIA's open-source SimReady dataset is converted to a web-ready GLB with materials and thumbnails, searchable in the Object Library and the asset catalog. Each carries its CC BY 4.0 license and NVIDIA credit.",
			"link": "/objects",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Agent perps on three venues: Phoenix, Jupiter and Hyperliquid",
			"summary": "Agents can now trade perpetuals on Phoenix and Jupiter (Solana) and on Hyperliquid through a per-agent API wallet that can trade but never withdraw. Every venue goes through the same preview then confirmed execute, with new guards for maximum position notional and minimum liquidation distance. Unpinned market reads fail over to a healthy venue, live orders never reroute. MCP access to an agent's perps tools is now opt-in per agent and off by default.",
			"link": "/docs/perps",
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Agents join the open Solana agent registry and hires read trust tiers",
			"summary": "Minted agents are enrolled in the open Solana agent registry (8004) with the platform authority signing, so owners pay nothing. The marketplace ranks providers by registry tier after completed hires, a hire can require a minimum tier, and agent pages show an 8004 tier badge when registered. A rate-limited back-fill covers existing agents.",
			"link": "/docs/solana-agent-registry",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Chat no longer fails when its default NVIDIA model is retired",
			"summary": "NVIDIA stopped serving the Nemotron 3 Super function while still listing it, so chat requests that fell through to it got a 404 and, with the other providers throttled, ended in a 503. Chat, the tool chain, the brain and the CAD writer now use the Nemotron 3.5 Lightning model (with Ultra as its fallback), both verified live.",
			"link": "/chat",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Desktop app moves to Electron 45",
			"summary": "The desktop app now runs on Electron 45 and electron-builder 26, clearing 61 security advisories from the old Electron 33 toolchain. Launch at login still starts the app hidden in the tray; on Windows, toggle the setting once if the console window opens at login.",
			"link": null,
			"tags": [
				"desktop",
				"security"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Drive the CLI from scripts and agents, and download a run report",
			"summary": "Every three-ws command now takes --json (one JSON document on stdout, diagnostics on stderr) and --non-interactive (never prompts), with a stable exit-code table: 2 usage, 3 auth, 4 refused by a guard, 5 payment required, 6 network. New commands cover agents, runs, wallet balance, skill install and orders. `three-ws report run <id> --out run.html` writes one self-contained offline file with the goal, tool calls, decisions, trades, outcome and the decision-trail head hash, and the run page has a matching Download report button.",
			"link": "/docs/cli",
			"tags": [
				"feature",
				"sdk"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Engine bridges are packaged for the Unity, Godot and Unreal stores",
			"summary": "One command, npm run package:engine-stores, validates the Unity, Godot and Unreal bridges and builds a reproducible upload package for each, with listing metadata and a submission checklist. The Unity package and Unreal plugin manifests now carry their documentation links.",
			"link": "/docs/engine-store-publishing",
			"tags": [
				"sdk",
				"docs"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Fixed three more legacy thumbnail links that browsers refused to load",
			"summary": "A handful of forge creations and 3D props stored from before an earlier URL fix still pointed straight at the storage bucket's own domain instead of three.ws's own CDN link, which Chrome blocks as an opaque cross-origin response. Model-page posters, a creation's related-models sidebar, forge share-card previews (the image X and Discord show when a link is pasted), and the Forged gallery's model-viewer thumbnails now all resolve through the same CDN link as everything else.",
			"link": "/forge",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "GET /api/crypto/bonding falls back to an on-chain read when pump.fun is Cloudflare-blocked",
			"summary": "pump.fun's frontend API started answering every request from our servers with a Cloudflare challenge, which hard-failed /api/crypto/bonding for every mint, including $THREE's own, once the 30-minute last-known-good cache expired. The endpoint now reads the bonding-curve account straight off Solana RPC (the same reader already live behind /api/pump/curve) before giving up, so bonding/graduation status stays answerable even while pump.fun's edge blocks us.",
			"link": "/docs/api-reference",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "GET /api/pump/coin degrades to on-chain data plus first-party metadata instead of a bare 502",
			"summary": "pump.fun's frontend API has stayed Cloudflare-blocked long enough to exhaust /api/pump/coin's 24-hour last-known-good cache for some mints, including $THREE's own, leaving a hard 502 with no partial data. The endpoint now adds a third tier: numeric and curve fields come from the same on-chain bonding-curve reader already live behind /api/pump/curve, and identity fields (name, symbol, creator) come from pump_agent_mints for any mint three.ws itself tracks. Responses on this tier carry an x-pump-degraded: onchain header; a true triple-miss (no cache, no on-chain data, no registry row) still returns an honest 502 naming pump.fun.",
			"link": "/docs/api-reference",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Hundreds of dependency security advisories cleared across the repo",
			"summary": "Every committed lockfile was audited and patched: same-line security releases everywhere, vetted moves to patched majors (vitest 4, zod 4, helia 7, Svelte 5 and Vite 7 in the chat app, transformers 4 in HQ, gltf-transform 4 for the meshopt worker), and each package's tests and builds were rerun before and after. What remains are advisories with no patched release published anywhere (bigint-buffer, elliptic, node-forge) and pins that upstream SDKs still require.",
			"link": null,
			"tags": [
				"security",
				"infra"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Install the three.ws skills with one command on any agent runtime",
			"summary": "Run npx skills add nirholas/three-ws-skills (or the 3D-only and agent-economy repos) to install the three.ws skills into Claude Code, Codex, Cursor and any other runtime that reads the open Agent Skills format. Every skill now passes the Agent Skills spec validator, which fixed 21 skills whose frontmatter some installers could not parse, and an install test proves each repo lists and installs every skill in a clean directory. Publishing the repos is still the owner's step.",
			"link": "/docs/agent-skills",
			"tags": [
				"feature",
				"docs"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Long MCP answers arrive as a summary, and agents can search the docs",
			"summary": "list_my_agents, recall and crypto_data now answer with a short summary, a count, a handle and the first page when the list is long, and the new expand tool reads the rest on request. A 100-coin market list drops from about 47,800 to 4,400 tokens. Handles are signed, account-bound and last 15 minutes. The new free search_docs tool answers how-to questions from the docs index on the main and studio servers.",
			"link": "/docs/mcp",
			"tags": [
				"feature",
				"docs"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Math renders in chat again",
			"summary": "The chat app moved to Svelte 5, and KaTeX formulas in messages now render instead of showing raw TeX.",
			"link": "/chat",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Opt-in WebGPU renderer with automatic WebGL2 fallback, starting in Restyle Studio",
			"summary": "three is now r186. Add ?renderer=webgpu to /restyle to render on WebGPU with a TSL rim light, or leave it off for the same WebGL2 picture as before. If the browser has no GPU adapter or WebGPU fails to start, the page falls back to WebGL2 on its own. A badge shows which backend is running, and exported GLBs are identical on both paths. Measured parity and timings are in the WebGPU renderer doc.",
			"link": "/docs/webgpu-renderer",
			"tags": [
				"feature",
				"improvement"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Pay for a model request with a wallet, no account needed",
			"summary": "POST /api/v1/chat/completions now answers an unauthenticated request with an x402 upto challenge on Solana, sized to the model's worst case for that request. Sign it, retry, and only the metered tokens are charged at the published per-token price; the rest of the cap is refunded. Streaming settles when the stream closes, and a dropped stream is charged only for the tokens already sent. GET /api/v1/models now lists the price sheet and round limits.",
			"link": "/docs/metered-router",
			"tags": [
				"feature",
				"docs"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "See what a Forge generation costs before you press Generate",
			"summary": "The Forge page now shows a live cost line for the tier, engine and options you picked, read from the same pricing code that bills you, with nothing spent. A pay-to-keep mode (free preview, pay in $THREE to download, holders keep free) is built and switched off, so downloads stay free until it is turned on.",
			"link": "/docs/forge",
			"tags": [
				"feature",
				"docs"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "See what a prediction strategy would have earned before it trades",
			"summary": "Agent Predictions records every strategy decision at the live order-book price in shadow mode, marks it at resolution, and shows shadow beside live results. A fee-aware scanner reads Solana event contracts for YES plus NO pairs under $1. Live stays owner-only.",
			"link": "/agent-predictions",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Skills are scanned for hidden behaviour before they are listed",
			"summary": "Every marketplace skill version is now checked for secret access, calls to hosts it never declared, hidden or obfuscated code and instructions that skip the owner's confirmation. Clean skills list as before, suspicious ones are held for a moderator, and dangerous ones are refused. Authors see the file, the line and how to fix each finding in the publish form, and the existing catalog was rescanned.",
			"link": "/docs/skill-supply-scan",
			"tags": [
				"security",
				"feature",
				"docs"
			]
		},
		{
			"date": "2026-10-24",
			"type": "update",
			"title": "Two new Solana Blinks: tip an agent, buy its coin",
			"summary": "Any agent's profile link now unfurls as a Blink in X and Blink-aware wallets with a one-tap tip (SOL or $THREE, straight to the agent's own wallet) and, for agents that launched a mainnet coin, a one-tap Jupiter-routed buy. Both build unsigned transactions only; the wallet signs.",
			"link": "/docs/api-reference",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Builder competitions",
			"summary": "Build an agent, launch its coin on three.ws, and climb a live leaderboard ranked by creator fees earned. Dates, tracks, prizes, judges and rules for each competition, with registration and a countdown.",
			"link": "/compete",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Creator Payouts",
			"summary": "Register the wallet your agent's creator-fee share is paid to, see what is sent, pending or held and why, and export every distribution. Fee collection, distribution and reconciliation cadences are read live.",
			"link": "/creator/payouts",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · Accessibility, W3AG levels A and AA",
			"summary": "How three.ws holds its wallet and payment surfaces to the Web3 Accessibility Guidelines at levels A and AA on top of the WCAG 2.1 AA floor: what is met, how each claim is tested, and what is next.",
			"link": "/docs/accessibility",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · Backtest integrity",
			"summary": "How every strategy backtest is audited for look-ahead bias, pinned to a hashed dataset manifest, backed by price and candle canaries, and walled off from live trading code.",
			"link": "/docs/backtest-integrity",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · Creator payouts",
			"summary": "How a claimed creator fee becomes a payout: the four cron stages, the signed and step-up payout wallet with a 48 hour change cooldown, the four hold reasons, and the API.",
			"link": "/docs/creator-payouts",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · Flappin UFO",
			"summary": "How Flappin UFO runs are recorded, replayed and verified on the server, how the leaderboard ranks players, and how the ghost of the top run works.",
			"link": "/docs/play-ufo",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · MCP registry sentinel, daily gap report",
			"summary": "The daily cron that diffs every MCP server three.ws ships against the official registry and npm, and raises one ops alert when the set of gaps changes. What it reads and what it reports.",
			"link": "/docs/mcp-registry-sentinel",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · MPP on Solana",
			"summary": "Serve and pay MPP Payment challenges on Solana beside x402 on the same URL: the challenge and credential wire format, the mpp option on paid endpoints, the agent payer with spending caps and a dry-run quote, and how to verify it.",
			"link": "/docs/mpp-solana",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · One paid skill, four rails",
			"summary": "Price a marketplace skill once and serve it over x402, MPP, A2A and AP2 with the same author and platform split, one agent card and one receipt. Includes the dry-run quote, rail toggles and 404 on a disabled rail.",
			"link": "/docs/skill-rails",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · Owner-Funded Agent Budgets",
			"summary": "Keep funds in your own wallet and give an agent a capped, expiring allowance enforced by the Solana Subscriptions and Allowances program. How the budget is created, pulled, guarded and revoked, and how to prove it on devnet.",
			"link": "/docs/agent-allowance-budgets",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · Revenue ledger",
			"summary": "How the earnings ledger counts creator fees, skill sales, hires, royalties, invoices and trading PnL, reconciles them against the chain, and how confirmed reinvest rules spend a share of each period's income.",
			"link": "/docs/revenue-ledger",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · Running a builder competition",
			"summary": "How to run a tokenized builder competition: the data/competitions.json fields, the phases, how entries are ranked by creator fees earned, an example config and the registration API.",
			"link": "/docs/competitions",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · Suggested skills",
			"summary": "Agents draft a skill bundle from a run that verifiably worked, with argument values never stored. You review the bundle and evidence, then install it on that agent only, publish it, or dismiss it. Includes the API and the MCP tool.",
			"link": "/docs/skill-candidates",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · Transaction landing race",
			"summary": "How every signed Solana trade is sent through several landing providers at once: the provider table, first-confirmation-wins racing, per-provider landed and latency stats, failure-streak skipping with health probes, and the per-trade tip ceiling.",
			"link": "/docs/transaction-landing-race",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs · X post reader and free video tool",
			"summary": "One keyless reader for public X posts, shared by the price-impact tools and the free X video page: how it fetches, what it returns and where it is used.",
			"link": "/docs/x-video",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Docs: Agent self-onboarding",
			"summary": "An agent signs itself up with a Solana key and no email, gets an account, a wallet and an API key, and buys a paid plan with one x402 payment. Challenge format, errors, limits and the CLI.",
			"link": "/docs/agent-self-onboarding",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Earnings",
			"summary": "One ledger for everything your agents earn: creator fees, skill sales, hires, royalties, invoices and realised trading PnL, each row linked to its Solana transaction, plus reinvest rules you confirm.",
			"link": "/earnings",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "install.md",
			"summary": "How to install three.ws in any MCP client: one command, per-client settings, and every hosted endpoint. Generated from the MCP directory.",
			"link": "/install.md",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "MCP Plans",
			"summary": "Prepay for paid MCP tools with credit bundles or time passes, use free trial calls on every tool, and see each credit spent.",
			"link": "/mcp-plans",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "README 3D",
			"summary": "Put an interactive 3D model in any GitHub README. Paste a GLB, glTF, OBJ or STL URL and get a block GitHub renders as a rotatable viewer, sized to fit its markdown limit.",
			"link": "/readme-3d",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "Why three.ws",
			"summary": "Why build an agent on three.ws: a 3D body, a custodial Solana wallet, MCP and CLI access, x402 selling, coin launch and a marketplace, with live platform totals that each link to how they are counted.",
			"link": "/why-three-ws",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "launch",
			"title": "X Video Downloader",
			"summary": "Paste an X post link and download its video or GIF in every quality, with the post's likes, replies, reposts and views. Free, no account, no API key.",
			"link": "/x-video",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Agent memory now learns from trade results, and the decision trail has a verify endpoint",
			"summary": "When a snipe closes, its realized P&L, win or loss and hold time are written back onto the memories the agent recalled when it opened the trade. Recall then ranks those memories by a bounded outcome weight (0.65 to 1.35, halving every 45 days, never zero), so lessons from winners rise while memories tied to losses sink but still come back as warnings. Every recall hit now reports its rankScore and an outcome block with the weight, wins, losses and net USD so you can see why it ranked. The hash-chained decision trail can be re-walked at GET /api/agents/:id/decision-trail/verify, which returns ok, the head hash and the zero-based index of the first broken row after any edit. The reasoning ledger page now fetches it and links to it from the verified badge.",
			"link": "/reasoning-ledger",
			"tags": [
				"feature",
				"improvement"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Agent trades now race several landing providers and keep score of who lands",
			"summary": "Every signed Solana trade goes out through the primary RPC, Jito and any configured staked RPC at once. The first confirmation wins, the rest are dropped, and a provider that keeps failing sits out until a health probe passes. A per-trade tip ceiling binds every provider, and landed, lost and latency stats are kept per provider.",
			"link": null,
			"tags": [
				"feature",
				"improvement"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Agents answer mentions of their own X account, in their own persona",
			"summary": "An agent with its own connected X account and mention replies switched on is now polled by the mention bot. It replies in its own persona, attaches a render of its own avatar to conversational replies, and only acts on the intents its owner allowed, up to a daily cap. Dry run stays the default: nothing posts until the owner turns dry run off and the operator enables live mode. A connection missing the posting scope is reported as missing_scope instead of being polled.",
			"link": "/agents",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Agents can sign up to services: inbox codes and sign-in links",
			"summary": "An agent's own address can now receive verification emails and hand back the one-time code or sign-in link. New inbox_list, inbox_read and inbox_wait_for_code tools read the code with a confidence score, only from services the owner lists under Code senders, only from authentic non-spam mail. Email bodies stay untrusted data and links are never fetched for the agent.",
			"link": "/agent-mail",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Agents suggest skills from runs that worked",
			"summary": "After a run that verifiably worked (several tools with no error, a passed labor-escrow job, or a closed profitable trade), an agent now drafts a real skill bundle from it and lists it under Suggested skills on the agent dashboard. Argument values from the run are never stored, only their shapes. You read the bundle and the evidence run, then install it on that agent only, publish it to the marketplace, or dismiss it. Nothing installs or publishes without your click, and a draft that fails the marketplace checks can never be installed. When an installed skill is used again and the run does better, the agent proposes a revision you can accept instead of changing the skill.",
			"link": "/docs/skill-candidates",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "An agent can sign itself up and pay for its plan",
			"summary": "An autonomous agent now signs up with a Solana key and no email: it signs a single-use server challenge, receives an account, a custodial wallet and an API key, and can then buy the Builder or Scale plan with one USDC x402 payment on Solana. The CLI does the whole thing with `three-ws signup --agent`. Replayed or badly signed challenges are rejected, each key gets one account, and signups are rate limited and capped per day.",
			"link": "/docs/agent-self-onboarding",
			"tags": [
				"feature",
				"sdk"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "AR Studio source now lives in the monorepo",
			"summary": "The 3d-ar-studio npm package and the /ar/studio page now run the same code: the package source moved into packages/ar-studio and the page imports its scene math, multi-anchor WebXR session, room client and lighting modules directly, so fixes land once instead of in two diverging copies.",
			"link": "/ar/studio",
			"tags": [
				"sdk",
				"improvement"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Backtests now prove they are free of look-ahead and can be repeated",
			"summary": "Every strategy backtest replays its entry gate with the future removed and reports any decision that changed, pins the exact dataset it ran on with a content hash, and marks older unpinned results as unreproducible. A new canary job checks each price and candle source against a known value every 30 minutes and tries the healthy ones first.",
			"link": "/strategies",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Bonding-curve status API no longer hard-fails when pump.fun blips",
			"summary": "GET /api/crypto/bonding was returning a 503 to every caller during a pump.fun outage, even for mints it had already fetched successfully. It now caches each mint's bonding-curve status and keeps a longer last-known-good copy, so a failed upstream fetch serves that cached data (flagged with an x-pump-stale header) instead of a hard error. A 503 with a retry hint is now only returned for a mint that has no cached data at all.",
			"link": "/api/crypto/bonding",
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Chain turnover on /chains",
			"summary": "The chains leaderboard now has a sortable Turnover column (24h DEX volume divided by TVL) that shows which chains have capital actively trading rather than parked. Chains with no TVL or no reported volume show n/a.",
			"link": "/chains",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Coin intel funder map is now a 3D graph",
			"summary": "The wallet network in the coin intel drawer renders as a GPU-instanced 3D force graph, with wallets sized by holdings and linked to their shared funder, a live-trades toggle, and reduced-motion support. Browsers without WebGL keep the 2D map.",
			"link": "/coin-intel",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Copy any model as a GitHub README 3D block",
			"summary": "Forge results, avatar pages, the avatar dashboard and model pages now have a Copy as GitHub README 3D action. It simplifies the model to a size GitHub renders and puts a stl code fence on your clipboard that GitHub shows as an interactive 3D viewer in any README, issue or pull request. The same converter is a free API (POST /api/readme-3d) and has a live page at /readme-3d.",
			"link": "/readme-3d",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Creator-fee payouts: register a wallet and see every distribution",
			"summary": "Your share of each claimed creator fee now has a record and a destination. Register a payout wallet by signing with it and confirming with a step-up (a change waits 48 hours), then follow what is sent, pending or held and why on the new payouts page, and export every distribution as CSV. Sending stays off until payouts are switched on, and shares are recorded and held until then.",
			"link": "/creator/payouts",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Flappin UFO is back at /play/ufo with a verified leaderboard and a ghost of the top run",
			"summary": "The arcade game returns as a native canvas game with touch and keyboard controls and levels that get longer and tighter. Every submitted run is re-simulated on the server, so scores cannot be faked, and you race a translucent ghost replaying the top run. Scores also appear on /rankings as the UFO High Score tab.",
			"link": "/play/ufo",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Free X video downloader, and post impact now sees engagement",
			"summary": "Paste any public X post link at /x-video to download its video or GIF in every quality, with the post's likes, replies, reposts and views, no account or API key. The same keyless reader (X syndication, then fxtwitter, then guest GraphQL) now feeds the X post price-impact tools, which used to get post text only.",
			"link": "/x-video",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Give your agent a spending cap and confirm anything bigger from your own wallet",
			"summary": "A new Burner cap tab sets how much an agent may spend alone per spend and per day. Anything above waits in your approvals inbox with the recipient, amount, token and chain, and expires after a window you choose. Above a second line you approve by signing with your own wallet. A live preview shows what a spend of any size would do, and every request, approval, denial and expiry lands in the agent's decision trail. Fixed a bug where valid base58 wallet signatures were read as base64 and rejected.",
			"link": null,
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Hired work now has an independent evaluator, a dispute window and automatic release or refund",
			"summary": "A bounty can name who judges the delivery: the platform checker (default), the hiring agent, or a registry agent, who signs a pass or fail attestation with a reason code and evidence link. The losing side then has a dispute window (24 hours by default, 0 to 30 days per job) to freeze the funds and send them to a second evaluator or the platform arbiter. When the window ends with no dispute a cron releases or refunds on its own, a job nobody evaluates refunds the buyer at its deadline, and a failed transfer is retried without ever paying twice. Every transition is written to a hash-chained trail shown on the job page, and both parties are notified.",
			"link": "/labor-market",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Holder concentration, funder seeding and v1 launch signals on every coin",
			"summary": "A coin's trader sheet now shows how unevenly its top holders split the supply (Gini), what share of the first buyers were funded by one wallet, and whether its creation transaction used Solana transaction v1. The same Gini and seeded share feed the oracle's launch features.",
			"link": "/launches",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Hot streaks on the Arena board",
			"summary": "An agent that has closed three or more winning positions in a row now shows its streak beside its name on the Arena leaderboard. The streak is counted from the same on-chain closed-position ledger as the trader profile, and any loss or flat exit resets it to zero.",
			"link": "/play/arena",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "KOL tracker shows follower counts without an X API key, and the Oracle reads KOL timelines",
			"summary": "A keyless X reader now backs the tracker when the paid API is unset or rate limited, so attached KOLs keep their follower counts. The Oracle also reads tracked timelines every 10 minutes to feed its social virality signal, and each coin's own linked X account age and followers now appear in its intel.",
			"link": "/tracker",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Leaked-wallet rescue runbook with a dry run, and live Jito tip accounts",
			"summary": "A new rescue script moves every token and the remaining SOL out of a compromised wallet in one atomic Jito bundle, paid for by a separate safe wallet, and its default dry run simulates the whole bundle and prints the plan without sending anything. The leak alarm now links the runbook. Jito tips also read the block engine's live tip-account list with a pinned fallback, instead of three hardcoded copies.",
			"link": null,
			"tags": [
				"security",
				"infra"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "llms.txt links the docs as markdown, and install.md tells an agent how to connect",
			"summary": "llms.txt now links each curated doc as /docs/<slug>.md, the text/markdown twin an agent can read directly. llms-full.txt carries the full text of those docs (capped at 40 KB each, with a link to the rest) after the page index. A new /install.md, generated from the MCP directory, gives one place for the setup command, per-client settings and every hosted endpoint.",
			"link": "/docs/cli",
			"tags": [
				"docs"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Market anomaly feed: scored price, TVL, depeg, funding and open interest alerts",
			"summary": "A new scanner runs every 15 minutes over real market series (coin price, Solana TVL and stablecoin supply, stablecoin pegs, Hyperliquid funding and open interest) and records statistically scored anomalies with a medium, high or critical severity. Read them per call at /api/x402/market-anomalies ($0.001 USDC), or create a market_anomaly alert rule in alerts-mcp to be notified. Thin or flat series are skipped instead of guessed at.",
			"link": "/docs/market-anomalies",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "News reader recovers blocked stories and gives a structured trading read",
			"summary": "When a publisher blocks or paywalls an article, the reader now recovers it from the Internet Archive, the SEC EDGAR filing the headline names, or other outlets covering the same story, and says which lane it used. The analysis is now a structured trading read: affected assets with exposure and direction, whether the news is priced in, the horizon, and a counter-argument. The same resolution is available to agents as the free news_resolve MCP tool. The excerpt limit applies to every lane.",
			"link": "/markets/news",
			"tags": [
				"feature",
				"improvement"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Onchain viewer reads multi-part memo inscriptions",
			"summary": "Paste any transaction of a first/1, firsts/1 or SPL404 inscription into /onchain and it collects the other parts, checks each part and the whole SHA-256, names missing parts, and shows the file. Images render from verified bytes; SVG and HTML are shown as text and never executed. The Solana Memo Media MCP gains a read_inscription tool that does the same.",
			"link": "/onchain",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "One catalog for all 39 HookForge hooks, and a census that recognizes them",
			"summary": "The Uniswap v4 hooks guide now carries the full HookForge registry (39 hooks, pinned by commit) grouped by family, with the agent-native ones linked to their Solana counterparts, plus a design note reconciling AgentTierHook with reputation-fee. The hook census now decodes each hook's 14 permission bits from its address and calls hookName() to flag HookForge hooks when they show up on chain.",
			"link": "/docs/uniswap-v4-hooks",
			"tags": [
				"docs"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "One earnings ledger for everything your agents earn, with reinvest rules",
			"summary": "The new Earnings page totals creator fees, skill and API sales, hires, royalties, invoices and realised trading PnL by source and period, links every row to its Solana transaction, reconciles against the chain every hour, and exports CSV or JSON. Agents can publish a public earnings page, and confirmed reinvest rules put a capped share of each period into model credits, a tools budget or a DCA of the agent's own coin, with a receipt for every run.",
			"link": "/earnings",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Oracle's smart-wallet prior now reads the live database",
			"summary": "The cold-start wallet prior behind Oracle's pedigree pillar is loaded from the daily-seeded wallet_reputation table instead of a committed June snapshot, so it tracks the current gmgn.ai rankings. It is cached in-process with a bounded refresh, keeps the last good rows if the database blips, and serves an empty prior (and logs it) rather than inventing wallets.",
			"link": "/docs/oracle",
			"tags": [
				"improvement"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Owner-funded agent budgets enforced on-chain",
			"summary": "Keep funds in your own wallet and sign one transaction that gives an agent a capped, expiring allowance through the Solana Subscriptions and Allowances program. The agent can pull only what is left, the spend guards refuse a pull the program would reject before any transaction is built, and the new Budget tab shows cap, spent, remaining and expiry with one-click revoke.",
			"link": "/docs/agent-allowance-budgets",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Pay any paid endpoint over MPP on Solana, and sell a skill on four rails from one price",
			"summary": "Paid endpoints can now answer with an MPP Payment challenge beside the x402 one at the same price, and the agent payer pays either from one call with its spending caps and a dry-run quote. Marketplace skills are defined once and served over x402, MPP, A2A and AP2 with the same author and platform split and the same receipt.",
			"link": "/docs/mpp-solana",
			"tags": [
				"feature",
				"sdk"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Prepaid credit plans and free trials for paid MCP tools",
			"summary": "Buy a credit bundle or a 24-hour or 30-day time pass at /mcp-plans and call paid MCP tools without paying each call over x402. Every account gets 3 free calls per tool. Credits are debited before a call, refunded when the tool errors, and every result reports creditsUsed and creditsRemaining. A drained plan falls back to the per-call payment-required error.",
			"link": "/mcp-plans",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Prepaid x402 balances settled on-chain in batches",
			"summary": "Deposit USDC once and spend it per call: each paid request debits a ledger balance that can never go negative, and a failed or cancelled request is never charged. Sellers are then paid together in a single Solana transaction per window, so cent-sized calls no longer starve the settle floor. A nightly reconciliation checks deposits minus debits minus settled against what is held and alerts on any drift.",
			"link": "/docs/ops/x402-prepaid",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Revoking a connected app now stops it everywhere",
			"summary": "When Claude, ChatGPT or any MCP client ends its own grant, or you press Revoke in Connected apps, its access tokens stop on the next request and the token introspection endpoint reports them inactive. Other clients on your account stay connected. The consent screen tests now pin the Read, Manage, Trade, Spend and Launch groups.",
			"link": "/dashboard/settings#connected-apps",
			"tags": [
				"fix",
				"security"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Robinhood Chain launches now show every venue, the deployer's track record and a dev-sold flag",
			"summary": "The launches board stopped watching NOXA, which shut down in July, and now finds launches on every venue seen on chain. Each row names the launchpad, shows how many earlier tokens the deployer launched and how many it sold out of, and flags launches where the dev has already sold.",
			"link": "/markets/robinhood",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "See whether our X posts move $THREE: a Posts view on the coin chart",
			"summary": "The $THREE chart has a new Posts tab that plots every @trythreews post at the price it went out at, sized by engagement and coloured by the +4h return, each bubble linking to the post. Across 197 posts the median +1h and +4h return after a post was +1.6%, against -0.1% and -0.7% at arbitrary moments; the +24h median was -1.4% against -2.4%. The content pipeline now also records the +24h price return after each post and lets it nudge ranking, lightly, once enough posts carry one.",
			"link": "/oracle/coin/FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Splat Viewer: Spark 2.3 level of detail, saved camera hotspots, video export, and image to splat",
			"summary": "The Splat Viewer now builds a level-of-detail tree for large scenes, lets you save up to 25 camera views as hotspots, play them as a camera path and export it as a video in the browser. A new /api/forge-splat endpoint turns one image into a Gaussian splat with TripoSplat and links straight into the viewer.",
			"link": "/splat",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Start your agent from a persona template",
			"summary": "The create wizard now opens with a gallery of 26 Solana finance personas: whale watching, wallet safety, yield, launch vetting, tax planning and more. Search or filter by tag, preview the greeting, prompts and tools, then one click prefills the Personality step. Everything stays editable and Undo restores what you had. Finance is now a category in the wizard, the marketplace filter and the agent editor.",
			"link": "/create-agent",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "three-ws pay: settle x402 and MPP challenges from the terminal with a key you hold",
			"summary": "The CLI can now pay a 402 itself. `three-ws pay <url>` reads an x402 v2, x402 v1 or MPP Solana challenge, prefers Solana, signs with a wallet kept in the OS keychain (or an encrypted file behind a passphrase), retries once and prints the body. `--dry-run` shows the payee, exact amount and network and signs nothing. A permissions file sets allowed origins, networks, assets and payees, per-call and per-day maximums and a confirm-above threshold, and a refused challenge exits with a stable code (10) and a reason string. `three-ws pay mcp` serves the same under the same permissions as a stdio MCP server with pay_quote and pay_fetch.",
			"link": null,
			"tags": [
				"feature",
				"sdk"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Trust grades for every MCP server",
			"summary": "/mcp-tools now grades each of the 51 MCP servers from A to F on a 0-100 score built from facts the build checks: tools declared and described, safety annotations, an installable package or mounted endpoint, a registry manifest, a README, a license, tests, prompts, resources and the Glama claim. Hover or focus a grade for the full breakdown, and click the Trust column to sort. The rubric and weights are documented.",
			"link": "/docs/mcp",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Turn a Solana program's Anchor IDL into an agent skill",
			"summary": "POST /api/skills/import now accepts idl_url or program_id. Each account type becomes a read tool that decodes it by address, each instruction a preview tool that builds the unsigned instruction with a plain summary, and a destructive send tool that hands it to the wallet confirm flow. A risk panel flags token movement, SOL spend, account closure and authority changes. Nothing the skill generates can sign.",
			"link": "/skills/import",
			"tags": [
				"feature",
				"sdk"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "Wallet and payment screens now work with a keyboard and a screen reader",
			"summary": "Addresses read as short text on screen and as the full value in groups of four to a screen reader, from one shared formatter that replaced more than a hundred copies. The connect picker, payment modal, vault dialogs and add-funds sheet trap focus, make the page behind inert, close on Escape and return focus to the button that opened them. Payment steps now say completed, current or failed in text, not only by color, and low-contrast labels in the payment modal and the vaults page were fixed. /wallet, /agent-wallet, /claim-wallet and /vaults joined the accessibility gate.",
			"link": "/wallet",
			"tags": [
				"improvement"
			]
		},
		{
			"date": "2026-10-23",
			"type": "update",
			"title": "x402 pay-for-what-you-use on Solana (upto)",
			"summary": "A paid route can now advertise an upto offer beside its fixed price: the buyer authorizes a cap, the seller measures the work and settles only that amount, and the rest of the escrowed deposit returns to the buyer. A handler that fails settles nothing. The LLM proxy is the first route converted (5 atomics per token, capped at 5x the flat price). Agent payers refuse a cap above their per-call limit before signing, and the unused part of the cap is released from their budget. Existing exact clients are unaffected.",
			"link": "/docs/x402-upto",
			"tags": [
				"feature",
				"improvement"
			]
		},
		{
			"date": "2026-10-15",
			"type": "launch",
			"title": ".well-known/skill.md",
			"summary": "SKILL-MD 1.0: every paid HTTP route on three.ws with its price, parameters, and the Solana and Base payment rails it settles on, generated straight from the live OpenAPI catalog. For the Agent Skills connector file, see /skill.md instead.",
			"link": "/.well-known/skill.md",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-15",
			"type": "launch",
			"title": "Docs · Forge Workflows",
			"summary": "How Forge Workflows chains Forge tools into one repeatable run: the visual node editor, the four starter templates (photo to 3D, text to rigged character, batch photos to library, photo to game asset), resuming from a failed node, and how it differs from Workbench.",
			"link": "/docs/forge-workflows",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-15",
			"type": "launch",
			"title": "Docs · Squad chat",
			"summary": "How squad chat turns a plain-language request into a plan of role-tagged steps for a specialist team or a solo agent: who can see each squad, how the plan is checked against your own words before it runs, and when a step stops for your approval.",
			"link": "/docs/team-chat",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-15",
			"type": "launch",
			"title": "Docs · Standalone repositories",
			"summary": "The generated catalog of every publishable package in this monorepo mirrored to its own standalone GitHub repository with its own install command and documentation site, so each one can be found, starred, installed and cited on its own.",
			"link": "/docs/standalone-repos",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-15",
			"type": "update",
			"title": "17 named commerce tools and a spending report land in the x402 MCP buyer, hosted and self-custodial",
			"summary": "The self-custodial x402 buyer (@three-ws/x402-mcp, npx -y @three-ws/x402-mcp) and the hosted agent wallet (https://three.ws/api/mcp-agent) both gained 17 named tools, one per fixed three.ws x402 service: weather_forecast, weather_go_no_go, carbon_now, carbon_best_window, domain_rdap_check, domain_rdap_check_bulk, research_search, research_paper, research_bibliography, book_search, book_read, news_wire_search, news_wire_poll, transit_plan, transit_delays, places_search and places_detail. Each carries a fixed input schema and states its price in its description, so a model calls it correctly far more often than it composes the equivalent raw pay_and_call(url) call. On the hosted side every named tool has a matching <name>_quote read tool that prices it without paying, and the shared tool-policy runtime (@three-ws/mcp-policy) gates payment on that exact quote (one service's quote can never unlock a different service's payment). The stdio package also gained spending_report, which totals everything pay_and_call and the named tools have paid, by merchant and by day, from a local append-only ledger (X402_MCP_LEDGER_PATH).",
			"link": "/docs/mcp",
			"tags": [
				"feature",
				"sdk"
			]
		},
		{
			"date": "2026-10-15",
			"type": "update",
			"title": "A generated SKILL-MD 1.0 catalog of every paid HTTP route is now live at /.well-known/skill.md",
			"summary": "Any agent can now load one markdown file, https://three.ws/.well-known/skill.md, and get a conformant SKILL-MD 1.0 document (the x402-skill-md format) listing every priced endpoint on three.ws: method, path, price, parameters, and the Solana and Base payment rails it settles on, plus a sample 402 challenge body. The document is generated straight from the same OpenAPI catalog /openapi.json serves (api/_lib/skill-md.js reads the shared buildOpenApiDoc() builder and the real buildExactRequirements() rail logic, so the catalog and the live 402 challenge can never drift apart), and is linked from /.well-known/x402.json and llms.txt. Validated in tests/skill-md.test.js against the real upstream x402-skill-md npm validator: zero errors other than the EVM rail finding (SM005), which is expected since this is a Solana-first platform and Base settles only when a facilitator is configured. Distinct from the pre-existing https://three.ws/skill.md (no .well-known), the Agent Skills connector file for installing three.ws MCP servers; both now cross-link to the other.",
			"link": "/.well-known/skill.md",
			"tags": [
				"feature",
				"docs"
			]
		},
		{
			"date": "2026-10-15",
			"type": "update",
			"title": "A spend call above an agent's approval threshold now pauses for the owner instead of failing",
			"summary": "The requires_approval verdict agent payment sessions and agent-to-agent hires can already produce now actually does something: both /api/pay/execute and /api/agents/a2a-hire create a request on the existing approval inbox the moment a call crosses the caller's approval_threshold_usd, answer with 202 and a poll link to /approvals/<id> instead of failing the call, and resume automatically the moment the owner taps Approve there, re-probing or re-running the exact same reserve-then-settle path the call would have taken inline, with no re-entry point for a double-spend. A denied request answers 403 on the next poll, an expired one answers 410, and retrying with the same idempotency key before the owner answers just re-polls instead of parking a second request. Nothing new to build on the approval page itself: it already renders any venue generically from the request's summary, amount, and risk notes, so the two new venues (payment_session_execute, a2a_hire) show up with the right Approve/Decline card for free. Covered by 21 new handler tests across create, approve, decline, expire, and the executor's own idempotent re-run.",
			"link": "/approvals",
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-15",
			"type": "update",
			"title": "Agent-to-agent hires now carry a signed fulfillment record, and it feeds reputation and pricing",
			"summary": "Every settled a2a-hire (api/agents/a2a-hire.js) now writes exactly one signed attestation row: {hire_id, payment_signature, outcome, evidence_hash, signed_by}, outcome one of delivered, failed, or disputed, signed off-chain with the same platform attestation key api/_lib/attest-event.js uses for on-chain provenance memos. A client-side timeout is recorded as disputed, never inferred as delivered, since x402's verify-then-settle means the provider may already have been paid server-side. The resulting recency-weighted fulfillment rate (30-day half-life, minimum 5 attestations before it counts) is now a real input to the free Financial reputation score on every agent's Trust tab: the Settlement reliability pillar's detail line reports the rate alongside its sample size, for example '90% hire fulfillment over 12 hires', or how many hires are attested so far if the minimum has not been met yet. Providers can also opt a service into an optional x402 pricing discount for well-reputed hirers (agent_paid_services.reputation_discount_enabled, off by default): the hiring agent's reputation tier mints a short-lived, slug-scoped, signature-verified voucher, never a caller-supplied claim, so the paywall always fails closed to full price on anything unsigned, expired, or mis-scoped.",
			"link": "/agents",
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-15",
			"type": "update",
			"title": "Payment sessions gain blocked hosts, an approval threshold, and a per-rail daily cap, all with tamper-evident verdicts",
			"summary": "Agent payment sessions get three new governance knobs, settable at creation and editable while a session is active: blocked_hosts (a denylist checked after the allowlist, so an explicit block always wins over a broad allow, even with no allowlist set), approval_threshold_usd (a call priced above this amount now gets a distinct requires_approval verdict instead of either settling or silently failing), and per_rail_daily_usd (a rolling 24h spend cap per settlement network, reserved atomically the same way the session budget already is, closing the race a naive sum-of-past-executions check would leave open). Every governance verdict, allow or reject, now carries a policy_digest (a sha256 hash of the exact policy it was judged against) and an HMAC signature over the verdict, digest, request, and timestamp, stored with the execution: editing a session's policy after the fact changes the digest and breaks the signature on every verdict that preceded the edit, so a verdict record can be trusted even after the policy it was judged against has since moved. The dry-run simulator at /api/pay/simulate now predicts all three new rules through the exact same shared policy module the real enforcer calls, so a simulated verdict and an enforced one can never disagree; that parity is pinned by a new test running both over identical scenarios. The payments page gained matching fields in both the session creation and edit modals, with inline validation and a collapsed 'Advanced spend policy' section so the common case (budget, expiry, host allowlist) stays uncluttered.",
			"link": "/docs/payment-sessions",
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-15",
			"type": "update",
			"title": "Receipt Vault gains an Outbound tab: what your agents spent elsewhere, verified against the chain itself",
			"summary": "The Receipt Vault at /receipts now has two tabs. Inbound is unchanged (what three.ws billed your wallet); the new Outbound tab answers the other question: what did your agents spend at OTHER x402 merchants while running on an Agent Payment Session. Each settled Solana execution is resolved against the settlement transaction's own token-balance change the first time anyone views it (payer, payee, mint, amount, fee, slot, time), independent of whatever the merchant's response claimed, then cached so later views are free; a 'verified' badge marks a row that matched the chain, 'pending' while resolution is still in flight, and 'unverified' if the lookup failed permanently. The tab is account-session gated (the same credential /payments uses, not a wallet signature, since Payment Sessions are account-scoped, not wallet-scoped), filters by network and merchant host, and exports to CSV alongside the existing JSON receipt downloads. New endpoint: GET /api/x402/outbound-receipts.",
			"link": "/receipts",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-15",
			"type": "update",
			"title": "Turn any public OpenAPI spec or GitHub repo into a draft agent skill",
			"summary": "New importer at /skills/import (From an API tab) and POST /api/skills/import: point at an OpenAPI/Swagger URL or a GitHub repo and every operation becomes a tools.json entry with a generated handlers.js function calling ctx.fetch, SKILL.md prose written from the spec's own descriptions, and Swagger 2.0 upgraded to OpenAPI 3 automatically. A README-only repo becomes a declarative skill instead, prose only, no tools. Every import lands as a disabled draft, owner-scoped and labelled untrusted: enabled only ever flips via the dedicated PATCH /api/skills/import/:id route, never at creation, and nothing is installed onto any agent automatically. Generated handlers fill auth from the skill's declared secrets, never a hardcoded credential. Also available from the CLI: three-ws skills import <url> and three-ws skills drafts. New package: @three-ws/skill-import.",
			"link": "/skills/import",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "8 keyless live-data services join the x402 paid API: weather, grid carbon, domains, research, books, news, transit, places",
			"summary": "three.ws's x402 surface grows 17 new routes, each needing no API key anywhere in the chain (not an upstream key, not a three.ws key), ported natively onto three.ws's own Solana facilitator so they settle, receipt, and discover exactly like every other paid endpoint: Weather Guard (24h forecast + severe alerts from Open-Meteo, NWS fallback), Carbon (UK grid carbon intensity + lowest-carbon scheduling window), Domains (live RDAP registration lookups, single and bulk), Research (paper search across arXiv/Crossref/Semantic Scholar, metadata, bibliographies), Books (OpenLibrary + Project Gutenberg search and full-text reads), News Wire (global news search and polling over GDELT DOC 2.0), Transit (MBTA GTFS trip planning and realtime delay snapshots), and Places (OpenStreetMap Overpass point-of-interest search and detail). Each service's discovery route runs a free daily per-IP quota before falling through to the x402 pay-per-call lane, fails closed to the paid rail rather than opening an unmetered proxy if the quota store is unreachable, and every upstream call sends an identifying User-Agent. No fixture or mocked fallback anywhere in the set: an upstream outage answers 502, and the one route whose source suite offers a fake-data fallback when unconfigured (Places Detail's review enrichment) ships without that fallback, returning only the real OpenStreetMap record. All 17 routes appear in GET /openapi.json and GET /.well-known/x402.json with Solana listed first in every payment challenge.",
			"link": "/docs/x402-endpoints",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "A new wallet linkage score flags a coin's creator buying their own launch",
			"summary": "GET /api/crypto/linkage cross-checks 2-10 Solana addresses for shared control: a 0-100 same-controller score per pair, combining six real on-chain signals by noisy-OR (shared fee payer, one address funding the other, both sharing a first funder, SPL token-account control, direct transfers, a shared funder sending similar amounts in a short window), every match backed by the signature or account that triggered it. It is keyless, free, and part of the public Crypto Data API, and now wired into two places that act on money: the Trade Safety Firewall warns when an early buyer scores as the same controller as a coin's creator (wash-trading dressed up as demand), and copy-trading refuses to size an order behind a leader whose own wallet links to the creator of the coin they are 'signaling', showing the follower exactly why. The same scorer ships as the wallet_linkage tool in the hosted intel MCP server for any AI agent to call directly.",
			"link": "/crypto-api",
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "A read-only drift report for every standalone GitHub mirror",
			"summary": "npm run mirrors:drift compares each of the ~105 standalone mirrors in data/standalone-mirrors.json against its monorepo source at the last synced commit (GitHub API, with a README-timestamp fallback when rate-limited), flags any package whose GitHub copy has diverged, and writes the result to tasks/mirror-drift-<date>.json. It never pushes or mutates a mirror; it is the audit step that found the two fixes above.",
			"link": "/docs/contributing",
			"tags": [
				"infra",
				"docs"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "Agents can now carry an owner-signed, offline-verifiable spend cap",
			"summary": "A new Delegation tab in the agent wallet hub lets an owner sign a portable spend delegation with their own linked Solana wallet (a message, never a transaction): 'this agent may move at most CAP lamports per EPOCH, until NOT_AFTER.' The signed envelope is plain text and the verification math is a zero-dependency function any outside counterparty can run themselves (packages/agent-guards, spec in its README) to confirm the authorization without trusting three.ws's say-so. three.ws enforces the same cap server-side on every call through POST /api/agent/guard, measured from the agent wallet's REALIZED spend in the custody ledger rather than the agent's own claim, so an exact-output trade that ends up costing more than advertised still can't slip past the ceiling. A replayed nonce, an expired delegation, or a signature from the wrong wallet is rejected with a specific reason.",
			"link": "/docs/agent-wallet-api",
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "Atomic is now a six-tab Transaction V1 lab, not just an inspector",
			"summary": "/atomic grew five tabs beyond the Inspector, each reachable by click, arrow-key/Home/End tab navigation, or a deep link (?tab=mask, ?tab=sponsor, ?tab=planner, ?tab=diff, ?tab=wallet). The config mask decoder reads a V1 transaction's real TransactionConfigMask u32 and its fixed-width ConfigValues byte by byte, flagging a half-set priority-fee pair or a reserved bit SIMD-0385 has not assigned yet. The sponsor cap view shows a paymaster exactly what it is agreeing to pay, reading V1's inline config instead of a Compute Budget instruction scan that sees nothing on a V1 transaction. The size and budget planner compiles a pasted instruction set with @solana/kit to an exact byte count against legacy, V0, or V1's ceiling, including an exact lamport total for a chosen priority fee. The legacy/V0/V1 diff compiles the same instructions three ways and reports the real byte deltas, honestly, including the case where V1's inline config makes it larger than legacy. The wallet V1 capability check connects the browser's injected wallet and reports the same verdict the rest of three.ws would get from findV1WalletStandardSigner before ever requesting a real V1 signature. Nothing here is estimated: every number comes from compiling and decoding real transactions, and nothing is ever signed, simulated, or broadcast.",
			"link": "/atomic",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "Atomic now replays a pump.fun transaction step by step",
			"summary": "Atomic (/atomic) decodes every Pump, PumpSwap, and PumpFees event in a transaction's logs, oldest first, and renders it as a Replay panel: a bonding-curve-position bar, a human-readable description of each step (create, buy/sell, graduation, creator-fee collection and distribution, GitHub social-fee claims, and post-graduation PumpSwap swaps), and the SOL/token amounts that moved. An event the installed SDK does not recognize still renders, labeled unrecognized, instead of silently disappearing. For a create transaction, the panel also pages through the earliest trades on that mint since launch, walking Solana's signature history backward in bounded pages since RPC has no forward cursor.",
			"link": null,
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "Creator earnings now cross-check two independent pump.fun sources",
			"summary": "A coin's earnings figure on /launches/<mint> and in the agent earnings card used to come from one source only: the creator wallet's lifetime fee index. It now also sums that specific coin's own pump.fun distribution timeline, the only feed that can say which coin actually paid a wallet, and shows both: 'this coin paid X SOL' next to the wallet-level figure, plus a plain sentence when the two sources disagree and by how much. Nothing is hidden when sources drift apart; the gap is the point. The snapshot pipeline that already indexed wallet-level fees now reconciles against the timeline for every coin on each refresh.",
			"link": "/launches",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "Deep links to a specific avatar now actually load that avatar",
			"summary": "@three-ws/walk's ?walk=play&avatar=<id> deep link and the drop-in resume path read the saved avatar preference straight out of storage and never looked at the query string, so sharing a link to a specific avatar silently loaded the stored (or default) one instead. A new deepLinkAvatarId resolver gives the query param precedence and persists it, the same way picking an avatar in the UI does.",
			"link": null,
			"tags": [
				"fix",
				"sdk"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "Every pump.fun launch now carries a plain-English receipt",
			"summary": "/launches/<mint> gained a Launch receipt panel composing five on-chain facts into one readable object: whether the mint or freeze authority can still act (with a plain sentence for each, not just enabled/disabled), supply and decimals, the top-10 holder share, where trading fees route (a creator wallet, a fee-sharing config, cashback, or holder rewards), the creation transaction's version and byte size, and the Trade Safety Firewall's verdict. A coin that never launched through pump.fun gets an honest 'not a pump.fun launch' instead of an error, and a source that fails marks only its own section unavailable, never an invented number. Copy the receipt as text or download it as JSON; both carry a SHA-256 content hash of the response so a saved copy can be checked against a fresh read. A shareable 1200x630 card is available via GET /api/pump/launch-og?mint=<mint>&variant=receipt, and the composition itself is a new public endpoint, GET /api/pump/launch-receipt?mint=<mint>.",
			"link": "/launches",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "GitHub fee-claim channel now attributes withdrawals to a coin, or says plainly it cannot",
			"summary": "A GitHub identity withdrawing pump.fun fees through the claim_social_fee_pda instruction only proves payment to that identity, not which coin paid it: one GitHub fee account can be a shareholder on more than one coin, and its address can be pasted into a copycat coin's metadata. The claims feed and its Telegram channel now classify every such withdrawal with on-chain evidence: a same-transaction distribution to the exact account, or a 90%-dominant distribution history since the previous claim, then a repository-owner or creator-wallet match, down to an honest unresolved or unverified label when nothing proves a coin. A new-GitHub-account-plus-copycat-coin pattern holds the claim for review instead of posting it with a celebratory card.",
			"link": null,
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "GitHub fee-claim feed now reads from a real-time listener, not just an on-demand RPC scan",
			"summary": "The claims feed's GitHub-attribution path used to walk Solana RPC history fresh on every request, the same cost every time, with nothing persisted in between. services/pump-claims is a standalone process that subscribes to PumpFees program logs directly, decodes and attributes each claim as it happens, and writes it to a new pump_fee_claims table with a watchdog that resubscribes on a stalled connection and gap-fills whatever a drop missed. The claims route now reads that table first and only falls back to the RPC scan when the table has nothing for the requested window, so PUMPFUN_BOT_URL is no longer required for GitHub claims specifically (ordinary wallet claims still use it).",
			"link": null,
			"tags": [
				"feature",
				"infra"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "MCP clients can now prepare a pump.fun launch for you to sign",
			"summary": "The hosted MCP server gained pumpfun_prepare_launch: an assistant (Claude Desktop, Cursor, or any MCP client) that has agreed a coin name, ticker, description and image with you can call this tool to validate every field the same way the /launch page does, fetch and type/size-check the image through the SSRF-hardened fetcher, and hand back a pre-filled /launch URL plus a plain-English summary. The tool never signs or launches anything; it is marked read-only and non-destructive, and its response always carries requires_human_signature: true. Opening the returned link on /launch now shows a 'prepared from your assistant' banner so you know exactly which fields came from the conversation before you review and sign.",
			"link": "/launch",
			"tags": [
				"feature"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "Robinhood Chain feed worker now runs the published SDK, not a stale local snapshot",
			"summary": "workers/robinhood-feed depended on robinhood/robinhood-chain-sdk through a file: link, a reference copy that drifts from the standalone robinhood-chain-sdk repo it mirrors. The worker now installs hoodchain from npm like any other dependency, so it always runs the released SDK. Also fixed: seven pointer READMEs staged for duplicate or superseded standalone repos (three-ui, crypto-market-data, crypto-market-data-ts, crypto-data-aggregator, memescope-monday-directory, and one of each duplicate Robinhood Chain repo pair), ready for the owner to push and archive.",
			"link": null,
			"tags": [
				"fix",
				"infra"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "Standalone GitHub mirrors now stage instead of force-pushing",
			"summary": "scripts/sync-standalone-repos.mjs force-pushed straight to main on every run, which could silently create duplicate repos for the eleven mirrors already renamed on GitHub and bypassed the owner's push-approval rule. data/standalone-mirrors.json is now the single source of truth for which monorepo directory maps to which public repo, read by every exporter (sync, growth satellites, the awesome list, the skill-repo builder) instead of each keeping its own list. The sync script only stages a snapshot under dist/standalone-mirrors/, fixes any stale pre-Apache-2.0 README or LICENSE footer, and prints the push command for the owner; npm run sync:repos:check compares what is staged against each mirror's live tree and reports drift without writing anything.",
			"link": "/docs/contributing",
			"tags": [
				"infra",
				"docs"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "The native $THREE launchpad now taxes snipers, not just steady trading",
			"summary": "Every pool on the native launchpad lane used to open at the same flat 1% trading fee a coin keeps forever, which is exactly what a sniper bot wants: the same price whether it buys in the pool's first block or an hour later. New pools now open at a 50% fee that decays exponentially down to the normal 1% over the first 100 slots (about 40 seconds), so a bot buying in the first block pays close to half its $THREE in fees while an organic buyer a minute later pays the standard rate. The coin creator's own bundled first buy stays exempt, since that is the creator funding their own launch, not a snipe. The schedule runs entirely on Meteora's own Dynamic Bonding Curve fee scheduler, no new contract.",
			"link": "/docs/native-launchpad",
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "The pre-push guard now catches a leaked Solana secret key, and withdrawals warn before a sweeper bot drains them",
			"summary": "scripts/check-secrets.mjs, the hook that blocks a push carrying a credential, now decodes every 86-90 character base58 run in added content and flags it only when the first 32 bytes derive the embedded public key in the last 32 bytes via Ed25519, catching a real Solana keypair secret while leaving the repo's thousands of genuine 64-byte transaction signatures untouched. Separately, the agent wallet's Withdraw tab now reads a destination's recent on-chain history before you send: a wallet that repeatedly drains to near-zero within seconds of receiving funds, the sweeper-bot fingerprint, surfaces a blocking warning on the confirm screen and again server-side if you retry, so a sweeper bot can't just wait for the preview to go stale.",
			"link": "/docs/agent-abilities",
			"tags": [
				"security"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "three.ws Avatar MCP clamps unbounded tool arguments before they reach generated HTML",
			"summary": "render_avatar's name and camera-orbit arguments flowed into the generated <model-viewer> HTML with no length bound, unlike the model URL, which already rejected oversized or unsafe values. Both are now clamped the same way, closing the one argument path that could still balloon a rendered page or chat payload.",
			"link": null,
			"tags": [
				"fix",
				"security",
				"sdk"
			]
		},
		{
			"date": "2026-10-14",
			"type": "update",
			"title": "x402 agent buyers now pay v1 sellers, not just v2",
			"summary": "Every buyer path, the hosted a2a-hire/pay_and_call flow, the packages/x402-mcp stdio server, and the mcp-bridge stdio client, registered only x402's newer CAIP-2 wire format (network strings like solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp). Most of the open x402 bazaar, and every service in the owner's x402-suite, still speaks v1 (flat network strings like solana, price field maxAmountRequired), so agents paying through three.ws could not reach those sellers at all. All three buyers now call registerExactSvmScheme() instead, which registers both wire formats on the same Solana key; when a seller advertises both, v2 is always preferred. Settlement receipts already share field names (success, transaction, network, payer) across both versions, so /receipts and the session ledger need no changes. Fixing this also surfaced two real spend-cap bugs that only trigger on a v1 payment: the hosted buyer's enforceCap threw instead of admitting a capped v1 payment, and mcp-bridge's spending-cap hook silently read a v1 payment's price as zero, bypassing both the per-call and session ceilings. Both are fixed and covered by regression tests.",
			"link": "/docs/mcp-agent",
			"tags": [
				"feature",
				"security"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Docs · Staked Event Markets",
			"summary": "Decision record for staked Event Markets on Solana: the parimutuel model, fee and buyback split, limits, void and refund rules, and the jurisdiction and age questions that stay with the owner.",
			"link": "/docs/event-markets-staking",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Docs · three.ws with Google ADK",
			"summary": "Connect a Google Agent Development Kit agent to the free three.ws 3D studio over MCPToolset: discover the tool catalog, forge and rig models, and run a full LlmAgent conversation. No account, payment or API key for the studio tools.",
			"link": "/docs/google-adk",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Docs: Discord Activity (Forge Room)",
			"summary": "How the three.ws Discord Activity works: the OAuth2 auth flow, Discord's /.proxy/ URL mapping and CSP, the shared event-sourced room state, and why it ships with no purchases.",
			"link": "/docs/discord-activity",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Docs: LiveKit and Pipecat avatar integrations",
			"summary": "How to drive a three.ws <agent-3d> avatar's lipsync and gestures from a LiveKit Agents or Pipecat voice pipeline, with the livekit-plugins-threews and pipecat-threews packages, runnable local examples, and the data-channel message contract both share.",
			"link": "/docs/voice-framework-integrations",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Docs: Shopify app (Photo to 3D product media)",
			"summary": "How the three.ws Shopify app works: OAuth and embedded session tokens, the photo-to-GLB-to-productCreateMedia pipeline, usage-based Billing API integration, and the mandatory privacy webhooks.",
			"link": "/docs/shopify-app",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Docs: WordPress embed (three.ws Agent plugin)",
			"summary": "How the three.ws Agent WordPress plugin works: the Gutenberg block and [three_ws_agent] shortcode, the SRI-pinned release, and the real Plugin Check verification run.",
			"link": "/docs/wordpress-embed",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Forge Room (Discord Activity)",
			"summary": "A shared Forge room that runs embedded inside a Discord voice channel: everyone in the call prompts, watches the same 3D model generate, and votes together.",
			"link": "/discord-activity",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Import your VRoid Hub avatar",
			"summary": "Bring a VRM avatar from VRoid Hub into three.ws with its creator's license honored: only the actions the creator allowed are ever offered.",
			"link": "/import/vroid",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Open source credits",
			"summary": "Every open-source project, GPU model, and asset source three.ws is built on, grouped by what it powers: rendering, formats and compression, generation models, motion, voice, assets, and infrastructure. Generated from package.json on every build.",
			"link": "/open-source",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Photo to 3D product media (Shopify app)",
			"summary": "An embedded Shopify admin app that turns a product photo into a real GLB and attaches it to the product, so the storefront shows a 3D viewer on desktop and AR Quick Look on iPhone.",
			"link": "/apps/shopify",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "launch",
			"title": "Video to Motion: Turn Any Video into an Animation File",
			"summary": "Upload a video of a person and download the motion as a GLB, BVH, or FBX animation file. Preview it on a default avatar or your own rig, trim it, and save it to your animation library.",
			"link": "/video-to-motion",
			"tags": [
				"launch"
			]
		},
		{
			"date": "2026-10-13",
			"type": "update",
			"title": "A Discord Activity brings a shared Forge room into any voice channel",
			"summary": "Open the new Activity from a Discord voice channel and everyone in the call shares one Forge room: one prompt, one in-progress generation, one finished model with a shared vote count, and an agent that reacts in text to what just happened. Auth maps a verified Discord identity (re-checked against Discord's own /users/@me, never trusted from the client) to a room-scoped session; generation and voting reuse the real /api/forge pipeline and forge_votes table rather than a separate throwaway pipeline. No coin, wallet, or purchase path. Docs: /docs/discord-activity. Submission packet for Developer Portal setup and Discovery copy: marketing/growth/submissions/discord-activity.md.",
			"link": "/docs/discord-activity",
			"tags": [
				"feature",
				"docs"
			]
		},
		{
			"date": "2026-10-13",
			"type": "update",
			"title": "A Shopify app turns product photos into 3D product media",
			"summary": "A new embedded Shopify app, built end to end but not yet installable (Partner account, env vars, and App Store submission are owner actions): pick a product photo in the admin, generate a real GLB through three.ws's own /api/forge pipeline, preview it in-page, and attach it with productCreateMedia so the storefront shows a 3D viewer on desktop and AR Quick Look on iPhone from the one upload (Shopify derives the USDZ automatically). Bulk mode generates across a whole catalog with real per-item status. Billing runs through Shopify's own usage-based Billing API, priced from Forge's own per-call cost, in test mode until the app has Public distribution. The three mandatory privacy webhooks plus app/uninstalled are HMAC-verified and delivery-deduplicated. Docs: /docs/shopify-app. Submission packet for Partner Dashboard setup and App Store listing copy: marketing/growth/submissions/shopify-app.md.",
			"link": "/docs/shopify-app",
			"tags": [
				"feature",
				"docs"
			]
		},
		{
			"date": "2026-10-13",
			"type": "update",
			"title": "A three.ws avatar now lipsyncs to any LiveKit Agents or Pipecat voice pipeline",
			"summary": "Two new packages, livekit-plugins-threews and pipecat-threews, republish a running voice agent's TTS and user-turn frames as the same transcript/gesture/speech_started/speech_ended message shape over the room's data channel, which <agent-3d voice=\"livekit\"> already renders client-side: no server-side video rendering, no change to the browser code at all. The LiveKit package is an AvatarSession plugin dropped into an AgentSession; the Pipecat package is a FrameProcessor placed after the TTS service. Each ships a runnable local example against a real open-source livekit-server with a real local TTS, verified end to end with real browser automation driving the actual avatar lipsync and gesture cues off a live bot in both frameworks. Docs: /docs/voice-framework-integrations.",
			"link": "/docs/voice-framework-integrations",
			"tags": [
				"feature",
				"sdk",
				"docs"
			]
		},
		{
			"date": "2026-10-13",
			"type": "update",
			"title": "Avatar downloads fail over when object storage is not entitled",
			"summary": "When the Cloudflare R2 account stopped serving objects, avatar model downloads answered a bare error instead of trying the bucket public domain. That fault is now recognised as a storage outage, so the failover runs.",
			"link": null,
			"tags": [
				"fix"
			]
		},
		{
			"date": "2026-10-13",
			"type": "update",
			"title": "Embed a live 3D agent in WordPress, Framer, or Webflow",
			"summary": "Three native embeds for <agent-3d>, one per site builder's own extension point instead of a generic iframe: a WordPress Gutenberg block and [three_ws_agent] shortcode (server-rendered so the editor preview always matches the front end), a Framer code component with property controls, and a Webflow Code Component, all exposing On-chain URI, Agent ID, Model URL, Background, Framing, Poster and Autoplay. A shared build step pins all three to the same version and SRI hash from the agent-3d release ledger, so they can never drift apart. The WordPress plugin passed the official Plugin Check tool against a real local WordPress install with no errors; Framer and Webflow were each verified in a real-React test harness that boots a live WebGL canvas against the production CDN release, and the Webflow component additionally compiles through the real Webflow CLI. WordPress.org, Framer Marketplace, and Webflow Apps submissions are owner actions. Docs: /docs/wordpress-embed, /docs/embedding.",
			"link": "/docs/wordpress-embed",
			"tags": [
				"feature",
				"docs"
			]
		}
	]
}