> For the complete documentation index, see [llms.txt](https://docs.nectarliquid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nectarliquid.com/security.md). # Security #### General Safety Exercise caution when interacting with any smart contract or blockchain application. Nectar Liquid operates parallel network environments across both Asset Chain Mainnet and Asset Chain Testnet. While the Testnet allows risk free experimentation using faucet assets, the Mainnet involves real financial capital. Even with rigorous testing and battle tested open source architecture, smart contract code can contain vulnerabilities that remain undetected even after review. Keep the following points in mind to protect your assets across both active networks: * Phishing attacks and scams are prevalent across both traditional and blockchain ecosystems. * Blockchain specific phishing techniques include tricking users into revealing private keys or seed phrases or tricking them into signing malicious transactions. * Consider maintaining two separate wallets. You can use one cold wallet with minimal decentralized application exposure to store the majority of your production assets and a separate active wallet for interacting with testnets or unfamiliar websites. * Before signing any transaction on either Asset Chain Mainnet or Testnet, verify the target contract address and review the operation name being signed. Most Web3 wallets display these details to assist with this verification. * Only interact with the official Nectar Liquid interfaces and the verified contract addresses matching your active network wallet selection. #### Audits Nectar Liquid is built upon the robust and heavily audited source code of GMX. The underlying smart contract architecture that powers our exchange has historically undergone extensive security reviews by leading blockchain security firms. The core logic we utilize has been audited by the following organizations: * Guardian: Conducted comprehensive multi month engagements covering the full severity range of the core synthetic architecture, fee automations, and protocol changes. * ABDK: Audited the foundational synthetic contracts at specific commits. * Certora: Conducted formal verification and audits of the synthetic architecture. * Dedaub: Audited the underlying smart contract infrastructure. * Sherlock: Conducted decentralized security reviews on protocol updates. To ensure transparency across our dual network setup, code audits are categorized by their specific deployment environments: Beta Testnet Smart Contracts Native smart contracts and environment integration parameters undergo continuous automated testing and internal optimization to ensure flawless compatibility with the Asset Chain consensus mechanism. Mainnet Production Contracts Production smart contract configurations are subjected to external auditing validations specific to the Asset Chain execution environment. Verified deployment addresses are published cleanly across our official contract directories to eliminate any configuration confusion. #### Bug Bounty Nectar Liquid is committed to maintaining a secure and resilient trading environment for all users across both operational networks. Community security contributions are highly valued. We encourage developers and security researchers to review our open source implementations. Our official bug bounty initiative features independent scopes and distinct tracking depending on the deployment layer. Mainnet Bug Bounty Targets * Scope: All live production smart contracts deployed on Asset Chain Mainnet, live production REST API endpoints, and production oracle integration modules. * Rewards: Distributed in live production assets or stablecoins based on the severity classification of the uncovered vulnerability. Beta Testnet Bug Bounty Targets * Scope: Experimental smart contracts deployed on Asset Chain Testnet, sandbox testing endpoints, and trial execution configurations. * Rewards: Tailored to incentivize early platform optimizations and security mapping prior to production code transitions. Full program details, submission guidelines, and active reward tier scales are officially published and updated on our dedicated Immunefi bug bounty page and verified community communication channels. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nectarliquid.com/security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.