Security and Risk Controls
The Issuance & Operation Layer inherits a robust security operating model and extends it to product-level issuance and operations. While this infrastructure provides rigorous safeguards, it does not make the underlying assets risk-free. Products still carry market risk, liquidity risk, strategy risk, oracle risk, smart contract risk, counterparty risk, legal risk, and operational risk.
To mitigate these risks, Venzo enforces strict product-level security controls:
Component Whitelisting
Restricts products exclusively to approved TaaS products, verified VaaS vaults, and whitelisted external components.
Product Mandate Enforcement
Prevents managers from changing assets, weights, venues, leverage, liquidity terms, or fees outside the approved rule set.
Issuance Controls
Links product tokens, receipts, shares, or position records strictly to approved registry entries, eligibility logic, NAV sources, and redemption terms.
NAV Signer Quorum
Requires multiple authorized valuation signers before a product-level NAV becomes authoritative.
Deviation and Freshness Checks
Automatically flags abnormal NAV moves, stale component data, missing reports, or inconsistent component pricing.
Status Propagation
If an underlying component is paused, impaired, expired, or deemed ineligible, the overarching product status updates automatically.
Role Separation
Strictly separates the roles of issuer, manager, NAV signer, whitelist manager, verifier, guardian, and governance participants.
Fee Visibility
Transparently displays management fees, performance fees, entry/exit fees, and fee layering before any subscription occurs.
Emergency Pause
Allows deposits, redemptions, rebalancing, issuance, or transfers to be paused immediately during abnormal market, oracle, strategy, or security events.
Disclosure Versioning
Links each product to its current methodology, risk disclosure, component list, fee schedule, and material updates.
Look-Through Reporting
Allows integrators and participants to inspect product-level exposure and the real-time status of underlying components.
Last updated
Was this helpful?