Skip to main content
Safe Harvest Risks

An overview of the key implementation risks of Covered Call Spread Tokens.

Updated over a week ago

There are a few risks associated with tokenized strategies - beyond the risk of the strategy itself (detailed here). It is important users are aware of these risks before depositing to or acquiring a tokenized strategy. Note that this is not necessarily an exhaustive list.

Execution Risks

Delayed Settlement

  • If options expire in-the-money, collateral will need to be swapped for USDC on settlement. Available spot liquidity on the exchange and the amount of collateral to be liquidated could factor in to longer settlement times, in order to ensure quality of execution.

Oracle risks

  • Per the Derive docs, for each market, there is a set of oracle inputs used for marking assets when computing margin and liquidations. This data is posted onchain for transparency and available via the public REST API. This data is provided by Block Scholes.

  • It’s possible that feeds for certain assets (particularly less liquid ones) may have marks that deviate from the true fair value, which can result in suboptimal execution for the strategy vault.

Underlying Collateral Risk

Holding the underlying collateral carries its own set of risks. These may include, but are not limited to, smart contract bugs, Ethereum bugs, restaking penalties, price fluctuations, and key management problems.

For a detailed overview of the risks specific to each type of collateral, please refer to the relevant documentation:

Bridge Risk

  • Transferring assets from one network to another carries risks associated with the underlying bridge provider. In this product, we use Socket as the bridge provider. Please review their documentation for more details.

Smart Contract Risk

  • Interacting with any smart contract carries the risk of losing access to your funds. The immutable nature of smart contacts makes it difficult and potentially impossible to recover them.

Did this answer your question?