Architecture Overview

A high-level guide to how Nava’s components fit together, aimed at developers integrating with the platform.

System Diagram

Transaction Lifecycle

1. User submits intent. Natural language, e.g., “Swap 2 ETH for USDC with max 0.5% slippage.”
2. Agent reasons. Selects the protocol and builds the transaction.
3. Agent submits proposal. Via the MCP Server or SDK, the intent and transaction proposal are encrypted and posted to NavaChain.
4. Escrow receives proposal. Funds are held and the proposal is routed to registered verification services.
5. Arbiter verifies. Deterministic triggers run first, then GoT reasoning if needed.
6. Verdict returned. Approve (with explanation) or reject (with failure reasons and remediation guidance).
7. Escrow executes or blocks. On approval, the transaction executes against the target protocol. On rejection, funds remain in escrow.