> For the complete documentation index, see [llms.txt](https://docs.buildex.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildex.global/readme-1.md). # Why DEX Matter Centralized exchanges (CeFi) dominate crypto trading, but history has shown that they also carry structural risks. Billions of dollars are lost each year due to hacks, mismanagement, or arbitrary restrictions. BuilDex addresses these issues with a **non-custodial model** powered by **zk-proofs** and **private pools**. *** ### Key Facts #### **$2.2B+ Lost in 2024** In 2024, crypto platforms suffered losses exceeding **$2.2 billion** from hacks — most of them on centralized exchanges.\ 👉 With BuilDex, custody is non-custodial: **your keys, your funds**. *** #### **$1.5B — Bybit Heist (2025)** In early 2025, the largest exchange hack in history occurred: **$1.5 billion in ETH** stolen from Bybit by North Korean hackers.\ 👉 Centralized custody creates a single point of failure. BuilDex eliminates this risk. *** #### **67% of Theft Linked to CeFi** From 2017 to 2022, over **$30 billion** was stolen in crypto crime. **Two-thirds** of these losses originated from centralized finance platforms.\ 👉 Decentralized models like BuilDex reduce systemic vulnerabilities. *** ### Conclusion Decentralization is not just a trend — it is a **necessary safeguard** against the recurring failures of centralized platforms.\ BuilDex leverages **zero-knowledge proofs** and **Dark Pool execution** to provide security, fairness, and true ownership for every trader. --- # 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.buildex.global/readme-1.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.