Skip to content

Risk Model

The Upside risk model is built on these assumptions:

1 Reserve backing is maintained

Deposited collateral remains in strategy and is available for exits

3 Oracle feeds are live

Deposit-time pricing requires accurate oracle data

4 On-chain mechanics are correct

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.

Yield goes to zero
Impact
  • 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
Recovery

Automatic when yield conditions improve. No action required for exit rights.

Upstream liquidity crunch

Strategy liquidity is temporarily constrained (e.g., high Aave utilization).

Impact
  • Withdrawal amounts may be temporarily constrained - Wrapper availability checks may reduce executable amount - Exits may require retries over time
Recovery

Liquidity normalizes as other Aave users repay. The capital still exists; it is temporarily lent out. This is a delay, not a loss.

Smart-contract exploit in strategy stack

Strategy capital is lost due to upstream protocol vulnerability.

Impact
Recovery

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.

Reserve shortfall

Strategy reserve collateral is below expected target (loss event or strategy accounting issue).

Recovery

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.

Mass redemption

A large share of investors attempt exits via redeem in a short time window.

Impact
  • 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
Recovery

Everyone gets the same rate. Outflow limits spread exits over time, preventing first-movers from extracting at others' expense.

Oracle outage

Oracle feed is stale, zero, or invalid.

Impact
  • 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
Recovery

An oracle outage blocks deposits but does not block exits. Exit conversion uses stored position parameters, not a live price feed.

Project abandonment

Project team becomes inactive.

Impact
Recovery

Exit rights remain on-chain and user-callable. Yield collection is permissionless.

Rounding and dust

Integer division leaves residual dust.

Impact
  • Rounding always favors the protocol (reserve), never the user - Small residual balances can remain until final cleanup/sweep operations
Recovery

Rounding always favors the protocol (reserve), never the user. The amounts are negligible (wei-level).

Each raise operates in full isolation: separate reserve accounting, position state, yield routing, and admin controls. See Guarantees for details.

RiskProtected?Mechanism
Project token goes to zeroYesPUT right returns collateral
Project team disappearsYesExits are permissionless on-chain
Upstream strategy exploitNoExits settle against remaining collateral
Temporary liquidity crunchDelayedRetries succeed as liquidity normalizes
Oracle failurePartialBlocks deposits, exits still work
Volatile collateral loses USD valueNoRedemption is in deposit asset, not USD