# Audits & Risks Teddy Cash has been audited by [HashEx](https://blog.hashex.org/teddy-cash-smart-contract-audit-report-ac4e151c6ac7). Teddy Cash is a fork of the [Liquity protocol](https://docs.liquity.org) and inherits all risks of that protocol. We have made [minimal changes](https://github.com/teddy-cash/dev/compare/main..fdb5093) to Liquity's original set of smart contracts. We recommend you review the following audits done for Liquity in addition to the one done by HashEx. * [Trail of Bits](https://github.com/trailofbits/publications/blob/master/reviews/Liquity.pdf) January 2021 * [Audit by Coinspect](https://www.coinspect.com/liquity-audit/) March 2021 Here are the most notable risks that you should be aware of when using Teddy Cash. #### No Backup Oracle Liquity uses the Chainlink oracle as primary price feed, and a Tellor oracle as fallback. Since the Tellor oracle was not available on Avalanche during deployment, Teddy Cash configured instead an empty contract as oracle, which is equivalent to disabling the backup oracle. Alternative solutions to retroactively add Tellor support once it becomes available, would make the protocol no longer immutable and this introduces additional risks. The removal of the backup oracle has been proven to work in other liquity forks ([Fluity](https://fluity.finance/), [PolyQuity](https://polyquity.org/), etc). #### Potential differences in a new EVM Any protocol that is forked to a new EVM can contain hard to detect and mission critical bugs that may lead to catastrophic losses. Proceed with extreme caution. --- # 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://docs.teddy.cash/audits-and-risks.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.