> For the complete documentation index, see [llms.txt](https://docs.koo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.koo.xyz/about-koo.xyz.md). # About Koo.xyz ## Introduction Koo.xyz is a next-generation decentralized derivatives exchange built on Arbitrum. Its core vision is to create the ultimate trading platform for **high capital efficiency and full asset sovereignty**. The product is built around four pillars: **NFT accounts**, **yield-bearing margin**, **real-yield governance**, and **professional multi-asset trading**. *** ### Current market pain points The market is still fragmented. Traders often have to choose between user experience and security. Right now, most of Perp DEXs still face major bottlenecks: * **Weak performance:** Fully onchain interaction creates high latency and slippage. This does not meet the needs of market makers or high-frequency traders. * **Low capital efficiency:** Margin sits idle while waiting for positions or supporting open positions. It does not generate additional yield. * **Rigid account structure:** Trading accounts are tightly bound to wallet addresses. Accounts with performance history or unrealized PnL cannot be transferred. * **Weak token utility:** Without real protocol revenue sharing, governance tokens often become simple farming assets. *** ### Koo.xyz solution and core advantages Koo.xyz rebuilds the derivatives trading stack from the ground up. #### 1. Native NFT account model * **The account is the asset:** Your full trading account, including assets, positions, trading history, and even API permissions, is minted as a unique NFT. * **Transferable ownership:** You can buy, sell, or transfer the full account on secondary markets. If you want to exit with a profitable position, you can transfer the account NFT directly. #### 2. Yield-bearing trading margin * Deposited collateral starts generating yield immediately. Idle USDC margin can be deployed safely into leading DeFi protocols such as Aave v3. * This improves capital efficiency without sacrificing liquidity or liquidation safety. #### 3. Multi-asset derivatives markets * Trade beyond crypto on a single platform. * Supported categories include crypto perpetuals, FX, commodities, equities, and RWA derivatives. #### 4. Pure onchain withdrawals and continuous risk control * **Full control:** Withdrawal rules are enforced directly by smart contracts. Even in extreme markets, valid withdrawals cannot be frozen through backend approval flows. * **Continuous risk model:** Institutional-grade high-frequency risk control and margin calculations support complex strategies and large positions. #### 5. Real yield and community governance with $KFC * Koo.xyz rejects Ponzi-style token design. **All trading fee revenue** is distributed to $KFC holders. * Holders receive rewards without complex staking flows. The team also performs regular buybacks to return protocol growth to the community. *** **With Koo.xyz, you do not need to trust anyone.** --- # 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.koo.xyz/about-koo.xyz.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.