> For the complete documentation index, see [llms.txt](https://sovavault.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://sovavault.gitbook.io/docs/technical-resources/protocol-overview.md).

# Protocol Overview

### Sova Enables:

* Tokenization of RWAs with flexible strategy implementations
* Share-based accounting for RWA representation using ERC4626 vaults
* NAV (Net Asset Value) oracle integration via Reporter contracts
* Built-in KYC/AML compliance features with extensible hook system
* Two-phase gated deposit flow for compliance verification
* Advanced withdrawal management for illiquid assets
* Role-based access control for protocol administration

### Deployment Information:

* **Network:** Base
* **Version:** V1
* **Deployment Date:** 2025-07-07
* **Git Tag:** `deploy-20250707`
* **Audit:** [Omniscia Audit Report](https://omniscia.io/reports/sova-network-fountfi-protocol-684adfa36579f5001821a219/)
* **Deployer Address:** `0x76F2DAD4741CB0f4C8C56361d8cF5E05Bc01Bf28`
* **GitHub:** [Link](https://github.com/SovaNetwork/fountfi)

| Contract                | Address                                    |
| ----------------------- | ------------------------------------------ |
| Role Manager            | 0x6c826Ea5664d64F570ed50d82107593c33af8A47 |
| Registry                | 0x50f4EF3B29362abA1B9EA88E600B016d99c44C3E |
| Conduit                 | 0x66Df6ECcC14D8bd12249b587835D92125e9DBe71 |
| KYC Rules Hook          | 0xD1b225374c64C87Cf0909910AF34e54021EFaEaA |
| Price Oracle Reporter   | 0xB8bBabD3134C18cA705dA904A73A86CB1001955a |
| Strategy Implementation | 0x66CA4C7973A73fd243563D068452F8D1C2D1E123 |
| Mock USD Token          | 0x295F16c13feA14c55289d16D83b2ABAAD3B820f3 |

### Protocol Architecture

<figure><img src="/files/eDi2SVi0FKQ3IY8SwJty" alt=""><figcaption></figcaption></figure>

### Key Terms and Concepts

* **tRWA (Tokenized Real World Asset)**: An ERC4626-compatible token that represents ownership shares in an underlying real-world asset strategy.
* **Strategy**: A contract that manages underlying assets and deploys its own tRWA token. Strategies implement different investment approaches for the underlying assets.
* **Registry**: The central hub of the protocol that manages all component registrations and deployments, ensuring only authorized components can interact.
* **Conduit**: A security contract that manages all asset transfers between users and the protocol, providing a layer of protection for token movements.
* **Hook**: A pluggable validation component that enforces rules before token operations (deposits, withdrawals, transfers). Hooks enable extensible compliance mechanisms.
* **Rules Engine**: A special type of hook that coordinates multiple sub-hooks, allowing complex validation logic to be composed from simpler rules.
* **Reporter**: An oracle contract that provides asset valuations to the protocol, enabling accurate share pricing.
* **GatedMint**: A two-phase deposit mechanism where assets are held in escrow pending explicit approval, allowing for issuer control over flow of funds and timing of acceptance.
* **Deposit Escrow**: A contract that temporarily holds assets during the two-phase deposit process until they are either accepted or refunded.
* **Withdrawal Queue**: A mechanism for managing withdrawals from illiquid assets, allowing for orderly processing of redemption requests.


---

# 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://sovavault.gitbook.io/docs/technical-resources/protocol-overview.md?ask=<question>&goal=<endgoal>
```

`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.