> For the complete documentation index, see [llms.txt](https://docs.ojolabs.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ojolabs.xyz/integration-guides/yield-risk-engine-v1-and-v2.md).
# Yield Risk Engine V1 & V2
Our yield risk engine is designed to put a static cap on how much a yield asset can appreciate over time. It's designed to reduce risk exposure to [inflation attacks](https://docs.openzeppelin.com/contracts/5.x/erc4626) where users are able to donate to an ERC-4626 vault and artificially increase the value of a vault token in order to borrow more against it. This type of attack happens [quite frequently](https://www.theblock.co/post/348785/analysis-of-700k-oracle-manipulation-exploit-highlights-vulnerabilities-in-defi-vaults). The yield risk engine was designed in collaboration with Gauntlet.
Disclaimer: No risk strategy can 100% protect against any type of attack. This risk engine should be considered a part of a broader risk strategy - we provide absolutely no warranty of effectiveness.
1. Navigate to the contract on HyperEVMScan
2. Check the current creationFee. This is the amount in the native token (in this case HYPE) that it will cost to spawn a new Yield Risk Engine.
3. Accept Terms - write to this tx to signify your acceptance of our disclaimer
4. Write a "Create" Tx. In this case the user is using one of our ERC-4626 vault price feeds, and paying 6 HYPE to create the yield risk engine. The cap they've chosen is 20%.
4. Done! You've spawned a new chainlink-interface-compatible yield risk engine which should cap the value of the asset to 20% over time.