> 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/gotts-vaults/vault/13-performance.md).

# Performance

> **Part of**: [Vault PRD](/docs/gotts-vaults/vault.md) | **Last Updated**: 2026-02-13

***

## Performance Requirements (Core-First)

Performance targets are split into launch-critical (core-v1) and deferred (post-v1 expansion).

***

## Core-v1 MCP Latency Targets

| Operation                                              | Target (p95) | Max Acceptable (p99) |
| ------------------------------------------------------ | ------------ | -------------------- |
| `list_vaults`                                          | < 250 ms     | < 1 s                |
| `get_vault_config`                                     | < 200 ms     | < 800 ms             |
| `vault_get_state`                                      | < 300 ms     | < 1 s                |
| `vault_get_positions`                                  | < 300 ms     | < 1 s                |
| `vault_get_strategy`                                   | < 500 ms     | < 2 s                |
| `vault_get_performance`                                | < 500 ms     | < 2 s                |
| `vault_get_risk_metrics`                               | < 400 ms     | < 1.5 s              |
| `vault_get_agent_shares`                               | < 300 ms     | < 1 s                |
| `vault_get_milestones`                                 | < 500 ms     | < 2 s                |
| `vault_simulate_deposit`                               | < 1 s        | < 3 s                |
| `vault_deposit` (pre-confirmation server latency)      | < 2 s        | < 5 s                |
| `vault_withdraw` (pre-confirmation server latency)     | < 2 s        | < 5 s                |
| `vault_rebalance` (pre-confirmation server latency)    | < 3 s        | < 8 s                |
| `vault_collect_fees` (pre-confirmation server latency) | < 2 s        | < 5 s                |
| `vault_register_agent`                                 | < 2 s        | < 5 s                |
| `vault_enroll_reputation`                              | < 2 s        | < 5 s                |
| `vault_claim_milestone`                                | < 2 s        | < 5 s                |
| `create_vault`                                         | < 5 s        | < 12 s               |
| `get_vault_rankings`                                   | < 1 s        | < 3 s                |

***

## Core-v1 Contract Gas Targets

| Operation                         | Target Gas | Maximum Gas |
| --------------------------------- | ---------- | ----------- |
| `createVault` (factory core path) | < 2,000k   | < 3,000k    |
| `deposit`                         | < 220k     | < 320k      |
| `withdraw`                        | < 220k     | < 320k      |
| `rebalance`                       | < 550k     | < 850k      |
| `registerAgent`                   | < 120k     | < 180k      |
| `enrollReputation`                | < 140k     | < 220k      |
| `claimMilestone`                  | < 180k     | < 280k      |

***

## Proxy Module Performance (Optional, Safety-Critical)

| Operation                                   | Target Gas | Maximum Gas |
| ------------------------------------------- | ---------- | ----------- |
| `announce()`                                | < 90k      | < 130k      |
| `execute()` (excluding downstream call gas) | < 60k      | < 90k       |
| `cancel()`                                  | < 35k      | < 55k       |

Operational targets:

* Monitor detection latency for new announcements: <= 60 seconds
* Cancel action dispatch latency (detected suspicious tx): <= 30 seconds

***

## Deferred Performance Targets (Post-v1)

These do not block core launch:

* CCA tool latencies and adapter gas targets (`submit_cca_bid`, `exit_cca_bid`, `claim_cca_tokens`, `deploy_liquidity`)
* Growth tool latencies (`vault_quick_deposit`, referral/recruitment tools)
* Hook-specific callback gas tuning beyond core rollout