> 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/readme.md). # Trover docs ## Operations * `runbook.md`: operator runbook; backend deploy procedure, Postgres settings, the known server condition, incident checks, X and key rotation, emergency stops. * `production-environment.md`: every production environment key for Vercel, Privy and the backend server, and how to change the server `.env`. * `RPC-COST-CONTROL.md`: RPC pool layout (`url|rps=|lanes=|cu=`), free-first tiered transport, the Alchemy ceiling, the 15-minute "RPC usage" meter and the measured endpoints. * `RUNBOOK-dex-overhaul.md`: deployment runbook for the 2026-08-27 DEX overhaul (indexer env, first-day behaviour, smoke test). * `trading-runbook.md`: launch, pause and recovery steps for stock-token trading. * `integration-testing.md`: the live-provider Docker suite and Robinhood testnet testing. * `contracts-runbook.md`: contract inventory, deploy-stack, testnet rehearsal, backups and Safe rescue paths. * `x-agent-setup.md`: what remains in `.env` to bring the X agent up under `@troveragent`. * `x-mcp.md`: the operator-only stdio bridge to X's hosted MCP. ## Architecture and product * `architecture.md`: data flow, identity priority, risk and confidence, the NFT market pipeline, schedules, security boundaries. * `agent-orchestration.md`: capability-driven agent runs across web, X mentions and DMs, including the NFT read capabilities. * `customer-mcp.md`: the OAuth-protected customer MCP at `api.trover.tech/mcp`. * `chatgpt-mcp-submission/README.md`: ChatGPT directory submission for the customer MCP; `test-prompts.md` beside it holds the review prompts. * `opensea-marketplace.md`: OpenSea integration and execution boundary, with a current-state preface (chain first, OpenSea fallback); the Trover Planets sections are historical. * `NFT-REALTIME-ROLLOUT-2026-08-28.md`: the websocket sale ingestor rollout, with a current-state preface (lane naming, verdicts, repair job). * `token-economics.md`: the four-way fee split, balance-weighted stock distributions, buyback and burn, league. * `stabledex.md`: the Stable Mainnet on-chain market terminal. * `stock-token-trading.md`: buy, sell and hold commands, wallet capability modes, policy. * `routing-and-pons-launchpad.md`: Uniswap routing on Robinhood Chain and Pons launches. * `relay-bridging.md`: Relay cross-chain bridging and its RPC configuration. * `basket-vault.md`: the static basket vault specification. * `claim-system-design.md`: the pull-based Merkle stock claim distributor. * `claims-fees-and-operations.md`: the internal panel, claims, fees and treasury operations. * `social-claims.md`: social X claims and Pons creator-fee claims. * `privy-automation.md`: one-time Privy delegated-signer enrollment. * `trover-privy-auth.md`: production authentication checklist. * `prompts-and-examples.md`: normalizer and composer prompt examples. ## Data files * `robinhood-pools.csv`, `robinhood-pools.sql`: Robinhood Chain pool seed data. ## Change records (by date) Each VERIFY file records one round: what was measured, what changed, the deploy commands and how to verify. They are history; the documents above are the current state. * `VERIFY-2026-08-28.md`: Discover page (trending, new mints, market) and the session's later rounds. * `VERIFY-2026-08-31-jobid.md`: BullMQ job ids without colons; dex-host `/nfts` rewrite. * `VERIFY-2026-08-31-mints.md`: on-chain mint indexing turned on. * `VERIFY-2026-08-31-price-decimals.md`: raw payment units were read as whole units. * `VERIFY-2026-08-31-wallet-send-and-health.md`: wallet fan-out send, 1m chart default, stat and health repair. * `VERIFY-2026-09-01-advanced-charts.md`: TradingView Advanced Charts on the token terminal. * `VERIFY-2026-09-01-chain-first-nft.md`: chain-first NFT ingestion and the per-sale scatter; `nft_token_metadata` migration. * `VERIFY-2026-09-02-nft-chain-head.md`: the scanners hold the chain head; the unapplied migration that blanked eleven tiles. * `VERIFY-2026-09-04-db-guardrails.md`: statement timeouts, connection limits, caching and retention. * `VERIFY-2026-09-04-nft-identity-columns.md`: filling the trending board's identity columns. * `VERIFY-2026-09-04-nft-trending-board.md`: the NFT trending board and its window index. * `VERIFY-2026-09-04-traders-and-rpc.md`: trader leaderboard and profiles; Dwellir cannot serve `eth_getLogs`; Ink block-range refusals. * `VERIFY-2026-09-05-instant-activity.md`: instant activity, duplicate collections, images, mint stats; the realtime service found dead. * `VERIFY-2026-09-05-mint-lifecycle.md`: mint lifecycle columns, drop schedules, the missed sale. * `VERIFY-2026-09-05-queue-loading-floor.md`: queue drain, loading states, floor grid. * `VERIFY-2026-09-05-round1-fixes.md`: degraded state, instant drops, sold-in-place, decimals, RPC spend (signer split, no `net_listening`, block-time cache). * `VERIFY-2026-09-05-round2-snipe.md`: reveal sniping tables and jobs. * `VERIFY-2026-09-06-rejected-sales-and-oom.md`: 85% of live fills stored rejected; worker heap (scan pile-up, OpenSea cache, swap tape); wrong-chain rows; Alchemy spend and the tiered pool. * `VERIFY-2026-09-07-rate-limits-and-soldout.md`: 429s were our own limiter behind the tunnel; per-visitor 600/min; OpenSea pacing and reserve; sold-out presentation. * `VERIFY-2026-09-07-discovery-live.md`: worker-warmed discovery lists, stale-while-revalidate page, per-chain scanner guards, batched mint writes, Postgres settings, the gap marker, per-network leaderboards. * `VERIFY-2026-09-08-agent-nft-reads.md`: twelve NFT agent capabilities, MCP reads, `contract-balance-watch`. * `VERIFY-2026-09-08-token-economics.md`: the NFT idea dropped; token stack, buyback keeper, economics route, admin-page deployer, Trovernomics rewrite. * `VERIFY-2026-09-09-terminal-orders-and-disk.md`: drag-scroll tab rows, limit line on both charts, owned-count fix, snipe wallet gate fix, active orders with cancel, internal sandbox, diff-based worker writes. * `VERIFY-2026-09-13-opensea-pool-chain-history.md`: OpenSea key pool, per-collection chain history backfill, renamed-slug merge, mint eligibility and card, bottom status bar, OG/copycat. * `PLAN-2026-09-13-fees-and-referrals.md`: 1% on every trade, referral links, daily referral league. * `VERIFY-2026-09-13-fees-round-1.md`: executor v2 with per-call capped fee; every Robinhood trade routed through it. * `VERIFY-2026-09-13-fees-round-2-referrals.md`: fee ledger, NFT marketplace fee, referral links, daily referral league (migration). * `VERIFY-2026-09-13-fees-round-3-split.md`: fees always in the settlement asset (executor v3), daily fee split 35/8/7/20/30, agent buys by name, site fee copy, GitBook source. * `dune-dashboard.md`: Dune queries for Trover DEX trades on Robinhood Chain (attribution by wallet set, then the fee executor), assembly steps. * `VERIFY-2026-09-08-contracts-rescue-paths.md`: rescue paths on every ETH-holding contract, two-road levels, deploy-stack and Safe rescue CLI. * `VERIFY-2026-09-08-design-deslop.md`: fonts shipped, `StateChip` replaces status dots, flat cards, 11 px floor, Trovernomics page. --- # 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/readme.md?ask=&goal= ``` `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.