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

# Protocol Overview

## **Neovestor Architecture Design**

*A Web3 Platform for Tokenized Institutional Assets*

***

### **Blockchain Layer**

**Foundation**: Built on **Solana** for high throughput, low fees, and scalability.

* **Core Components**:
  * **SPL Token Standard**: Fractional ownership of RWAs (e.g., real estate, private credit) represented as SPL tokens.
  * **Solana Programs**: On-chain logic for asset tokenization, governance, and compliance.
  * **State Compression**: Efficient storage of asset metadata (e.g., property deeds, loan terms).

***

### **Core Protocol Modules**

#### **a. Asset Tokenization Engine**

* **Function**: Converts RWAs into programmable, tradable tokens.
* **Components**:
  * **Asset Vaults**: Isolated smart contracts holding legal rights and collateral for tokenized assets.
  * **Dynamic Pricing Oracle**: Integrates decentralized oracles (e.g., Pyth Network) for real-time NAV updates.
  * **Compliance Wrappers**: ERC-3643-like token standards for automated KYC/AML checks and jurisdictional restrictions.

#### **b. Liquidity Management Layer**

* **Function**: Ensures seamless entry/exit for investors.
* **Components**:
  * **Reserve Pool**: 10–15% of AUM held in USDC for instant redemptions.
  * **Liquidity Router**: Directs redemptions to reserves or secondary markets (e.g., Raydium DEX).
  * **Staking Vaults**: Investors stake tokens to earn yield while awaiting asset maturity.

#### **c. Risk & Governance Engine**

* **Function**: Balances returns with risk mitigation.
* **Components**:
  * **AI Risk Model**: Analyzes credit risk, market volatility, and asset correlations.
  * **DAO Governance**: Token holders vote on asset onboarding, fee changes, and protocol upgrades.
  * **Circuit Breakers**: Automatically pause withdrawals during extreme market stress.

***

### **Institutional Integration Layer**

**Function**: Bridges traditional finance (TradFi) and DeFi.

* **Components**:
  * **Asset Origination Portal**: Institutional partners (e.g., private equity firms) submit RWAs for tokenization.
  * **Custody Gateway**: Fireblocks/Copper integration for secure custody of physical assets (e.g., real estate deeds).
  * **Regulatory Adapter**: Automates compliance with MiCA, SEC Reg D, and FATF Travel Rule.

***

### **User Interface Layer**

**Function**: Simplifies access for retail and institutional users.

* **Components**:
  * **Investor Dashboard**: Track portfolio performance, yields, and liquidity reserves.
  * **Compliance Hub**: Modular KYC/AML checks (e.g., Fractal ID integration).
  * **Secondary Marketplace**: Trade tokenized RWAs on integrated DEXs (e.g., Orca, Raydium).

***

### **Security & Compliance**

#### **a. Security Stack**

* **Smart Contract Audits**: Regular audits by firms like Halborn and Ottersec.
* **Decentralized Insurance**: Coverage for hacks or defaults via Nexus Mutual.
* **Multi-Sig Governance**: Critical operations (e.g., treasury withdrawals) require 3/5 signer approvals.

#### **b. Compliance Stack**

* **Jurisdictional Filtering**: Geoblocking for restricted regions.
* **Tax Reporting**: Automated generation of IRS Form 8949 and capital gains reports.
* **Permissioned Pools**: Accredited investor-only asset pools compliant with SEC regulations.

***

### **Cross-Chain & Interoperability**

**Function**: Expands accessibility beyond Solana.

* **Components**:
  * **Wormhole Integration**: Bridge tokenized RWAs to Ethereum, Polygon, etc.
  * **LayerZero Support**: Cross-chain messaging for unified liquidity and governance.

***

### **Data Flow Diagram**

*(Conceptual Overview)*

```
Investors → Deposit USDC → Tokenization Engine → Asset Vaults → RWA Deployment  
                          ↓  
                    Liquidity Layer → Reserves/DEXs  
                          ↓  
                    Risk Engine → Rebalancing/Adjustments  
                          ↓  
                    Governance → DAO Voting  
```

***

### **Key Innovations vs. Traditional Platforms**

| **Feature**       | **Traditional Finance**      | **Neovestor**                           |
| ----------------- | ---------------------------- | --------------------------------------- |
| **Accessibility** | High minimums ($1M+)         | $100 minimums                           |
| **Liquidity**     | Illiquid (6–12+ month exits) | Instant redemptions + secondary markets |
| **Transparency**  | Opaque reporting             | Real-time on-chain dashboards           |
| **Fees**          | 2–5% management fees         | 0.25–0.9%                               |

***

### **Future Roadmap**

* **Phase 1**: Launch tokenized real estate and private credit pools.
* **Phase 2**: Integrate AI-driven risk modeling and cross-chain liquidity.
* **Phase 3**: Partner with sovereign wealth funds for global RWA diversification.

***

*Disclaimer: This is a conceptual overview. Features may evolve based on regulatory and market conditions.*


---

# 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://neovestor.gitbook.io/neovestor/technology-stack/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.