Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(finish): trim order 957 to the launcher deploy and first owner-run launch, the only steps still gated

nirholas8dcfcf08cf2a
diff --git a/prompts/finish/957-uniswap-lane-and-launch-status.md b/prompts/finish/957-uniswap-lane-and-launch-status.md
index a946a2e80..fde7e89d1 100644
--- a/prompts/finish/957-uniswap-lane-and-launch-status.md
+++ b/prompts/finish/957-uniswap-lane-and-launch-status.md
@@ -1,9 +1,6 @@
-Our launch lanes are pump.fun, Meteora DBC and a Robinhood Chain paired launch (api/_lib/paired-launchpad.js, api/_mcp/tools/paired.js with paired_launch_quote and paired_launch). There is no standalone Uniswap lane, and the paired launch has no idempotency key and no status endpoint, so a client that times out cannot tell whether a launch happened.
+Remaining from this order (everything else shipped and verified: lane config and picker, idempotent EVM launches, GET /api/launches/:id, generated docs/launch-lanes.md, 18 launcher contract tests passing on a Base mainnet fork).
-Add an Uniswap lane on an EVM chain we already support: a fixed-supply token with a pool created through Uniswap's contracts or a maintained SDK, with creator fee routing, liquidity lock options, and a quote that lists every fee. Solana remains the default lane and must be unaffected. For both EVM lanes add an Idempotency-Key header, a persisted launch record, and GET /api/launches/:id that reports stages until finalized, so a retry returns the same launch. Wire the existing launch wizard to a lane picker that compares fees, graduation behaviour, creator share and chain from live config.
+1. Owner deploys the launcher contract on Base from contracts/src/ThreeWsUniswapLauncher.sol (deploy script in contracts/script), then sets UNISWAP_LAUNCHER_ADDRESS on the three-ws-api Cloud Run service with `gcloud run services update --update-env-vars`. Until then GET /api/launches/lanes reports the lane as unavailable with that reason. Deploying is an owner-gated, irreversible on-chain action.
+2. Owner-run first real launch through /launch/uniswap with the confirmation table, then `GET /api/launches/:id` until finalized. Confirm the Idempotency-Key retry returns the same record.
-Spend gate applies: the wizard shows the confirmation table and signs only after an explicit yes. Test on a testnet or fork; a real launch is the owner's action. Document each lane with a table generated from the lane config.
-
----
-
-This brief is standalone. Assume no other brief has run, and keep working if others run at the same time: use names unique to this work for tables, routes and files, give migrations a fresh timestamp, append to shared files instead of rewriting them, and re-read a shared file before you edit it. CLAUDE.md governs everything, including its spend gate (anything that signs or moves funds shows recipient, amount, asset and chain and waits for an explicit yes; test with devnet, simulation or paper mode) and the rule that nothing naming another crypto project is committed without the owner's approval, so list any new third-party names you introduce in your report. Never name any competitor in a committed file. Finish it fully: wire it, document it, add the changelog entry, verify it for real, and report what you observed.
+Spend gate and the commit gate in CLAUDE.md apply. Never name any competitor in a committed file.