Risk
Key risks and assumptions
The main protocol, operational, and UX risks that users and contributors should understand.
Main Risks
- queued burns may not settle immediately
- batch pricing can move outside user tolerance
- upgradeable contracts introduce admin trust
- subgraph lag can temporarily affect historical UI clarity
- single-chain assumptions mean unsupported-network handling is strict
Main Assumptions
- keepers execute queue and strategy operations
- strategy NAV reporting is correct enough for pricing inputs
- contract address snapshots in frontend config stay current
- operators update docs when deployments move
Last updated on