Risks

Strip is built around productive collateral, routed yield, liquidity pools, and incentive distribution. Each layer has its own risk. The core economic rules are fixed in code, but fixed rules do not remove risk; they make the system easier to understand. Users should know what the protocol can control, what it cannot, and where external assumptions enter.

​

Collateral risk

Supported yield-bearing assets carry their own risk before they ever enter the protocol. A supported asset may lose value, depeg, suffer smart contract issues, change its yield profile, or become less liquid. Principal Tokens represent deposited value inside Strip, but they do not remove the underlying risk of the deposited asset. If the collateral weakens, the Principal Token inherits that weakness. Strip routes yield; it does not guarantee the safety or performance of the underlying collateral.

​

Yield risk

Strip depends on realized yield. Yield can rise, fall, pause, or disappear. A vault with lower realized yield produces less output for compounding and buyback, and the STRIP demand generated by that vault declines with it. Projected APR is not the same as harvested yield; the system runs on realized output.

​

Liquidity risk

PT/STRIP liquidity can deepen or thin over time. Thin liquidity means worse execution, higher slippage, and more volatile pricing. Liquidity providers take exposure to both sides of the pool and may experience impermanent loss, price movement, or reduced fee income if volume is low. The 90/10 structure is designed to anchor liquidity around principal value, but it does not remove market risk, and the STRIP side of the pool is by design the thinner side, so STRIP price is more sensitive to flow than PT.

​

Smart contract risk

Strip relies on vault contracts, Principal Tokens, the routing layer, the BuybackBurner, PT/STRIP pools, the Uniswap v4 hook, the PoolWrapper, sWLP, stSTRIP, emissions contracts, and boost infrastructure. A bug in any component can create loss, incorrect accounting, failed routing, or broken incentives. Audits, testing, and transparency reduce this risk; they do not eliminate it.

​

Oracle and rate risk

Principal Token pricing depends on a live redemption-rate feed, and this dependency should be understood precisely. Vault operations, including withdrawals, require a fresh oracle price; if the feed goes stale or updates stop, deposits and withdrawals revert until the price is updated. The redemption guarantee is user-controlled, but its liveness depends on the oracle’s. Rate-protection bounds and high-water-mark pricing reduce the impact of temporary distortions, with two consequences worth knowing. If rate data moves outside the protection bounds, vault activity pauses until the anomaly is resolved. And because the high-water mark only rises, a genuine, sustained decline in the underlying asset’s value (such as a depeg) leaves the mark above the real rate, halting normal operations until a timelocked reset adjusts it. The protocol also has an emergency mode: if the vault is paused, withdrawals remain possible on a pro-rata basis. Deposits stop; exit does not.

​

Keeper and execution risk

Some actions require routine offchain execution: keeping the price feed fresh, publishing boost roots, triggering buybacks, redeeming yield, distributing emissions, and updating allocation points. If keepers are delayed or fail, rewards, buybacks, or boost data may lag until execution resumes, and a stalled price feed pauses vault activity entirely, as described above. Boost data outages are fail-safe: claims proceed at the 1x baseline, never zero. See Trust Assumptions.

​

Market and incentive risk

A Principal Token earns nothing on its own; the yield it would have produced is routed into the loop. A PT holder’s compensation is STRIP emissions, which means the position’s return depends on the value of STRIP, an asset with a market price that can fall as well as rise. If STRIP’s price declines, the effective return on staked PT declines with it, and the trade of routing yield for emissions becomes less attractive. This creates a reflexive dynamic that users should see clearly: weaker STRIP demand can reduce deposits, which reduces realized yield, which reduces buybacks. The protocol’s design counters this with real, external yield funding the burn and with emissions that decay on a fixed schedule, but design does not repeal market risk. Participants should evaluate the position at STRIP prices they consider realistic, not at the prices they hope for.

​

Genesis risk

During Genesis, emissions accrue while claims are disabled until a fixed onchain timestamp. Rewards earned in this window cannot be transferred, priced, or sold until claims open, and their eventual value is unknown while they accrue. The claims date is verifiable onchain, but the value that arrives on that date is set by the market, not the protocol. Depositors forgo realized underlying yield during this period in exchange for accrued STRIP whose price does not yet exist.