> For the complete documentation index, see [llms.txt](https://docs.tren.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tren.finance/protocol/asset-risk/security-risk.md). # Security Risk As Tren Finance works with varied asset types including LP tokens, money market deposits, and LRTs, a high level of importance is put on the technical security of each asset. While the technical risk analysis process does comprise of purely technical elements, there are many elements that require both qualitative and technical viewpoints. The tech team at Tren Finance will conduct smart contract reviews to gauge the security of the underlying code of an asset. As a part of this process, the team will review smart contract audits conducted by respected auditors in the space, on top of conducting internal reviews. To gauge the security of an asset, as shown in the [risk methodolgy table](/protocol/asset-risk.md#risk-methodology), the total number of on-chain holders, and transfers is also taken into account. These factors provide a viewpoint on how much the smart contract has been used, and by how many users. In general, the more that a smart contract has been used, the safer it is. The security review process also encompasses a large portion of the centralisation risk review process below. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.tren.finance/protocol/asset-risk/security-risk.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.