> For the complete documentation index, see [llms.txt](https://gotts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gotts.gitbook.io/docs/website/website/landing-page/01-overview.md).

# Landing Page Overview

> **Last Updated**: 2026-02-18 **Status**: Draft (v0.1) — living document, iterated as product decisions are finalized
>
> For market data backing all claims in this document, see [prd/shared/market-context.md](/docs/prd-shared/market-context.md). For terminology, see [prd/shared/glossary.md](/docs/prd-shared/glossary.md).

***

## Table of Contents

1. [Overview](#1-overview)
2. [Problem Statement](#2-problem-statement)
3. [Market Context — Why Now](#3-market-context--why-now)
4. [Target Personas](#4-target-personas)
5. [Product Suite](#5-product-suite)
6. [Security Architecture](#6-security-architecture)
7. [Reputation System](#7-reputation-system)
8. [Protocol Economics](#8-protocol-economics)
9. [Uniswap Integration](#9-uniswap-integration)
10. [Key Standards](#10-key-standards)
11. [Developer Resources](#11-developer-resources)
12. [Non-Goals](#12-non-goals)
13. [Open Questions](#13-open-questions)
14. [Glossary](#14-glossary)

***

## 1. Overview

**Product name:** Gotts **Tagline:** No Safer Place **Live at:** `gotts.ai` **Positioning:** The bank for sovereign AI agents — permissionless vaults, cryptographic custody, and a reputation system that compounds on-chain. Built entirely on Uniswap and secured by fifteen independent layers of defense.

Gotts is sovereign wealth infrastructure for autonomous AI agents. It provides four composable primitives — a vault, a custody layer, an MCP server, and an agent execution network — that together give any AI agent a complete financial backend in a single transaction.

The protocol deploys on EVM chains (Ethereum and Base) and is powered end-to-end by Uniswap (V2, V3, V4, and UniswapX). Every vault deployed creates a permanent, structural source of Uniswap volume driven by vault lifecycle logic, not market sentiment.

***

## 2. Problem Statement

Agent Capital Markets arrived without infrastructure.

Autonomous AI agents accumulating capital, executing transactions, and managing on-chain strategies had no infrastructure built for them as first-class actors. The available options — Yearn vaults, Morpho markets, human-oriented custodians — were designed for human depositors and lacked:

* **Identity.** Agents had wallets, not verifiable on-chain identities. No protocol could gate access based on an agent's track record.
* **Safe custody.** Private keys either lived in agent memory (a single prompt injection away from compromise) or in human-operated hardware with no agent-native access model.
* **Reputation.** There was no persistent, portable record of an agent's behavior that could compound into financial leverage over time.
* **Payment rails.** Agent-to-agent and agent-to-service payments required API keys, invoices, and human-managed accounts — none of which an autonomous agent can maintain.
* **Execution infrastructure.** No permissionless, decentralized network existed to execute vault lifecycle jobs (rebalancing, harvesting, liquidation) without a trusted human operator.

Gotts is the institution that was missing.

***

## 3. Market Context — Why Now

Three infrastructure forces converged in the 90 days prior to launch, creating a unique window. For the full dataset, see [prd/shared/market-context.md](/docs/prd-shared/market-context.md).

### 3.1 ERC-8004 — Agent identity is now a standard

* **Live on Ethereum mainnet:** January 29, 2026
* Co-authored by engineers at MetaMask and Google
* Establishes on-chain identity, reputation, and validation registries for autonomous AI agents
* Designated a strategic priority by the Ethereum Foundation's dAI Team
* Gotts is among the first protocols to build on it at launch

### 3.2 x402 — Agent payments reached scale

* **Launched:** May 2025
* **Volume:** 100M+ agent-to-agent transactions processed
* x402 protocol (Cloudflare) with \~200ms settlement on Base
* v2 added wallet-based identity, automatic API discovery, and multichain via CAIP standards
* Google's AP2 (Agent Payments Protocol) enables machine-to-machine micropayments alongside x402 (60+ organizations)
* Gotts uses x402 in both directions: agents pay for external data per-request in USDC; the Gotts MCP Server exposes its own endpoints as x402-gated resources

### 3.3 Base L2 — The dominant L2 for AI agent activity

* **46.6% of all L2 DeFi TVL** (\~$4.63B)
* 7–10M daily transactions; 62% of total L2 revenue
* This creates a structural tailwind for agent infrastructure built on Base

### 3.4 Uniswap V4 — Hooks are production-ready

* Live since January 2025; surpassed **$1B TVL** with **2,500+ hook-enabled pools**
* 150+ hooks developed; AI-agent-related implementations emerging
* Projects like Bunni v2 (\~59% of V4 hook volume), Clanker ($5B+ agent token volume), and Flaunch ($75.6M V4 volume) demonstrate hooks are proven infrastructure

### 3.5 Broader AI Agent Capital Markets

| Metric                                          | Figure                                 |
| ----------------------------------------------- | -------------------------------------- |
| AI agent token market cap                       | $7.7B+ with $1.7B daily trading volume |
| Uniswap transactions from bots/agents (Messari) | \~70%                                  |
| BankrBot autonomous agents                      | 220K+ wallets, 2M+ messages            |
| Olas autonomous transactions                    | 9.9M+ agent-to-agent                   |
| Agent-to-agent x402 transactions                | 100M+                                  |

***

## 4. Target Personas

### Persona 1 — AI Agent Developers

**Who:** Engineers and teams building autonomous AI agents that need to interact with DeFi.

**Pain today:** Writing financial infrastructure from scratch — custody, yield, payment rails — is expensive, risky, and not the core product. Each piece requires specialized knowledge of different protocol interfaces.

**What Gotts gives them:** A complete financial backend in one transaction. Register via ERC-8004, deploy a vault, and immediately have custody, yield, reputation, and payment rails — with zero financial infrastructure code written.

**Key value props:**

* One-transaction setup
* 147 typed MCP tools pluggable into any MCP-compatible agent framework (Claude, GPT-4o, Cursor agents)
* x402 payment rails built in — no API keys or accounts receivable
* Pre-flight simulation on every write operation

***

### Persona 2 — Yield Strategists

**Who:** Individuals or teams that want to run on-chain yield strategies autonomously, 24/7, without a human operator in the loop.

**Pain today:** Automated strategies require either centralized infrastructure (trusted bots) or bespoke on-chain code with no composability. Rebalancing optimization requires constant attention.

**What Gotts gives them:** A vault with a bounded strategy managed by the agent network — with the 15-layer security stack ensuring no single point of failure can drain it.

**Key value props:**

* Auto-compounding yield via Uniswap V4 hooks, Morpho, Aave, and Pendle
* am-AMM Harberger auctions: the best strategy manager wins the vault; rent flows to depositors as real yield
* Senior/Junior tranche splits for different risk appetites
* PolicyCage: strategy bounds enforced by immutable on-chain logic after deployment

***

### Persona 3 — Protocol Builders

**Who:** Teams building DeFi protocols that want to integrate vault infrastructure, add agent-gated features, or monetize endpoints without building proprietary systems.

**Pain today:** ERC-4626 vaults are composable but lack agent-native gating. Building reputation or payment systems from scratch is expensive and non-standard. Monetizing API endpoints requires centralized API key management.

**What Gotts gives them:** Composable primitives — open standards with production-grade execution, custody, and reputation on top.

**Key value props:**

* ERC-4626 vaults — composable with the entire DeFi stack; no proprietary interfaces
* ERC-8004 identity integration — gate advanced features behind verified on-chain agent reputation from day one
* x402 revenue primitive — monetize any endpoint without API keys; charge per-request in USDC with \~200ms settlement
* Goblin Network integration — outsource permissionless job execution to a decentralized executor network

***

## 5. Product Suite

### 5.1 Gotts Vault

**Type:** Permissionless ERC-4626 vault factory

A vault deployed by an agent in a single transaction. Identity-gated via ERC-8004. Yield-bearing from day one. Composable across the entire DeFi stack.

See [prd/vault/01-overview.md](/docs/gotts-vaults/vault/01-overview.md) for full spec.

**Core features:**

| Feature                      | Description                                                                                         |
| ---------------------------- | --------------------------------------------------------------------------------------------------- |
| Auto-created Uniswap V4 pool | Every share token gets a V4 pool at deployment; NAV-priced and hook-governed from block one         |
| NAV-aware pricing            | On-chain hook prevents mispricing of vault shares                                                   |
| am-AMM Harberger auction     | Continuous strategy manager auction; winning manager pays rent directly to depositors as real yield |
| Collective CCA participation | Vault capital participates collectively in Uniswap CCA token launches                               |
| DeFi composability           | Morpho, Pendle, and Aave composability at deployment; no custom integration                         |
| Tranche splits               | Senior/Junior perpetual yield tranches within a single vault                                        |
| PolicyCage                   | Strategy bounded by immutable on-chain logic; no human override after deployment                    |

**Rehypothecation (Tier III+):** 60% of idle capital deployed to Morpho, Aave, and Seamless for verified agents. *(expansion track, post-v1)*

***

### 5.2 Gotts Safe

**Type:** Agent-native TEE custody layer

Keys are generated, stored, and used exclusively inside hardware enclaves. They never enter agent memory.

See [prd/mcp-server/01-overview.md](/docs/gotts-safe-mcp-server/mcp-server/01-overview.md) for full spec.

**Hardware attestation:** AWS Nitro, Intel TDX, AMD SEV-SNP

**Three-lane privilege isolation:**

| Lane           | Scope                                                    | Purpose                  |
| -------------- | -------------------------------------------------------- | ------------------------ |
| Hot lane       | Session keys scoped to specific vault operations         | Day-to-day execution     |
| Cold lane      | Owner authority for parameter changes and high-value ops | Governance-level changes |
| Fail-safe lane | Can only call `cancel()` — never initiate                | Emergency veto only      |

**Additional properties:**

* Time-delayed proxy as the primary security primitive
* Cancellation window survives full hardware compromise
* Escalation between lanes is architecturally impossible
* TEE attestation verified at runtime

***

### 5.3 The MCP Server

**Type:** Model Context Protocol server — 147 typed, validated, safety-checked tools

Comprehensive access to the full Uniswap protocol surface — across 11 chains, all major versions, with pre-flight simulation on every write operation. The server is the safety layer between an agent's intent and on-chain state.

**Tool categories:**

| Category                          | Tool count |
| --------------------------------- | ---------- |
| Data, Historical & Token Research | 18         |
| Portfolio, P\&L & Analytics       | 10         |
| Trading & Execution               | 9          |
| Liquidity Management              | 12         |
| Intelligence & Research           | 54         |
| Real-Time & Protocol Fees         | 12         |
| Self-Improvement & Memory         | 10         |
| Safety, Session Keys & Utility    | 22         |
| **Total**                         | **147**    |

The vault package (`packages/vault/`) adds 35 additional tools (24 core + 5 am-AMM + 6 proxy) for vault operations, strategy auctions, and time-delayed proxy management.

**Selected capabilities:**

* Trading: quote, approve, swap, cross-chain execution
* Liquidity: position management, JIT, TWAMM rebalancing
* Research: pool analytics, token data, opportunity scanner
* CCA: bid construction, intelligence scoring, participation
* Safety: pre-flight simulation, slippage guards, address validation
* Streaming: real-time price feeds, mempool monitoring

**Wallet support:** EOA, ERC-4337, Safe multisig, Privy — wallet-agnostic.

**Payment:** x402 outbound — pay-per-use external data access with no API key onboarding.

***

### 5.4 The Agent Network

**Type:** Library of 32 autonomous specialist agents + Goblin Network permissionless executor

See [prd/agents/01-overview.md](/docs/agents/agents/01-overview.md) for full spec.

**Specialist agents:**

| Agent            | Function                                                                |
| ---------------- | ----------------------------------------------------------------------- |
| Trade Executor   | Optimal routing across V2, V3, V4, and UniswapX                         |
| LP Strategist    | Range management, rebalancing triggers, fee harvesting                  |
| Pool Researcher  | Statistical analysis of pool behavior and risk                          |
| Vault Manager    | Deposit, rebalance, harvest, and distribute yield                       |
| Treasury Manager | Multi-asset allocation and revenue distribution                         |
| + 27 others      | Execution, research, strategy, development, infrastructure, and economy |

**Goblin Network:**

* Permissionless job execution framework — any address can join
* Gas refund model for executors
* Decentralized execution without a trusted operator
* Composition patterns support delegation hierarchies for multi-agent workflows

***

## 6. Security Architecture

**Summary:** 15 independent layers. 3 cryptographic. None optional.

Designed for a threat model where: TEE hardware can be broken for $50, prompt injection bypasses \~12% of defenses, and a single hallucinated address can drain a wallet.

See [prd/shared/safety-layers.md](/docs/prd-shared/safety-layers.md) for the canonical defense model.

| Layer | Name                            | Description                                                                                                                                                     | Type              |
| ----- | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
| L0    | ERC-8004 Identity Gate          | Universal agent identity gate for all vault participation. No secondary staking or proprietary systems.                                                         | —                 |
| L1    | TEE Key Isolation               | Keys generated and stored inside hardware enclaves. Never touch agent memory. Attested at runtime.                                                              | **Cryptographic** |
| L2    | CaMeL Injection Defense         | Capability-based security separating control flow from data flow. Untrusted data cannot affect program execution.                                               | —                 |
| L2.5  | MCP Integrity Verification      | Tool provenance signing. Independent state verification. MCP-Guard achieving 96% attack detection.                                                              | —                 |
| L3    | TEE Policy Engine               | Signing policies enforced at the enclave level. A compromised LLM cannot sign outside its defined envelope.                                                     | **Cryptographic** |
| L4    | Time-Delayed Execution          | The primary security primitive. Every major transaction announced on-chain before execution. Mandatory cancellation window survives all known hardware attacks. | —                 |
| L5    | Active Monitoring & Cancel      | Fail-safe cancel authority in a separate key and privilege lane. Veto any pending transaction during the delay window.                                          | —                 |
| L6    | Pre-Flight Simulation           | Every write operation simulated via `eth_call` before broadcast. Catches hallucinated addresses, incorrect amounts, and reverts.                                | —                 |
| L7    | On-Chain Guards                 | Immutable Solidity modifiers: `onlyAgent`, `hasReputation`, `withinTierLimit`. Cannot be bypassed after deployment.                                             | **Cryptographic** |
| L8    | Post-Trade Verification         | Independent state reconciliation after every execution. Discrepancies trigger automatic position review and alert escalation.                                   | —                 |
| L9    | Reputation Enforcement          | On-chain track record gates access to advanced features. Misbehavior has permanent, compounding consequences.                                                   | —                 |
| L10   | Adaptive Circuit Breakers       | Continuous dampening curves, never binary halts. Regime-aware alpha parameter adjusts to market stress in real time.                                            | —                 |
| L13   | V4 Hook Safety Checks           | Validate hook permission flags, verify access control, audit delta accounting. Prevents exploits like Cork Protocol ($11M, May 2025).                           | —                 |
| L14   | Reputation-Gated Tool Access    | ERC-8004 reputation tier determines which MCP tools an agent can invoke. Higher-risk tools require higher reputation.                                           | —                 |
| L15   | SIWE + OAuth 2.1 Authentication | Sign-In with Ethereum for identity proof; OAuth 2.1 for remote MCP server access.                                                                               | —                 |

**Audit status:** Pre-launch; undergoing formal verification and independent audit. Audit reports, formal verification proofs, and bug bounty details to be published before mainnet deployment. The time-delayed proxy at L4 ensures a cancellation window even if contracts are fully compromised.

***

## 7. Reputation System

On-chain, portable, non-transferable reputation on a 1,000-point scale. Trust accrues through 20 milestones across five categories and compounds over time. An agent that leaves Gotts leaves its entire track record behind.

### 7.1 Tiers

| Tier | Name       | Score  | Deposit Cap | Mgmt Fee Discount | Perf Fee Discount | Capabilities Unlocked                                                                                     |
| ---- | ---------- | ------ | ----------- | ----------------- | ----------------- | --------------------------------------------------------------------------------------------------------- |
| I    | Unverified | 0      | $1,000      | 0%                | 0%                | Protocol access. Basic vault participation.                                                               |
| II   | Basic      | 50+    | $10,000     | 5%                | 5%                | Standard vault operations.                                                                                |
| III  | Verified   | 200+   | $50,000     | 10%               | 10%               | Rehypothecation: 60% of idle capital. *(expansion track, post-v1)*                                        |
| IV   | Trusted    | 500+   | $100,000    | 20%               | 15%               | Uncollateralized credit delegation via Aave V3. Up to 5× recursive leverage. *(expansion track, post-v1)* |
| V    | Sovereign  | 1,000+ | $10M daily  | 30%               | 25%               | Governance participation. Permanent identity lock available.                                              |

Fee discounts are applied to the vault creator's configured rates. Example: a vault with 3% management fee charges a Verified depositor 2.7% (3% × 0.90).

Sovereign tier structurally requires ecosystem contribution — non-ecosystem milestones cap at 915 points.

### 7.2 Milestones

20 milestones across five categories. All auto-attested on-chain via the VaultReputationEngine and written to the ERC-8004 Reputation Registry.

| Category      | Milestones | Max Points | Examples                                                        |
| ------------- | ---------- | ---------- | --------------------------------------------------------------- |
| **Entry**     | 2          | 50         | First simulation, first deposit                                 |
| **Time**      | 4          | 205        | Weekly streak, 30d/90d/180d continuous hold                     |
| **Capital**   | 3          | 335        | $10K/30d TWAP, $50K/30d TWAP, $100K/30d TWAP                    |
| **Behavior**  | 5          | 250        | Profitable position, diversification, profitable exit           |
| **Ecosystem** | 6          | 435+       | Vault creation, governance vote, am-AMM bid, capital attraction |

Anti-gaming: self-deposits excluded, minimum activity thresholds, multi-creator requirements for diversification, caps on repeatable milestones.

### 7.3 Defection Detection

**Post-v1 (deferred per D-028):** The following mechanisms are adopted but will ship after v1 launch once sufficient behavioral data exists.

Four mechanisms prevent endgame exploitation by agents who build reputation cooperatively then pivot to extraction:

1. **Withdrawal acceleration detection** — second derivative of withdrawal rate over 7-day rolling window; flagged agents face 24-hour cooldown
2. **Behavioral regime classification** — cooperative, tit-for-tat, or defective (threshold: \~30% defection rate per Fontana et al.)
3. **Exponentially decay-weighted scoring** — recent behavior (last 30 days) weighted 3× relative to older milestones
4. **Exit bond** — Trusted and Sovereign agents post 0.5% of AUM; slashed if defection pattern detected (>90% confidence) within 30 days

### 7.4 Properties

* Non-transferable; identity transfers trigger 30-day linear reputation decay
* Track record is permanent and on-chain — attested to the ERC-8004 Reputation Registry
* Portable: any protocol that reads ERC-8004 can verify an agent's Gotts reputation
* Misbehavior has permanent, compounding consequences (L9 enforcement)
* Deterministic: same on-chain state always produces the same claim result

***

## 8. Protocol Economics

### 8.1 The Volume Flywheel

Gotts does not consume Uniswap volume. It manufactures it. Every vault deployed is a permanent, structural source of Uniswap flow — driven by vault lifecycle logic, not market sentiment.

```
Agent deploys Gotts Vault
        │
        ▼
V4 pool for share token auto-created (NAV-priced, hook-governed)
        │
        ▼
am-AMM Harberger auction begins
Winning manager pays continuous rent → flows to depositors as real yield
        │
        ▼
Vault capital enters Uniswap
Rebalances, CCA bids, JIT liquidity
All vault lifecycle events route through V4 hooks
        │
        ▼
Fee revenue + rent → vault depositors
Higher yield → more capital → more Uniswap volume
        │
        └──────────────────── (loop) ────────────────────┘
```

The flywheel is architectural, not incentivized. Gotts and Uniswap are symbiotic by design.

### 8.2 Fee Structure

Zero protocol fee at the base layer. Vault creators keep 100% of their configured fees (Morpho pattern).

**Vault fees (set by creator, subject to immutable caps):**

| Fee Type    | Cap             | Collection                                                                   |
| ----------- | --------------- | ---------------------------------------------------------------------------- |
| Management  | 500 bps (5%/yr) | Accrued continuously; collected via `report()` (Yearn V3 Accountant pattern) |
| Performance | 5,000 bps (50%) | On net-new profit above high-water mark only                                 |
| Entry       | Configurable    | Deducted at deposit time (default 0); reflected in `previewDeposit()`        |

**Creator reputation gates how high fees can be set:**

| Creator Tier        | Max Management | Max Performance |
| ------------------- | -------------- | --------------- |
| Unverified          | 1%             | 20%             |
| Basic               | 2%             | 30%             |
| Verified            | 3%             | 40%             |
| Trusted / Sovereign | 5%             | 50%             |

**Depositor reputation discounts** reduce the rates they pay (see Section 7.1 for the full table).

**am-AMM rent:** Continuous per-block payment from the winning strategy manager directly to depositors — real yield independent of vault trading performance.

### 8.3 Yield Sources

* Uniswap V4 fee revenue from NAV-aware pool
* am-AMM Harberger auction rent (continuous, to depositors)
* Rehypothecation yield from Morpho, Aave, and Seamless (Tier III+)
* Uncollateralized credit delegation returns (Tier IV+)

***

## 9. Uniswap Integration

Gotts is powered by Uniswap entirely. Every component of the Uniswap protocol surface is utilized.

| Integration        | Function                                                               |
| ------------------ | ---------------------------------------------------------------------- |
| V4 Hooks           | NAV-aware pool governance, vault lifecycle events, strategy management |
| NAV-Aware Pools    | Share token pricing reflects true net asset value at all times         |
| UniswapX           | Optimal trade routing; cross-chain execution                           |
| CCA Participation  | Collective vault participation in Uniswap Capital Commitment Auctions  |
| Dynamic Fee Engine | Fees adjust to market conditions in real time                          |
| am-AMM Auctions    | Harberger-tax strategy manager selection; rent to depositors           |
| TWAMM Rebalancing  | Time-weighted average market maker for large rebalances                |
| ERC-7683 Intents   | Cross-chain intent execution                                           |
| V2 · V3 · V4       | Full version coverage for routing and liquidity                        |
| 11 Chains          | Multi-chain coverage via the MCP server                                |

***

## 10. Key Standards

| Standard     | Description                                                                                                            | Status                       |
| ------------ | ---------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
| **ERC-4626** | Tokenized vault standard. Common interface enabling composability with every DeFi protocol that speaks the standard.   | Established                  |
| **ERC-8004** | On-chain identity, reputation, and validation registries for autonomous AI agents. Co-authored by MetaMask and Google. | Live on mainnet Jan 29, 2026 |
| **x402**     | HTTP-native machine-to-machine payment protocol settled on-chain. \~200ms settlement in USDC. No API keys.             | Live; 100M+ transactions     |
| **ERC-7683** | Cross-chain intent standard. Used for UniswapX cross-chain execution.                                                  | Established                  |

***

## 11. Developer Resources

All components are open source on GitHub.

| Resource   | Description                                                                                                                               |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Docs**   | Full API reference, integration guides, architecture deep-dives. Quickstart gets an agent connected to the MCP server in under 5 minutes. |
| **GitHub** | MCP server, vault contracts, agent library, and Goblin Network executor — all open source. Inspect, fork, contribute.                     |
| **SDK**    | Type-safe SDK for TypeScript. Deploy vaults, query agent reputation, construct x402 payment headers, stream real-time price feeds.        |

**Integration quickstart (via MCP server):** Any MCP-compatible agent framework (Claude, GPT-4o, Cursor agents, custom frameworks) can call Gotts tools directly. Every write operation is pre-flight simulated before broadcast. The agent never holds raw private keys.

***

## 12. Non-Goals

The following are explicitly outside the scope of the landing page and the protocol it describes:

* **No proprietary base-layer token.** The 0% base protocol fee model is architectural; there is no Gotts governance token driving fees at launch.
* **No human-custodied keys.** Agent keys never leave hardware enclaves. There is no human operator who can access or move funds.
* **No human-only vault interface.** Yearn- and Morpho-style human depositor UX is not a design target. Human depositors can interact via ERC-4626 standard interfaces, but the product is optimized for agents.
* **No proprietary data oracles.** External data is consumed via x402-gated endpoints; the protocol does not operate its own oracle network.
* **No cross-protocol governance.** Gotts does not attempt to govern or influence the behavior of Uniswap, Morpho, Aave, or other integrated protocols.

***

## 13. Open Questions

| Question                               | Priority | Notes                                                                             |
| -------------------------------------- | -------- | --------------------------------------------------------------------------------- |
| Mainnet launch date                    | High     | Audit completion is the primary dependency                                        |
| Audit scope and auditors               | High     | Formal verification + independent audit; details TBD                              |
| Bug bounty structure                   | High     | To be published before mainnet                                                    |
| Governance token / structure           | Medium   | Tier V includes governance participation; scope of governance TBD                 |
| SDK versioning and stability guarantee | Medium   | TypeScript SDK; release cadence TBD                                               |
| Goblin Network token economics         | Medium   | Gas refund model described; full tokenomics TBD                                   |
| PolicyCage parameter set               | Medium   | Which strategy parameters are immutably bounded and what the defaults are         |
| Multi-chain vault deployment           | Low      | MCP server supports 11 chains; vault factory chain coverage TBD                   |
| x402 inbound pricing                   | Low      | Rate schedule for external callers accessing Gotts MCP endpoints via x402         |
| Landing page copy vs. PRD              | Low      | This PRD is the product spec; final marketing copy may diverge from spec language |

***

## 14. Glossary

For the full canonical glossary, see [prd/shared/glossary.md](/docs/prd-shared/glossary.md). Key terms for this document:

| Term                  | Definition                                                                                                                                                                                      |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **am-AMM**            | Automated Market Maker with active management. In Gotts, a Harberger-tax auction where the winning strategy manager pays continuous rent to vault depositors.                                   |
| **CaMeL**             | Capability-based security framework that separates control flow from data flow, blocking prompt injection attacks by ensuring untrusted data cannot affect program execution.                   |
| **CCA**               | Capital Commitment Auction. Uniswap mechanism for token launches; Gotts vaults participate collectively.                                                                                        |
| **ERC-4626**          | Ethereum tokenized vault standard. Defines a common interface for yield-bearing vaults, enabling composability across DeFi.                                                                     |
| **ERC-7683**          | Cross-chain intent standard used by UniswapX for cross-chain execution.                                                                                                                         |
| **ERC-8004**          | Ethereum standard (live Jan 29, 2026) establishing on-chain identity, reputation, and validation registries for autonomous AI agents.                                                           |
| **Goblin Network**    | Permissionless decentralized executor network. Any address can join and execute vault lifecycle jobs (rebalancing, harvesting, etc.) in exchange for gas refunds.                               |
| **MCP**               | Model Context Protocol. An open standard for AI agents to interact with tools and services. The Gotts MCP Server exposes 147 tools over this protocol.                                          |
| **NAV**               | Net Asset Value. The true value of a vault's underlying assets. Gotts V4 pools are NAV-aware, meaning share token pricing reflects NAV at all times via on-chain hook.                          |
| **PolicyCage**        | Immutable on-chain logic that bounds the strategy parameters of a vault after deployment. No human or agent can override it.                                                                    |
| **TEE**               | Trusted Execution Environment. Secure hardware enclave (AWS Nitro, Intel TDX, AMD SEV-SNP) where agent keys are generated, stored, and used. Keys never leave the enclave.                      |
| **Reputation System** | On-chain, 1,000-point reputation system. Five tiers (Unverified to Sovereign) with 20 milestones across five categories that gate access to progressively more powerful financial capabilities. |
| **TWAMM**             | Time-Weighted Average Market Maker. Used for large vault rebalances to minimize price impact over time.                                                                                         |
| **x402**              | HTTP-native machine-to-machine payment protocol (May 2025). Enables per-request payments in USDC with \~200ms settlement and no API keys.                                                       |

***

*This document is a living draft. Sections marked with open questions should be updated as decisions are finalized.*