> For the complete documentation index, see [llms.txt](https://docs.trover.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trover.tech/engineering/verify-2026-09-08-token-economics.md).

# Verify 2026-09-08: token economics (NFT idea dropped)

Migration status: **none**. No Prisma schema change; the admin manifest lives in Redis (`trover:contract-stack-manifest:v1:<chainId>`), the buyback ledger uses the existing `TreasuryLedgerEntry` (`entryType = buyback_burned`).

## What changed

Contracts (`packages/contracts`): planets, renderer, agent progress and the SeaDrop base removed; `TroverBuybackBurn` added; router splits four ways per source (35/15/20/30 holders/league/burn/treasury, `setSplit`); deploy and rescue scripts accept a single-signer admin; testnet 46630 deployed and rehearsed (39 steps, `deployments/robinhood-46630-{stack,rehearsal}.json`).

Backend: worker `buyback-burn` (10 min; keeper = claim-automation account; deepest WETH/TROVER v3 pool; QuoterV2; SwapRouter02 calldata into `buyAndBurn`; dry-run first; ledger entry), `GET /v1/token/economics`, `GET|PUT /v1/admin/contracts/manifest`, `/v1/nft-market/trover` removed, agent capability `nft_trover` → `token_economics` (`read_token_economics`) on web chat, X and MCP.

Web: Trovernomics page rewritten (split, holders, buyback, league, rescue, live counters via `TokenEconomicsLive`), Orbits page and components removed (header link, sitemap, SEO, i18n), Planets probe removed from both NFT terminals, `/api/nft/contract-metadata` removed, admin page gains "Deploy the token stack" (`ContractStackDeployer`, artifacts in `apps/web/src/lib/contracts/stack-artifacts.json`).

Docs: `nftomics-tokenomics.md` → `token-economics.md`; `contracts-runbook.md`, `STATUS-2026-09-08.md`, `agent-orchestration.md`, `customer-mcp.md`, `x-agent-setup.md`, `opensea-marketplace.md` (historical note), `README.md`.

## Checks run

* `tsc --noEmit`: core, domain, api, worker, web clean.
* Contract suite (user-authorised for the testnet work): 17 passing.
* Testnet: `deploy:stack:testnet` (9 assertions) and `rehearse:testnet` (39 steps, `REHEARSAL_EXIT=0`).

## Checks for you

1. `/tokenomics` on trover.tech after the Vercel build: the chip reads "token not launched" until `BUYBACK_BURN_ADDRESS` is set on the server, then "live"; no planet or orbit copy anywhere (`/orbits` is a 404).
2. `/internal` → "Deploy the token stack": pick testnet, connect a wallet with test ETH, type `DEPLOY 46630`, deploy; the record shows six addresses and 9/9 assertions. Reload the page: the record persists and the button reads "re-run checks".
3. Web chat or MCP: "how much TROVER has been burned" → the `token_economics` reply (before launch: "token not launched; buybacks start after the Pons launch").
4. `curl https://api.trover.tech/v1/token/economics` → JSON with `split`, `buyback`, `holders`, `league`, `servedAt`.

## Deploy

Frontend: pushed to `main`, Vercel builds.

Backend (one deploy at a time, detached):

```
ssh trevor-server
cd ~/trover && git pull --ff-only origin main
nohup bash -c 'set -x; docker compose -f docker-compose.yml -f docker-compose.production.yml build api worker && docker compose -f docker-compose.yml -f docker-compose.production.yml up -d --no-deps api worker; echo DEPLOY_EXIT=$?' > deploy-$(date +%Y%m%d-%H%M).log 2>&1 &
```

After mainnet deployment of the stack (from the admin page), add to the server `.env` (backup first): `OPENSEA_REVENUE_ROUTER_ADDRESS`, `BUYBACK_BURN_ADDRESS`, `ETH_CLAIM_DISTRIBUTOR_ADDRESS`, `SOCIAL_CLAIM_ESCROW_ADDRESS`, `AUTO_INVEST_FEE_EXECUTOR_ADDRESS`, `LEAGUE_VAULT_ADDRESS`; after the token launch `BUYBACK_ENABLED=true`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trover.tech/engineering/verify-2026-09-08-token-economics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.