> For the complete documentation index, see [llms.txt](https://city-protocol.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://city-protocol.gitbook.io/docs/introduction/value-proposition/vault-creators-and-curators.md).

# Vault Creators & Curators

Vault creators and curators need infrastructure that can turn a strategy mandate into a secure, monitorable vault. A simple deposit contract is not enough for institutional-grade yield. The vault must control who can deposit, where capital can move, how NAV is updated, what venues are approved, how fees accrue, when redemptions happen, and what conditions trigger a pause.

**City Protocol helps vault creators and curators:**

* deploy standardized vault contracts;
* configure accepted assets, supported networks, minimum deposits, capacity, fees, and redemption periods;
* define strategy whitelists, approved venues, allocation limits, drawdown controls, and collateralization thresholds;
* separate vault governance from strategy execution through creator-bound execution;
* use role-based permissions for curators, strategy managers, NAV signers, guardians, and operators;
* require oracle quorum, signer approval, and deviation checks for NAV updates;
* expose deposits, withdrawals, NAV reports, fees, strategy debt, settlement records, and permission changes through indexed data;
* apply emergency pauses or circuit breakers when product state breaches defined limits.

The benefit is a vault environment that is easier to launch, easier to govern, and easier to trust. Curators can focus on product design and strategy selection while City Protocol standardizes the control, accounting, monitoring, and redemption infrastructure around them.