Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(deploy-onchain): document the atomic v1 mint in the changelog, STRUCTURE.md, and the metaplex-agent-mcp README
nirholasf4959cfe8630
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 9050e9096..8493ff6ca 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,8 +7,8 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-09-16- **Docs · The /launch launchpad** (`/docs/launchpad`): How three.ws/launch launches a pump.fun coin for a 3D agent: agent-linked metadata, the 1% dev-buy fee, v0 lookup-table and Solana transaction v1 formats, claiming creator rewards on three.ws, and the API behind it.-- **$THREE pages now show the real buyback ledger instead of a burn estimate**: The $THREE live page and the token dashboard used to show a "$THREE burned" total that was estimated from the number of agents on the platform, not read from the blockchain. The platform does not burn $THREE, so that number is gone. Both pages now show what the protocol actually commits to: the share of revenue set aside to buy $THREE on the open market, how much has been bought, and whether the buyback engine is running. The AWS page also no longer says Marketplace usage is billed to your AWS invoice; the subscription is free and usage is paid per call. (`/three-live`) `[fix]`- **A cleaner launchpad for your 3D agent's coin, with rewards you claim right here**: three.ws/launch is rebuilt around one flow: pick one of your 3D agents, name the coin, and launch it on pump.fun from your wallet or from the agent's own wallet. The coin's metadata links your agent's page and 3D body, a live preview and cost panel show exactly what you will pay (including a 1% three.ws fee on the dev buy), and a new My coins tab shows unclaimed creator rewards and claims them in one click, no pump.fun app needed. Launches now fit in a single transaction thanks to pump.fun's lookup table, and larger ones, like USDC-paired coins with a dev buy, use Solana transaction v1 automatically when your wallet supports it. This also fixes launches that were failing because an on-chain buyback program stopped accepting new agents. (`/launch`) `[feature, improvement, fix]`+- **Deploy your agent on-chain with Solana's new transaction v1**: Minting an agent to Solana now uses the new transaction v1 format whenever your wallet supports it, from the agent deploy button, the registration wizard (vanity addresses included), and /deploy-onchain. On /deploy-onchain that turns a Genesis-shape deploy from two wallet transactions into one: the asset is created and registered in the Metaplex Agent Registry atomically, so there is no half-finished deploy if something fails in between. Each deploy spells out its compute, account data, and priority fee limits instead of relying on defaults, and three.ws checks that the transaction that landed on-chain is the exact version it prepared before recording your agent. Wallets that have not added v1 yet keep working exactly as before, and a deployed agent now shows which transaction format it used. (`/deploy-onchain`) `[feature, security]`- **GitHub fee claims now say what they actually prove**: A GitHub fee claim on pump.fun proves that a GitHub account collected creator fees routed to it. It does not prove that person built the coin, owns the linked repository, or backs the project. Claim cards on /pumpfun used to read as a developer endorsing a coin even when the account was a lookalike name, the coin had no GitHub link at all, or one fee account was shared by several coins and the card simply picked the biggest one. Every claim now carries one of five labels: verified repository, verified creator wallet, identity mismatch, unverified, or unresolved pooled withdrawal. Only the two verified labels get trade buttons or count toward a coin's reputation score, mismatches are flagged in red, and the Telegram claims channel follows the same rules. (`/pumpfun`) `[fix, improvement]`## 2026-09-15diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 021ef9501..fe2ee834a 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -193,7 +193,7 @@ bottom.| Open Inference Protocol (OIN v0.1) | spec [specs/OPEN_INFERENCE_PROTOCOL.md](specs/OPEN_INFERENCE_PROTOCOL.md), verifier [api/_lib/oin-verify.js](api/_lib/oin-verify.js), conformance runner [scripts/oin-conformance.mjs](scripts/oin-conformance.mjs), reference node [workers/stylize/oin.py](workers/stylize/oin.py) | In-repo | Phase 4 roadmap: the vendor-neutral wire protocol that decouples inference from any single provider. A job envelope, a signed capability advertisement at `GET /.well-known/oin`, and an Ed25519-signed response bound to the job by a SHA-256 digest over its RFC 8785 canonical form, so any third party can verify a node's result without trusting the transport or the platform. The stylize worker is the reference node behind `OIN_ENABLED=true` (byte-for-byte its pre-OIN self with the flag off) and self-hosted operators with no GCS bucket sign filesystem artifacts via `OIN_RESULT_DIR`. `node scripts/oin-conformance.mjs --node <url>` drives advertisement, submit, poll, response verification, and artifact hashing end to end. Settlement rides on [specs/inference-receipts.md](specs/inference-receipts.md). Tests: [tests/oin-verify.test.js](tests/oin-verify.test.js), [workers/stylize/test_stylize.py](workers/stylize/test_stylize.py) || Production server (Google Cloud Run) | [server/](server) + [Dockerfile](Dockerfile) | Live | Single Express container serving the static frontend, the vercel.json route table, and all `api/**` handlers with Vercel-parity routing; deploy via `npm run deploy:gcp` ([server/cloudbuild.yaml](server/cloudbuild.yaml)), crons via [scripts/create-gcp-scheduler.mjs](scripts/create-gcp-scheduler.mjs) · see [server/README.md](server/README.md) || Multiplayer 3D world (world.three.ws) | [deploy/world/](deploy/world) — [Dockerfile](deploy/world/Dockerfile), [cloudrun.yaml](deploy/world/cloudrun.yaml), [apply-hardening.sh](deploy/world/apply-hardening.sh), patches in [deploy/world/patches/](deploy/world/patches); health monitor [api/cron/world-health.js](api/cron/world-health.js) | Live · `hyperfy-world` on Cloud Run | [Hyperfy](https://github.com/hyperfy-xyz/hyperfy) pinned to an exact upstream commit and rebuilt with three local patches (server-side upload cap, `/status` blueprint-asset enumeration, fail-closed-without-`ADMIN_CODE`). World state (SQLite + uploaded assets) lives in the GCS bucket `world-three-ws-data` mounted at `/app/world`, so the container is stateless. **The world is gated:** without `ADMIN_CODE` Hyperfy's `effectiveRank` falls back to `Ranks.ADMIN` and every anonymous visitor gets server-side build rights — the fail-open default that emptied the world on 2026-06-12. Deploy + verify with `bash deploy/world/apply-hardening.sh`; builders unlock in-world with `/admin <code>`. See [deploy/world/README.md](deploy/world/README.md) |-| Metaplex Agent Registry deploy (Genesis-333 mint for everyone) | [pages/deploy-onchain.html](pages/deploy-onchain.html) + [src/deploy-onchain.js](src/deploy-onchain.js) `→ /deploy-onchain`, shared builders [packages/metaplex-agent-mcp/src/lib/](packages/metaplex-agent-mcp/src/lib) (published as `@three-ws/metaplex-agent-mcp`, also in the official MCP registry as `io.github.nirholas/metaplex-agent`) | Live | Mint any agent into the Metaplex Agent Registry in the exact Genesis 333 shape: data: URI metadata, verified creator, 5% royalties, immutable metadata, EIP-8004 identity with `model.uri` + `x402Support`. The page signs with the user's own wallet (Phantom/Solflare/Backpack, `signAllTransactions`) through the same-origin RPC proxy; the MCP server gives agents the identical mint with their own key (preview-first, `confirm:true` gated) plus a prepare/send lane for external wallets. Both consume one isomorphic builder library, and [tests](packages/metaplex-agent-mcp/test/genesis-shape.test.mjs) pin the output byte-for-byte to the live Genesis #332 URIs. Devnet is a free rehearsal lane end-to-end. A mainnet deploy also pays a flat 0.02 SOL fee to the $THREE buyback wallet, halved at 50k $THREE in the paying wallet and waived at 250k, disclosed in every preview and carried inside the create transaction ([packages/metaplex-agent-mcp/src/lib/three.js](packages/metaplex-agent-mcp/src/lib/three.js)); the `three_status` tool prices it against any wallet. |+| Metaplex Agent Registry deploy (Genesis-333 mint for everyone) | [pages/deploy-onchain.html](pages/deploy-onchain.html) + [src/deploy-onchain.js](src/deploy-onchain.js) `→ /deploy-onchain`, shared builders [packages/metaplex-agent-mcp/src/lib/](packages/metaplex-agent-mcp/src/lib) (published as `@three-ws/metaplex-agent-mcp`, also in the official MCP registry as `io.github.nirholas/metaplex-agent`) | Live | Mint any agent into the Metaplex Agent Registry in the exact Genesis 333 shape: data: URI metadata, verified creator, 5% royalties, immutable metadata, EIP-8004 identity with `model.uri` + `x402Support`. The page signs with the user's own wallet (Phantom/Solflare/Backpack, `signAllTransactions`) through the same-origin RPC proxy; a wallet that advertises Solana transaction v1 over Wallet Standard instead signs create + register as ONE atomic v1 transaction (Genesis-shape mints overflow v0's 1,232 bytes but fit v1's 4,096), built by [api/_lib/solana/transaction-v1.js](api/_lib/solana/transaction-v1.js); the MCP server gives agents the identical mint with their own key (preview-first, `confirm:true` gated) plus a prepare/send lane for external wallets. Both consume one isomorphic builder library, and [tests](packages/metaplex-agent-mcp/test/genesis-shape.test.mjs) pin the output byte-for-byte to the live Genesis #332 URIs. Devnet is a free rehearsal lane end-to-end. A mainnet deploy also pays a flat 0.02 SOL fee to the $THREE buyback wallet, halved at 50k $THREE in the paying wallet and waived at 250k, disclosed in every preview and carried inside the create transaction ([packages/metaplex-agent-mcp/src/lib/three.js](packages/metaplex-agent-mcp/src/lib/three.js)); the `three_status` tool prices it against any wallet. || Solana Memo viewer | [public/onchain/index.html](public/onchain/index.html) `→ /onchain` | Live | A shareable, wallet-free reader for public Solana transaction Memos. It accepts a signature or Solscan transaction URL, requests version-1 transactions directly from the mainnet RPC, previews the supported raster data URI formats, provides a file download or text-copy action, and keeps each result tied to its signer, timestamp, and Solscan source. It refuses to execute active formats such as SVG because Memo content is untrusted. Docs: [docs/solana.md](docs/solana.md#viewing-files-written-in-a-transaction-memo). || Onchain agent wallets (spending allowances, not private keys) | [packages/onchain-agent-wallets/](packages/onchain-agent-wallets) (published as `@three-ws/onchain-agent-wallets`, MCP registry `io.github.nirholas/onchain-agent-wallets`) | Live | Give an agent a Solana wallet without giving it the money. Funds sit in a vault token account the OWNER owns, derived deterministically from the owner address plus the agent id (`createWithSeed(owner, "oaw1:<agent>")`); the agent holds only a capped SPL Token delegation over it, so the token program itself refuses any spend past the ceiling and decrements it on every transfer. Guardrails on top (per-tx, rolling daily, recipient and host allowlists, expiry, pause, confirm-above threshold) are enforced before signing, and every decision including refusals lands in a local ledger. `pay_x402` probes the price unpaid, checks it against the guardrails, tops the agent up for exactly that amount, pays, and leaves it empty. Owner actions need no key on the machine: they come back as unsigned transactions for Phantom/Solflare/Ledger. [Delegation tests](packages/onchain-agent-wallets/test/token-delegation.test.mjs) run the real SPL Token program in process and assert that 61 against a remaining allowance of 60 fails on-chain. || On-chain contracts (Solidity + Solana) | [contracts/](contracts) · [contracts/README.md](contracts/README.md) | Mixed: `ThreeWSPayments` + `ThreeWSFactory` live on BSC/Base/Arbitrum, the rest in-repo | Every contract and program three.ws owns, in one Foundry project plus three Anchor programs. ERC-8004 identity/reputation/validation registries (reference implementations of the canonical deployments the platform actually reads), the live x402 USDC receiver and its CREATE2 vanity factory, `AgentPayments`, `GreenfieldVault`, `WorldMoves`, and the Solana `skill_license` / `agent_invocation` programs. `forge test` covers the Solidity set with 242 tests across 8 suites; the Solana side is covered by the LiteSVM row below. Deploy status per contract and the address provenance per chain: [contracts/DEPLOYMENTS.md](contracts/DEPLOYMENTS.md) |diff --git a/data/changelog.json b/data/changelog.jsonindex 1077d98f9..fd6b4e58b 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -4,7 +4,7 @@{"date": "2026-09-16","title": "Deploy your agent on-chain with Solana's new transaction v1",- "summary": "Minting an agent to Solana now uses the new transaction v1 format whenever your wallet supports it, from both the agent deploy button and the registration wizard, including agents with a custom vanity address. Each deploy spells out its compute, account data, and priority fee limits instead of relying on defaults, and three.ws checks that the transaction that landed on-chain is the exact version it prepared before recording your agent. Wallets that have not added v1 yet keep working exactly as before, and a deployed agent now shows which transaction format it used.",+ "summary": "Minting an agent to Solana now uses the new transaction v1 format whenever your wallet supports it, from the agent deploy button, the registration wizard (vanity addresses included), and /deploy-onchain. On /deploy-onchain that turns a Genesis-shape deploy from two wallet transactions into one: the asset is created and registered in the Metaplex Agent Registry atomically, so there is no half-finished deploy if something fails in between. Each deploy spells out its compute, account data, and priority fee limits instead of relying on defaults, and three.ws checks that the transaction that landed on-chain is the exact version it prepared before recording your agent. Wallets that have not added v1 yet keep working exactly as before, and a deployed agent now shows which transaction format it used.","tags": ["feature","security"diff --git a/packages/metaplex-agent-mcp/README.md b/packages/metaplex-agent-mcp/README.mdindex 711658308..bacb89b08 100644--- a/packages/metaplex-agent-mcp/README.md+++ b/packages/metaplex-agent-mcp/README.md@@ -160,7 +160,7 @@ const mint = buildAgentMint(umi, {const { signatures, atomic } = await sendAgentMint(umi, mint, { toBase58Signature });```-The registration and metadata builders are also importable on their own (dependency-free, browser-safe) from `@three-ws/metaplex-agent-mcp/lib/registration`, and the transaction builders from `@three-ws/metaplex-agent-mcp/lib/mint`. The three.ws `/deploy-onchain` page runs on exactly these.+The registration and metadata builders are also importable on their own (dependency-free, browser-safe) from `@three-ws/metaplex-agent-mcp/lib/registration`, and the transaction builders from `@three-ws/metaplex-agent-mcp/lib/mint`. The three.ws `/deploy-onchain` page runs on exactly these. When `atomic` is `false`, `combinedBuilder` still holds the whole mint: compiled as a Solana transaction v1 (4,096-byte limit) it lands create + register in one atomic transaction, which is what `/deploy-onchain` does for any wallet that advertises v1 signing.## Requirementsdiff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 475eab6e7..0fdfbcd41 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-16T19:36:18.607Z",+ "generated_at": "2026-09-16T19:49:26.980Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -22,23 +22,24 @@{"date": "2026-09-16","type": "update",- "title": "$THREE pages now show the real buyback ledger instead of a burn estimate",- "summary": "The $THREE live page and the token dashboard used to show a \"$THREE burned\" total that was estimated from the number of agents on the platform, not read from the blockchain. The platform does not burn $THREE, so that number is gone. Both pages now show what the protocol actually commits to: the share of revenue set aside to buy $THREE on the open market, how much has been bought, and whether the buyback engine is running. The AWS page also no longer says Marketplace usage is billed to your AWS invoice; the subscription is free and usage is paid per call.",- "link": "/three-live",+ "title": "A cleaner launchpad for your 3D agent's coin, with rewards you claim right here",+ "summary": "three.ws/launch is rebuilt around one flow: pick one of your 3D agents, name the coin, and launch it on pump.fun from your wallet or from the agent's own wallet. The coin's metadata links your agent's page and 3D body, a live preview and cost panel show exactly what you will pay (including a 1% three.ws fee on the dev buy), and a new My coins tab shows unclaimed creator rewards and claims them in one click, no pump.fun app needed. Launches now fit in a single transaction thanks to pump.fun's lookup table, and larger ones, like USDC-paired coins with a dev buy, use Solana transaction v1 automatically when your wallet supports it. This also fixes launches that were failing because an on-chain buyback program stopped accepting new agents.",+ "link": "/launch","tags": [+ "feature",+ "improvement","fix"]},{"date": "2026-09-16","type": "update",- "title": "A cleaner launchpad for your 3D agent's coin, with rewards you claim right here",- "summary": "three.ws/launch is rebuilt around one flow: pick one of your 3D agents, name the coin, and launch it on pump.fun from your wallet or from the agent's own wallet. The coin's metadata links your agent's page and 3D body, a live preview and cost panel show exactly what you will pay (including a 1% three.ws fee on the dev buy), and a new My coins tab shows unclaimed creator rewards and claims them in one click, no pump.fun app needed. Launches now fit in a single transaction thanks to pump.fun's lookup table, and larger ones, like USDC-paired coins with a dev buy, use Solana transaction v1 automatically when your wallet supports it. This also fixes launches that were failing because an on-chain buyback program stopped accepting new agents.",- "link": "/launch",+ "title": "Deploy your agent on-chain with Solana's new transaction v1",+ "summary": "Minting an agent to Solana now uses the new transaction v1 format whenever your wallet supports it, from the agent deploy button, the registration wizard (vanity addresses included), and /deploy-onchain. On /deploy-onchain that turns a Genesis-shape deploy from two wallet transactions into one: the asset is created and registered in the Metaplex Agent Registry atomically, so there is no half-finished deploy if something fails in between. Each deploy spells out its compute, account data, and priority fee limits instead of relying on defaults, and three.ws checks that the transaction that landed on-chain is the exact version it prepared before recording your agent. Wallets that have not added v1 yet keep working exactly as before, and a deployed agent now shows which transaction format it used.",+ "link": "/deploy-onchain","tags": ["feature",- "improvement",- "fix"+ "security"]},{diff --git a/public/changelog.json b/public/changelog.jsonindex de70e42a0..6e1550de5 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-16T19:36:18.499Z",+ "generated_at": "2026-09-16T19:49:26.940Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -19,23 +19,24 @@{"date": "2026-09-16","type": "update",- "title": "$THREE pages now show the real buyback ledger instead of a burn estimate",- "summary": "The $THREE live page and the token dashboard used to show a \"$THREE burned\" total that was estimated from the number of agents on the platform, not read from the blockchain. The platform does not burn $THREE, so that number is gone. Both pages now show what the protocol actually commits to: the share of revenue set aside to buy $THREE on the open market, how much has been bought, and whether the buyback engine is running. The AWS page also no longer says Marketplace usage is billed to your AWS invoice; the subscription is free and usage is paid per call.",- "link": "/three-live",+ "title": "A cleaner launchpad for your 3D agent's coin, with rewards you claim right here",+ "summary": "three.ws/launch is rebuilt around one flow: pick one of your 3D agents, name the coin, and launch it on pump.fun from your wallet or from the agent's own wallet. The coin's metadata links your agent's page and 3D body, a live preview and cost panel show exactly what you will pay (including a 1% three.ws fee on the dev buy), and a new My coins tab shows unclaimed creator rewards and claims them in one click, no pump.fun app needed. Launches now fit in a single transaction thanks to pump.fun's lookup table, and larger ones, like USDC-paired coins with a dev buy, use Solana transaction v1 automatically when your wallet supports it. This also fixes launches that were failing because an on-chain buyback program stopped accepting new agents.",+ "link": "/launch","tags": [+ "feature",+ "improvement","fix"]},{"date": "2026-09-16","type": "update",- "title": "A cleaner launchpad for your 3D agent's coin, with rewards you claim right here",- "summary": "three.ws/launch is rebuilt around one flow: pick one of your 3D agents, name the coin, and launch it on pump.fun from your wallet or from the agent's own wallet. The coin's metadata links your agent's page and 3D body, a live preview and cost panel show exactly what you will pay (including a 1% three.ws fee on the dev buy), and a new My coins tab shows unclaimed creator rewards and claims them in one click, no pump.fun app needed. Launches now fit in a single transaction thanks to pump.fun's lookup table, and larger ones, like USDC-paired coins with a dev buy, use Solana transaction v1 automatically when your wallet supports it. This also fixes launches that were failing because an on-chain buyback program stopped accepting new agents.",- "link": "/launch",+ "title": "Deploy your agent on-chain with Solana's new transaction v1",+ "summary": "Minting an agent to Solana now uses the new transaction v1 format whenever your wallet supports it, from the agent deploy button, the registration wizard (vanity addresses included), and /deploy-onchain. On /deploy-onchain that turns a Genesis-shape deploy from two wallet transactions into one: the asset is created and registered in the Metaplex Agent Registry atomically, so there is no half-finished deploy if something fails in between. Each deploy spells out its compute, account data, and priority fee limits instead of relying on defaults, and three.ws checks that the transaction that landed on-chain is the exact version it prepared before recording your agent. Wallets that have not added v1 yet keep working exactly as before, and a deployed agent now shows which transaction format it used.",+ "link": "/deploy-onchain","tags": ["feature",- "improvement",- "fix"+ "security"]},{diff --git a/public/changelog.xml b/public/changelog.xmlindex 9b4b5f39d..4bb60cc93 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -14,14 +14,6 @@<category>launch</category><description>How three.ws/launch launches a pump.fun coin for a 3D agent: agent-linked metadata, the 1% dev-buy fee, v0 lookup-table and Solana transaction v1 formats, claiming creator rewards on three.ws, and the API behind it.</description></item>- <item>- <title>$THREE pages now show the real buyback ledger instead of a burn estimate</title>- <link>https://three.ws/three-live</link>- <guid isPermaLink="false">2026-09-16:$THREE pages now show the real buyback ledger instead of a burn estimate</guid>- <pubDate>Wed, 16 Sep 2026 12:00:00 GMT</pubDate>- <category>fix</category>- <description>The $THREE live page and the token dashboard used to show a "$THREE burned" total that was estimated from the number of agents on the platform, not read from the blockchain. The platform does not burn $THREE, so that number is gone. Both pages now show what the protocol actually commits to: the share of revenue set aside to buy $THREE on the open market, how much has been bought, and whether the buyback engine is running. The AWS page also no longer says Marketplace usage is billed to your AWS invoice; the subscription is free and usage is paid per call.</description>- </item><item><title>A cleaner launchpad for your 3D agent's coin, with rewards you claim right here</title><link>https://three.ws/launch</link>@@ -30,6 +22,14 @@<category>feature</category><description>three.ws/launch is rebuilt around one flow: pick one of your 3D agents, name the coin, and launch it on pump.fun from your wallet or from the agent's own wallet. The coin's metadata links your agent's page and 3D body, a live preview and cost panel show exactly what you will pay (including a 1% three.ws fee on the dev buy), and a new My coins tab shows unclaimed creator rewards and claims them in one click, no pump.fun app needed. Launches now fit in a single transaction thanks to pump.fun's lookup table, and larger ones, like USDC-paired coins with a dev buy, use Solana transaction v1 automatically when your wallet supports it. This also fixes launches that were failing because an on-chain buyback program stopped accepting new agents.</description></item>+ <item>+ <title>Deploy your agent on-chain with Solana's new transaction v1</title>+ <link>https://three.ws/deploy-onchain</link>+ <guid isPermaLink="false">2026-09-16:Deploy your agent on-chain with Solana's new transaction v1</guid>+ <pubDate>Wed, 16 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>Minting an agent to Solana now uses the new transaction v1 format whenever your wallet supports it, from the agent deploy button, the registration wizard (vanity addresses included), and /deploy-onchain. On /deploy-onchain that turns a Genesis-shape deploy from two wallet transactions into one: the asset is created and registered in the Metaplex Agent Registry atomically, so there is no half-finished deploy if something fails in between. Each deploy spells out its compute, account data, and priority fee limits instead of relying on defaults, and three.ws checks that the transaction that landed on-chain is the exact version it prepared before recording your agent. Wallets that have not added v1 yet keep working exactly as before, and a deployed agent now shows which transaction format it used.</description>+ </item><item><title>GitHub fee claims now say what they actually prove</title><link>https://three.ws/pumpfun</link>diff --git a/public/features.json b/public/features.jsonindex 93305cc53..23a47427f 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-16T19:36:18.426Z",+ "generated_at": "2026-09-16T19:49:26.734Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",