> For the complete documentation index, see [llms.txt](https://docs.solera.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solera.market/protocol/integrations/smart-contract-risk.md). # Smart Contract Risk While the Solera Protocol has been audited, vulnerabilities may be missed by its developers, auditors, and core contributors in its smart contracts that facilitate user to platform interaction. PL's smart contracts are undergoing an audit with Trail of Bits. Please note, there is a possibility of a missed attack vector or bug which may be critical to the health of the protocol. In realizing this, bug bounties are available to the community, however it is possible that such risks exist in the protocol arising from smart contract errors such as: * Theft of protocol funds * Theft of user funds * Theft of unrealized yield * Attacks on protocol parameters through governance Bounties will be determined by the degree of the reported vulnerability with reported critical vulnerabilities being rewarded with the highest bounties. --- # 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.solera.market/protocol/integrations/smart-contract-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.