# Security The security of the LADT protocol is of paramount importance to us. Our development team has worked diligently alongside third-party auditors and consultants to invest significant time and effort in ensuring that the protocol we have chosen is not only safe but also highly dependable. This collaborative effort aims to minimize vulnerabilities and enhance the overall robustness of the system. To maintain transparency and accountability, we have made all contract code and balances accessible to the public. This transparency enables anyone with an interest in the protocol to verify its integrity and security. Additionally, we actively encourage security professionals to participate in our “bug bounty program”, providing them with incentives to identify and report any previously undiscovered vulnerabilities. This proactive approach helps us in continuously improving the protocol’s security. It’s worth noting that we believe the true test of a smart contract’s security is determined by several factors. These include the size of the contract, its visibility within the community, and the length of time it has been operational. We emphasize the importance of exercising caution and conducting your own assessment of the security and suitability of the protocol before engaging with it. This approach empowers users to make informed decisions regarding their involvement with the LADT protocol, ensuring that they have confidence in its security and reliability. --- # 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.ladt.co/economic-model/security.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.