FOREVER MARKETS
Risks & capped beta
The important boundaries users and liquidity providers should understand before using Forever.
Material risks
| Risk | What it means |
|---|---|
| Smart-contract risk | A bug could lose or lock collateral |
| Oracle risk | Incorrect or unavailable stock data can stop trading or misprice execution |
| Liquidity risk | Orders may fill partially or with price impact; LP withdrawals may wait |
| Leverage risk | Leveraged positions can be liquidated rapidly |
| LP risk | Trader profits and bad debt can reduce vault share value |
| Admin-key risk | The current wallet can upgrade contracts and change risk configuration |
| Infrastructure risk | Reporter, RPC, relayer and keeper availability affect product operation |
Current protections
Market, position, gross OI and net OI caps
Endpoint reserve solvency checks after every fill
Dynamic leverage above 15×
Conservative oracle bounds and staleness checks
Restricted liquidation keepers
Shared-vault sleeve caps and 10% idle buffer
First-loss capital and 15% sleeve drawdown breaker
Close-only and Frozen emergency modes
Internal fuzzing, invariants and exact-live migration tests
Not yet complete
Independent third-party security audit
Multisig and delayed upgrade execution
Activated Chainlink Data Streams production feeds
Dedicated production RPC with independent fallback
Permissionless market creation
Uncapped TVL or open interest
Capped beta reduces blast radius; it does not make the protocol risk-free.