> For the complete documentation index, see [llms.txt](https://nobots.gitbook.io/nobots-gitbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nobots.gitbook.io/nobots-gitbook/security.md). # 🛡️ Security #### General safety ⚠️ Exercise caution when interacting with any smart contract or blockchain application. Although the NoBots team mitigates risk through rigorous testing, independent audits, smart contract code can contain vulnerabilities that remain undetected even after review. 🧠 Keep the following points in mind: * 🎣 Phishing attacks and scams are prevalent in both traditional and blockchain contexts. * 🕵️ Blockchain-specific phishing techniques include tricking users into revealing private keys or seed phrases, or into signing malicious transactions. * 🗂️ Wallet separation: Consider maintaining two separate wallets — one to store the majority of your holdings (a "cold" wallet with minimal dApp exposure), and a separate wallet for interacting with new or unfamiliar websites. * ✅ Verification: Before signing any transaction, verify the target contract address and review the operation being signed. Most wallets display the operation name and contract details to assist with this. * 🔗 Official links: Only interact with the official NoBots interface and verified contract addresses listed in the contracts page. --- # 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://nobots.gitbook.io/nobots-gitbook/security.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.