> ## Documentation Index > Fetch the complete documentation index at: https://docs.stripyield.com/llms.txt > Use this file to discover all available pages before exploring further. # 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 control, and where external assumptions enter the system. ## Collateral Risk Strip supports yield-bearing assets. Those assets have their own risk before they ever enter the protocol. A supported asset may lose value, depeg, suffer from smart contract issues, change its yield profile, or become less liquid in the market. Principal Tokens represent deposited value inside Strip, but they do not remove the underlying risk of the asset deposited. 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. If yield declines, 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 pools create liquidity between Principal Tokens and STRIP. Liquidity can deepen or thin over time. Thin liquidity can create worse execution, higher slippage, and more volatile pricing. PT/STRIP 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 pool structure is designed to anchor liquidity around principal value, but it does not remove market risk. ## Smart Contract Risk Strip relies on vault contracts, Principal Tokens, the routing layer, the BuybackBurner, PT/STRIP pools, the Uniswap v4 hook, PoolWrapper, sWLP, stSTRIP, emissions contracts, and boost infrastructure. A bug in any of these components can create loss, incorrect accounting, failed routing, broken incentives, or unexpected behavior. Audits, testing, and transparency reduce this risk, but they do not eliminate it. ## Oracle and Rate Risk Principal Token pricing depends on redemption mechanics, vault accounting, and rate data. The system uses rate-protection bounds and high-water-mark pricing to reduce the impact of temporary distortions, but pricing still depends on accurate inputs. If an oracle, rate source, or accounting feed behaves incorrectly, vault activity may pause or pricing may be affected until the issue is resolved. ## Keeper and Execution Risk Some actions require routine execution. Keepers publish boost data, trigger buybacks, burn accumulated STRIP, redeem yield into the BuybackBurner, run emissions distribution, and update allocation points. Keeper actions are bounded and visible, but delays or failures can still affect user experience. A missed execution may delay buybacks, emissions updates, boost publication, or fee routing until the relevant action is performed. ## Incentive Risk STRIP emissions allocate rewards to users who support the system. Allocation is based on productivity, liquidity, and sustained alignment. These incentives can attract capital, but they can also change behavior. Users may enter for emissions and leave when rewards decline. Vault APRs may shift. Liquidity may move between pools. Boost resets can change reward distribution. The system is designed to favor sustained alignment, but it cannot force participants to stay. ## Market Risk STRIP is a market-traded asset. Its price can move independently of protocol output, emissions, buybacks, liquidity, or broader market conditions. Routed yield creates recurring STRIP demand, but it does not guarantee price appreciation. Buyback and burn reduces supply from circulation, but market price still depends on liquidity, demand, sentiment, emissions, and selling pressure. ## Operational Risk Strip has privileged roles for operation, safety, and routine execution. These roles are limited by scope, timelocks, rate limits, and public event logs, but they still exist. Users should understand which parts of the system are fixed, which parts require operational execution, and which actions can be performed by the multisig, keepers, or approved signers. ## Protocol Risk Strip is a new mechanism. The loop is clear: productive collateral creates yield, yield routes into STRIP demand, part of the output compounds, and incentives allocate ownership to aligned participants. The long-term behavior of that loop depends on collateral quality, realized yield, market depth, emissions, user behavior, and broader DeFi conditions. Users should size positions with the understanding that Strip contains smart contract risk, collateral risk, liquidity risk, market risk, and execution risk. The protocol makes those flows visible, but visibility is not the same as certainty.