> For the complete documentation index, see [llms.txt](https://docs.kryptox.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kryptox.finance/getting-started/trade-and-earn.md).

# Trade and Earn

* Deposited margin does not stay idle. It is automatically deployed to:
  * Leading DeFi lending protocols such as Aave and Compound
  * Low-risk onchain strategies under strict risk controls
* Most of the yield belongs to the user. The platform only takes a share of the interest.
* Interest is settled every 8 hours and can be used as margin.

\
Routing margin into yield strategies is not as simple as connecting to a lending protocol. It is a system-level problem involving **liquidation safety, liquidity matching, and extreme market response**:

* Yield strategies must support instant redemption and must not interfere with liquidation
* Interest settlement and margin calculation must stay strictly decoupled to avoid circular dependencies
* In extreme markets, liquidation and risk reduction must take priority over yield maximization

KryptoX solves this by **isolating yield positions from trading margin logic** and applying a **conservative collateral availability model**. This lets the platform share yield without weakening system safety.\
\
\
For more details, see [Yield-bearing USDC](https://docs.kryptox.finance/earn/yield-bearing-usdc)


---

# 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://docs.kryptox.finance/getting-started/trade-and-earn.md?ask=<question>
```

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.