Risk Model
Design Assumptions
Section titled “Design Assumptions”The Upside risk model is built on these assumptions:
Deposited collateral remains in strategy and is available for exits
Yield strategy (e.g., Aave V3) honors deposits and withdrawals
Deposit-time pricing requires accurate oracle data
Smart contract logic executes as designed
When these assumptions hold, principal protection works as intended. The risk model addresses what happens when they don’t.
Risk Scenarios
Section titled “Risk Scenarios”Click a scenario to jump to full details below.
Principal still works, buyback (if enabled) stops
Auto-recovery when yield returnsWithdrawals temporarily constrained
Normalizes as liquidity returnsStrategy value drops, loss isolated to raise
Proportional settlement of remainingExits settle against available collateral
Circuit breaker slows panic velocityCircuit breaker throttles, exits stretch over time
Same rate for all, no first-mover advantageNew deposits blocked
Exits still work (stored parameters)Admin operations halt
Exit rights remain on-chain- Principal mechanics still function, investors can still redeem - Configured buyback (if any) and ecosystem budget inflow stops - No guaranteed minimum yield - Platform revenue stops for that raise
Automatic when yield conditions improve. No action required for exit rights.
Strategy liquidity is temporarily constrained (e.g., high Aave utilization).
- Withdrawal amounts may be temporarily constrained - Wrapper availability checks may reduce executable amount - Exits may require retries over time
Liquidity normalizes as other Aave users repay. The capital still exists; it is temporarily lent out. This is a delay, not a loss.
Strategy capital is lost due to upstream protocol vulnerability.
- Reported strategy value drops - Exit paths continue, but payouts settle against actual remaining collateral - Loss is isolated to the affected raise context - The circuit breaker may activate to throttle outflows during the initial discovery window, spreading exits over time instead of rewarding the fastest responders
Exits settle via proportional settlement against remaining collateral. Every investor receives the same proportional rate. Principal protection covers project-token downside, not reserve depletion from upstream strategy compromise.
Strategy reserve collateral is below expected target (loss event or strategy accounting issue).
- Exits settle against available collateral and conversion constraints - Circuit breaker outflow controls slow panic/exploit velocity
Each exit settles against available collateral. In normal operation this equals the original deposit; in a shortfall, it equals the proportional share of what remains.
A large share of investors attempt exits via redeem in a short time window.
- Each exit uses the same conversion mechanics for that position - Wrapper and strategy liquidity governs immediate execution capacity - Circuit breaker can throttle outflow velocity - Processing may stretch across multiple blocks if upstream liquidity is constrained
Everyone gets the same rate. Outflow limits spread exits over time, preventing first-movers from extracting at others' expense.
Oracle feed is stale, zero, or invalid.
- New deposits are blocked/reverted - Existing position exits remain available through conversion math and reserve state - A prolonged outage pauses all new deposits, which can delay a raise from reaching its cap
An oracle outage blocks deposits but does not block exits. Exit conversion uses stored position parameters, not a live price feed.
Project team becomes inactive.
- Exit rights remain on-chain and user-callable - Strategy may continue accruing yield passively - Yield collection is permissionless; anyone can trigger the claim function - Administrative operations (e.g. configured buyback execution) halt if no operator acts
Exit rights remain on-chain and user-callable. Yield collection is permissionless.
Rounding and Dust
Section titled “Rounding and Dust”Integer division leaves residual dust.
- Rounding always favors the protocol (reserve), never the user - Small residual balances can remain until final cleanup/sweep operations
Rounding always favors the protocol (reserve), never the user. The amounts are negligible (wei-level).
Risk Isolation
Section titled “Risk Isolation”Each raise operates in full isolation: separate reserve accounting, position state, yield routing, and admin controls. See Guarantees for details.
What Is and Isn’t Protected
Section titled “What Is and Isn’t Protected”| Risk | Protected? | Mechanism |
|---|---|---|
| Project token goes to zero | Yes | PUT right returns collateral |
| Project team disappears | Yes | Exits are permissionless on-chain |
| Upstream strategy exploit | No | Exits settle against remaining collateral |
| Temporary liquidity crunch | Delayed | Retries succeed as liquidity normalizes |
| Oracle failure | Partial | Blocks deposits, exits still work |
| Volatile collateral loses USD value | No | Redemption is in deposit asset, not USD |