> For the complete documentation index, see [llms.txt](https://docs.ht.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ht.xyz/hypertrade-dex/security.md). # Security Hypertrade is fully non-custodial and permissionless. Users interact directly with the protocol's smart contracts, and no third party ever takes custody of their assets. All swaps, liquidity deposits, and withdrawals happen entirely on-chain, following deterministic rules encoded in the AMM. #### Core security principles * Immutable AMM logic - The core smart-contract logic cannot be altered after deployment, ensuring predictable and verifiable behavior. * Transparent reserves - All token balances inside pools are visible on-chain at all times. Anyone can independently verify liquidity, fees, and swap outcomes. * No privileged execution paths - There are no admin keys or special accounts that can alter pricing, move user funds, or bypass normal pool logic. * Continuous auditing of smart contracts - Smart contracts are subject to ongoing review and external audits to detect and minimize potential vulnerabilities. #### Result Users always retain full control over their assets, interacting directly with verifiable, permissionless smart contracts rather than intermediaries. --- # 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.ht.xyz/hypertrade-dex/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.