> For the complete documentation index, see [llms.txt](https://candora.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://candora.gitbook.io/whitepaper/introduction.md). # Introduction Centralized exchanges weren’t built to be fair. They were built to scale fast, aggressively, and often at the expense of the very people who trusted them. At first, no one really questioned it. The interfaces got smoother. The apps got faster. Liquidity looked deep. Everything felt like progress. But underneath, something else was taking shape. Retail traders started noticing it in small, frustrating ways. Orders slipping just enough to hurt. Prices moving right before execution. Withdrawals stalling at the worst possible moments. Fees that weren’t obvious until it was too late. You could line up the perfect trade, with timing and conviction aligned, and still come out behind. It's not one big failure. It was a pattern, and people got used to it. They started blaming themselves instead of the system. > “Maybe I was too slow.” > > “Maybe it’s just volatility.” > > “Maybe that’s just how it works.” But it wasn’t. Behind the scenes, execution quality wasn’t equal. Access wasn’t equal. Control definitely wasn’t equal. The system favored those who built it, not those who used it. Liquidity could be shaped. Latency could be exploited. Friction could be introduced exactly where it hurt the most, right when users needed precision, speed, and trust. And over time, people adapted. Not by fixing the system, but by lowering expectations. Losses were rationalized. Friction was normalized. The problem was internalized. *** ### The Breaking Point By late 2025, the illusion finally shattered. Volatility spiked. Panic spread. Bitcoin and major alts cascaded, triggering waves of forced liquidations. Liquidity didn’t just thin. It vanished. Orders stuck. Prices falling. Stop-losses failed. Users were locked out. Meanwhile, liquidation bots executed flawlessly. No lag. No delay. No mercy. > UI down, liquidations continued. > > APIs unstable, liquidations executed. > > Users locked out, positions closed. At this point, it stops looking like coincidence. It looks like priority. The theater is over. For years, exchanges relied on the same explanations: “unexpected traffic,” “temporary degradation,” “infrastructure scaling.” But patterns don’t repeat by accident. If a system only works when nothing is happening, it doesn’t work. Exchanges profit from liquidations, liquidation systems remain operational under stress, user controls fail at the exact same moment. Intentional or not, the outcome is the same: users lose, the system collects. Strategy didn’t matter when execution was broken. Limit orders didn’t fill. Cancels didn’t go through. Orders executed late, or not at all. Positions weren’t updating. At that point, you weren’t trading. You were watching. The late 2025 crash wasn’t just another failure. It was a breaking point. A trigger. Builders, traders, and engineers looked at the same pattern and said: > Enough. Not another patch. Not another PR apology. Not another “we’re upgrading servers.” A reset. Because the problem wasn’t one exchange. It was the standard itself. *** ### Why Candora Exists That frustration is where Candora begins. Not as another exchange chasing growth curves or trading volume headlines, but as a reaction. A refusal to accept that this is “just how things are.” As an answer to a question no one else dared to ask: > What would trading infrastructure look like if it were built to survive the worst day in the market? Candora is built on a different premise: execution should mean something. Orders should behave exactly as expected. No hidden games. No silent penalties. Access shouldn’t come with layers of control designed to slow you down or lock you out. Capital should feel like yours, while still moving through defined security, compliance, and integrity controls where required. Open participation model with user-directed trading and withdrawal intent, supported by institutional-grade, multi-layer custody infrastructure and automated, non-discretionary sanctions screening. No artificial barriers placed between you and your own decisions. This isn’t about optics or marketing language. It’s about correcting what’s been quietly broken for years. *** ### Looking Forward There will be another crash. That’s guaranteed. But what happens next will define the next generation of crypto infrastructure. The platforms that survive won’t be the ones with the loudest narratives. They’ll be the ones that stay online, execute fairly, and preserve user control under stress. Because the truth is, people didn’t leave centralized exchanges because they didn’t understand them. They left because they finally did. Candora exists for those people, the ones who saw through it, who felt the friction, who got tired of playing a game that was never designed to be fair. And decided it was time to fight back. > 2025 exposed the problem. > > Candora is our answer. *** ## Core Philosophy Candora is built around a simple standard: market risk should primarily come from the market, not from avoidable venue design. The system is designed to minimize venue-created risk while keeping execution fair, visible, and reliable under stress. In extreme conditions, predefined stabilization controls may activate to preserve fairness, predictability, and market integrity. The sections that follow define how that standard is implemented across matching, custody, risk, access, and user protection. --- # 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: ``` GET https://candora.gitbook.io/whitepaper/introduction.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.