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(prompts): log order 512's gate, mainnet config creation stays owner-only

nirholascc12705836ef
diff --git a/prompts/finish/512-integrate-13-anti-snipe-native-lane.md b/prompts/finish/512-integrate-13-anti-snipe-native-lane.md
index 7256a5f75..29b33eb28 100644
--- a/prompts/finish/512-integrate-13-anti-snipe-native-lane.md
+++ b/prompts/finish/512-integrate-13-anti-snipe-native-lane.md
@@ -1,5 +1,7 @@
# integrate 13: a decaying anti-snipe fee on the native $THREE launch lane
+**Evolve status (2026-10-14):** every task and every Definition of done line this session can verify is done: the curve config, both test suites, the devnet e2e run, and the docs/changelog. One line remains, and it is the owner's by design: creating the mainnet curve config (`node scripts/native-launchpad-create-config.mjs --network mainnet`, about 0.006 SOL). See [row 64 of production-100-OWNER-ACTIONS.md](_context/production-100-OWNER-ACTIONS.md) for the exact command and the env pin that follows it. This file stays in place until that row is actioned; retire it then per the close-out steps below.
+
How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now; one gated step, named below.
## Operating clause (binding)
diff --git a/prompts/finish/_context/integrate-PROGRESS.md b/prompts/finish/_context/integrate-PROGRESS.md
index cb0cf17ca..a7a2465b8 100644
--- a/prompts/finish/_context/integrate-PROGRESS.md
+++ b/prompts/finish/_context/integrate-PROGRESS.md
@@ -606,3 +606,64 @@ landed, so no `STRUCTURE.md` row or `data/pages.json` entry was needed.
Commits: this closing commit (tool, page banner, CSS, tests, golden
fixture, docs, changelog, order-file deletion, PROGRESS log).
+
+## 2026-10-14: order 512-integrate-13 stopped on a gate (evolve)
+
+Switched the native $THREE launch lane's curve from a flat 1% trading fee to
+a decaying anti-snipe schedule in `api/_lib/native-launch/config.js`:
+`fee.baseFeeParams` now sets `BaseFeeMode.FeeSchedulerExponential` with a
+50% starting fee (`antiSnipeStartFeeBps`) decaying to the steady-state 1%
+(`antiSnipeEndFeeBps`, equal to the existing `tradeFeeBps`) over 25 periods
+across 100 slots (`antiSnipeDecayPeriods` / `antiSnipeDecaySlots`, about 40
+seconds). `RateLimiter` was ruled out, not just compared: the SDK's own
+`getBaseFeeParams()` throws "BaseFeeMode.RateLimiter is deprecated" for any
+new config in this SDK version, which settles the measurement the task
+asked for before reaching devnet. `enableFirstSwapWithMinFee` stays on so
+only the creator's pool-creation-bundled first buy is exempt. `laneInfo()`
+now serves the schedule under a new `anti_snipe` key (additive, checked
+against every existing consumer of the spread object before adding it).
+
+Verified: `npx vitest run tests/native-launch-curve.test.js` passes 20/20,
+including four new cases asserting the fee starts at 5000 bps, decays
+monotonically slot by slot, reaches exactly 100 bps at slot 100 and stays
+there past it, and taxes slot 2 at more than 10x the steady-state fee.
+`scripts/native-launchpad-e2e-devnet.mjs` now quotes an identical 1,000
+$THREE buy at pool activation and again 21 slots later; because the public
+devnet faucet is rate-limited (confirmed: `-32603` then an explicit `429`
+"airdrop faucet has run dry", and no funded devnet key exists anywhere in
+this worktree's env or GCP Secret Manager), the run used a local
+`solana-test-validator` cloning the real DBC, Token-2022, ATA, and Metaplex
+Token Metadata programs directly off devnet (the documented fallback in
+`docs/draft-agent-mint.md`), which executes byte-identical on-chain program
+logic with unlimited local airdrops. Real output: the fee for the same
+buy dropped from 400.040459 $THREE to 156.523092 $THREE over those 21
+slots, a real signed devnet-program transaction decaying the way the
+schedule says it should. The new schedule was also confirmed directly
+against the live mainnet DBC program via the script's existing zero-cost,
+keyless `--simulate` flag: `simulation OK: config + a $THREE-quoted pool
+created by the live DBC program (144429 compute units)`.
+`scripts/native-launchpad-create-config.mjs` needed no code change: both
+its `--simulate` and real `--network` paths already share the one
+`curveBuildParams()` call that config.js's edit updated. `docs/native-
+launchpad.md` gained an "Anti-snipe: a decaying fee instead of a flat one"
+section (the schedule, why exponential over linear/RateLimiter, and the
+one honest EVM difference: the anti-snipe premium flows through the same
+creator/platform split every trade uses, never to LPs, since DBC pools
+have no third-party LPs pre-graduation) and its curve table row. `data/
+changelog.json` got a new entry and `npm run build:pages` ran clean.
+`npm run check:rules --paths <all 5 touched source/docs files>` exits 0.
+
+What cannot finish from this session: creating the mainnet curve config is
+the on-chain write this order named up front as the one gated step (about
+0.006 SOL). Confirmed before naming the owner action that this is a
+first-time activation, not a change to a live config: `gcloud run services
+describe three-ws-api --region us-central1` lists zero `NATIVE_LAUNCH_*`
+env vars in production today. See [row 64 of
+production-100-OWNER-ACTIONS.md](production-100-OWNER-ACTIONS.md) for the
+exact `node scripts/native-launchpad-create-config.mjs --network mainnet`
+command, its funding requirement, and the env-pin command that follows it.
+Leaving `512-integrate-13-anti-snipe-native-lane.md` in place with a dated
+Evolve status paragraph rather than deleting it.
+
+Commits: this closing commit (curve config, tests, e2e script, docs,
+changelog, owner-actions row, order-file annotation, PROGRESS log).
diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.md
index 75244a3e0..7c11dadee 100644
--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md
+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md
@@ -79,6 +79,8 @@ on it; some resolve themselves as other work lands.
| 63 | **Apply the per-coin earnings timeline migration, and only then deploy** (added 2026-10-14 by the evolve loop closing out order 510-integrate-11). `api/_lib/pump-creator-fees.js` now sums each coin's own pump.fun distribution timeline (`fetchCoinEarnings`) alongside the existing wallet-level fee index, and `api/_lib/creator-earnings-snapshot.js` reconciles the two into five new `agent_coin_earnings` columns (`coin_earned_lamports`, `coin_distributions`, `coin_earnings_source`, `reconciliation_delta_lamports`, `reconciliation_pct`). The migration (`api/_lib/migrations/20261015090000_agent_coin_earnings_timeline.sql`) is written and verified idempotent and syntactically correct via a throwaway PGlite run, never against production. Exact apply command: `npm run db:migrate -- --apply --file 20261015090000_agent_coin_earnings_timeline.sql` (read `npm run db:status` first; this applies immediately with no dry run, and the shared worktree may have other agents' unrelated pending migrations queued, so review the full pending list before running). Critical ordering note: `api/pump/launch-detail.js`'s `creatorFeesFor()` and `api/_lib/agent-earnings.js`'s `getAgentEarnings()` both now select the new columns in the SAME query as the pre-existing ones, so if this commit's code reaches production before the migration lands, that combined select throws `column "coin_earned_lamports" does not exist` on every call; the pre-existing `.catch(() => null)` wrapper around `creatorFeesFor()` silently swallows it, degrading `economics.creator_fees` to `null` for every coin (not just the new fields) until the migration is applied. Apply the migration before (or as part of) the next deploy that includes this diff, not after. | one `npm run db:migrate -- --apply` run, timed before the next deploy | Restores and extends per-coin creator-earnings data (`economics.creator_fees`) with a second, independent, reconciled source instead of risking it going silently null | [510-integrate-11-per-coin-earnings-source.md](../510-integrate-11-per-coin-earnings-source.md) |
| 61 | **Push and archive 7 retired repos** (added 2026-10-14 by the evolve loop closing out order 503-integrate-04). `data/retired-repos.json` lists `three-ui`, `crypto-market-data`, `crypto-market-data-ts`, and `crypto-data-aggregator` (all superseded by the `/markets` page or `src/` in this monorepo), `memescope-monday-directory` (duplicate of `memescope-monday`), and one repo from each of the two Robinhood Chain duplicate pairs (`robinhood-chain-alert-bot`, duplicate of `robinhood-chain-alerts`; `robinhood-chain-trading-bot`, duplicate of `robinhood-chain-traders`). `npm run retire:repos` staged a one-commit pointer README under `dist/retired-repos/<repo>/` for each, explaining the retirement and linking to the replacement; it never calls `gh` and never pushes. To approve, run these 14 commands (7 pushes, 7 archives): `git -C dist/retired-repos/three-ui push --force https://github.com/nirholas/three-ui.git HEAD:main && gh repo archive nirholas/three-ui --yes`, `git -C dist/retired-repos/crypto-market-data push --force https://github.com/nirholas/crypto-market-data.git HEAD:main && gh repo archive nirholas/crypto-market-data --yes`, `git -C dist/retired-repos/crypto-market-data-ts push --force https://github.com/nirholas/crypto-market-data-ts.git HEAD:main && gh repo archive nirholas/crypto-market-data-ts --yes`, `git -C dist/retired-repos/crypto-data-aggregator push --force https://github.com/nirholas/crypto-data-aggregator.git HEAD:main && gh repo archive nirholas/crypto-data-aggregator --yes`, `git -C dist/retired-repos/memescope-monday-directory push --force https://github.com/nirholas/memescope-monday-directory.git HEAD:main && gh repo archive nirholas/memescope-monday-directory --yes`, `git -C dist/retired-repos/robinhood-chain-alert-bot push --force https://github.com/nirholas/robinhood-chain-alert-bot.git HEAD:main && gh repo archive nirholas/robinhood-chain-alert-bot --yes`, `git -C dist/retired-repos/robinhood-chain-trading-bot push --force https://github.com/nirholas/robinhood-chain-trading-bot.git HEAD:main && gh repo archive nirholas/robinhood-chain-trading-bot --yes`. `dist/` is gitignored, so re-run `npm run retire:repos` first if the staged trees were cleaned since this session. | 7 pushes + 7 archives | Removes 7 stale/duplicate public repos from the owner's GitHub without losing their history (each gets a pointer commit first) | [503-integrate-04-robinhood-copies-and-retired-repos.md](../503-integrate-04-robinhood-copies-and-retired-repos.md) (retired this session; see `_context/integrate-PROGRESS.md`) |
+| 64 | **Create the mainnet native-launchpad curve config and pin it, activating the lane** (added 2026-10-14 by the evolve loop closing out order 512-integrate-13). `api/_lib/native-launch/config.js`'s curve now opens every pool at a 50% anti-snipe trading fee that decays exponentially to the steady-state 1% over the first 100 slots (Meteora DBC's own fee scheduler, verified by `tests/native-launch-curve.test.js`, a devnet e2e run against a local validator cloning the real DBC/Token-2022/ATA/Metaplex programs, and a zero-cost `--simulate` run against the live mainnet DBC program). Production currently has zero `NATIVE_LAUNCH_*` env vars set (`gcloud run services describe three-ws-api --region us-central1` env list checked), so this is first-time lane activation, not a change to a live config; no existing launch is affected. Exact command: `node scripts/native-launchpad-create-config.mjs --network mainnet`, needing `NATIVE_LAUNCH_PARTNER_SECRET_BASE58` (or `X402_TREASURY_SECRET_BASE58` as a fallback signer) funded with at least 0.05 SOL in that wallet (the script's own balance floor for rent + fees headroom); the on-chain spend itself is about 0.006 SOL (this order's own estimate for the `createConfig` transaction's rent and fee). Optionally set `NATIVE_LAUNCH_FEE_WALLET` first if the platform's fee claimer should be a wallet other than the signer. The script prints the created config pubkey and the exact env line to pin; run `gcloud run services update three-ws-api --region us-central1 --update-env-vars NATIVE_LAUNCH_CONFIG_KEY=<printed pubkey>` (config-only, pre-approved) to put the lane live. | one `node scripts/native-launchpad-create-config.mjs --network mainnet` run (~0.006 SOL) + one `gcloud run services update --update-env-vars` pin | Activates the native $THREE launchpad lane on mainnet with the decaying anti-snipe fee baked into the curve from the very first launch | [512-integrate-13-anti-snipe-native-lane.md](../512-integrate-13-anti-snipe-native-lane.md) |
+
Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), which
declared itself "delete on reading" and had outlived that by three weeks.