Relationship Other Modules

Relationship to TaaS

TaaS tokenizes yield products. VaaS operates the vaults behind them.

In the City Protocol capital layer, TaaS can issue the tokenized representation of a product, while VaaS manages the vault mechanics: deposits, share accounting, strategy allocation, NAV updates, monitoring, and redemption.

For example:

    A["Asset / Strategy"] --> B["TaaS Product Token"]
    B --> C["VaaS Vault"]
    C --> D["NAV + Verification"]
    D --> E["Earn Module Listing"]
    E --> F["User Deposit / Redemption"]

This separation allows City Protocol to support multiple product designs. Some products may be token-first. Others may be vault-first. The infrastructure can support both.

---

Relationship to the Earn Module

The Earn Module is the user-facing layer.

VaaS sits beneath it as the vault operating system. It provides the smart contracts, accounting, policy controls, monitoring, and redemption logic that allow City Protocol and partner apps to expose yield products in a simplified interface.

The Earn Module can display:

· vault type;

· supported asset;

· expected liquidity;

· risk controls;

· current NAV;

· capacity;

· verification status;

· redemption rules;

· historical performance;

· product status.

The user sees a simple yield product. VaaS handles the technical and operational complexity behind it.