# Why did we build this?
Exchanges today sit on mountains of locked collateral. Billions in BTC, ETH, SOL, memecoins, and NFTs sit idle on CEXs, DEXs, and in wallets, trapped as dead weight. Traders can’t touch it, can’t use it, can’t unlock its real value. That capital inefficiency is one of the biggest wastes in crypto.
Quanto was built to flip this script. We let anything be margin, NFTs, LP tokens, even lowcap coins, so traders can finally deploy the assets they already hold. Instead of collateral sitting uselessly, it becomes firepower.
At the same time, this cycle is driven by **lowcap memecoins**, and retail wants leverage on them. We built Quanto to make that possible. If the trend is running, traders should be able to long it with size or short it into the ground.
But most importantly, we wanted a **real flywheel** for the core token. Not just empty promises. Every trade, every liquidation, every fee loops back into QTO through buybacks and burns. Holders don’t just watch volume numbers on a dashboard, they own a piece of the exchange, with a token that is directly tied to the growth of the platform.
Quanto is not just another trading app. It’s a machine built to unlock dead collateral, amplify the biggest narratives of the cycle, and create a community that gets rich together when the exchange wins.
\
**Relevant Topics:**
---
# Agent Instructions: 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://docs.quanto.trade/about-quanto/why-did-we-build-this.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.