# The Target Market In any market, higher risk generally has higher yield and lower market caps. This is why yield must be adjusted for risk. We see this in DeFi today. Big blue-chip protocols like AAVE hold billions of dollars of ETH both for collateralized loans (e.g., borrowing USDC) and because it's a well-audited place to store ETH for non-zero yield. Smaller protocols with less audits and more complexity hold less ETH. But (using April 2022 numbers) the vast majority of ETH isn't in DeFi at all. There's >110M ETH. And blue chip protocols hold only 100,000s of them. ![Data as of April 2022. Numbers are much lower at time of writing (July 2022).](https://3375053316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCuoWrqUivgdEBM9CMKny%2Fuploads%2FnQXt29Li55FzIP0psVzM%2FTAMgif.gif?alt=media\&token=4491ca8a-ecbd-4c59-88f5-dfe891891412) This is not because blue-chips are untrustworthy- they're great and will likely grow a **lot** as regulations codify how institutions can self-custody assets and use these protocols. It's because they have risks above the intrinsic risk of holding volatile assets like ETH including: Oracles, Liquidations, Collateral, Smart Contract risks, and Contract Upgrade/Migration risks.\ \ True Freeze has no oracles, no liquidations, no lending/borrowing, no contract upgrades. By reducing the risks to only smart contract risks, it aims to appeal to 1,000,000s of ETH and serve as the benchmark rate for all of DeFi. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://deepfreezellc.gitbook.io/true-freeze/origins/the-target-market.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.