> For the complete documentation index, see [llms.txt](https://wp.lovely.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.lovely.finance/security-considerations.md). # Security Considerations The Web3 landscape is endangered by various news of security threats. Blackhats have drained quite several blockchains, protocols, exchanges, wallets, and crypto projects. There are a plethora of cases. During market research, we got feedback that users wondered whether threat actors could take away their hard-earned funds. Lovely Finance is a company that is in touch with the people. As a result, we deem it fit to address this dilemma so our users can have a heightened trust in our ecosystem. In lieu of this, Certik—one of the most brilliant auditing firms in Web3—has audited our protocol, smart contracts, and dApps. In addition, we have also carried out penetration testing on our applications, which gave us insights into what we have to improve. With this due diligence on our part, it is safe to say all our products are safe and secure for anyone to use them confidently. --- # 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://wp.lovely.finance/security-considerations.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.