Enzyme Protocol Explained: On-Chain Vaults and Manager Risk
A transparent vault can show holdings and transactions; it does not guarantee a competent or honest strategy.
Policies constrain managers only to the extent configured and correctly implemented.
Key takeaways
Depositors receive vault shares. Value follows the portfolio after fees.
Managers trade through adapters. Supported integrations expand opportunity and attack surface.
Policies encode boundaries. Asset lists, investor rules and position limits must be inspected.
Valuation depends on price feeds. Illiquid assets can make NAV misleading.
The vault lifecycle
A manager creates a vault, selects denomination asset, fees, policies and integrations. Investors deposit under those terms; the vault trades and later processes share redemptions.
Manager due diligence
Review identity, mandate, track record, fee structure, leverage, concentration, upgrade permissions and whether positions can be exited during stress.
For organizations
Separate operational keys, use multisig controls, document valuation and test emergency redemption before accepting external capital.
Decision checklist
Verify current official documentation, contracts or legal entities, administrator permissions, fees, liquidity and the full exit path. Test the smallest practical transaction and record what happens when an interface, oracle, bridge, operator or counterparty fails.
Keep a dated baseline of addresses, reserves or collateral, governance roles and normal withdrawal results. Recheck it after upgrades or incidents. An audit, license application, partnership or TVL number answers only one part of the risk.
Before increasing exposure, define an observable stop condition: a collateral deviation, missed withdrawal, governance change, loss of market depth or unsupported software version. Decide the response in advance and retain enough native gas and independent wallet access to execute it without relying on customer support.