> For the complete documentation index, see [llms.txt](https://vitaprotocol.gitbook.io/vita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitaprotocol.gitbook.io/vita/vita-protocol/whitepaper/chapter-12-protocol-architecture-and-execution-engines.md).
# Chapter 12 · Protocol Architecture and Execution Engines
The steel frame beneath the Ring of Life
### 12.1 Genesis Deployment and Omnichain Genes
The VITA Genesis Edition deploys first on BNB Chain, carrying genesis launch, crystal activation, the Tower Network and the DAO transition; it also integrates with several Bitcoin Layer 2 infrastructure providers and decentralized liquidity aggregators to build the base settlement interfaces for the BTC Yield Engine. BNB Chain is the delivery room of genesis and Bitcoin the destination of value, and the protocol's territory will extend outward as governance and technical verification allow. The architecture has been Omnichain Ready from the start, and any future network must observe three iron rules: no replication of the genesis issuance, no arbitrary expansion of supply, and no direct commingling of unverified cross-chain data.
### 12.2 Five Layers of the Protocol
| Layer | Responsibility |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Application layer | Wallets, DApps, AI agents, payments, RWA, DePIN and community tools |
| Execution layer | Core logic: genesis launch, crystal activation, liquidity, burning and governance |
| Identity and contribution layer | Wallet identity, crystal credentials, network relationships, contribution snapshots and reputation records |
| Omnichain messaging layer | Cross-chain messages, state proofs, asset adaptation, replay protection and fault isolation |
| Settlement layer | VITA, BNB, BTC-anchored assets and future settlement assets approved by governance |
### 12.3 The VITA Hooks Engine: A Pluggable Execution Core
The VITA Hooks Engine is built on the programmable extensibility of Uniswap v4 Hooks, executing the protocol's preset logic at key lifecycle points: pool initialization, liquidity changes, swaps, fee handling and settlement. The protocol preserves Uniswap v4's underlying AMM pricing in full and coordinates LP management, time-weighted market making, contribution synchronization and state settlement through modular hooks — LP Hook, TWAMM Hook, Fee Hook, Settlement Hook, Governance Hook and a reserved Oracle / Risk Hook, each in its own role and isolated from the rest. Every production hook must pass five gates: whitelist governance, security audit, permission disclosure, timelock and emergency pause. A hook's authority is bounded by code — it may not bypass core protocol rules, may not alter the token supply, and may not touch user assets.
### 12.4 The TWAMM Hook: Letting Time Smooth the Waves
The Time-Weighted Automated Market Maker splits large trades and market-making strategies across continuous time windows for gradual execution, smoothing price impact, reducing slippage and improving pool depth and capital efficiency. Its remit is restrained and clear: market execution along the dimension of time only, isolated from governance and from pricing logic.
### 12.5 The AI Strategy Engine: A Strategy Layer That Thinks
Reading on-chain market state, liquidity depth, volume and volatility, the AI Strategy Engine proposes dynamic strategies for market-making parameters and time windows, which the Hooks Engine executes within authorized bounds — including optimizing the routing efficiency of BTC reserve settlement so that the path from on-chain fees to the Bitcoin reserve stays efficient and unobstructed. Four locks bind its authority strictly: it cannot custody assets, cannot transfer assets, stays isolated from price formation, and remains at all times subject to governance and emergency pause. The full execution path is public and traceable:*AI Strategy Engine → VITA Hooks Engine → TWAMM Hook → Uniswap v4 Pool → Settlement Engine*。
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://vitaprotocol.gitbook.io/vita/vita-protocol/whitepaper/chapter-12-protocol-architecture-and-execution-engines.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.