# LeverAcc Docs

## LeverAcc Docs

- [Welcome](https://leveracc.gitbook.io/leveracc-docs/readme.md)
- [What is LeverAcc](https://leveracc.gitbook.io/leveracc-docs/getting-started/what-is-leveracc.md)
- [Background & Problems](https://leveracc.gitbook.io/leveracc-docs/getting-started/background-and-problems.md)
- [LeverAcc's Solution](https://leveracc.gitbook.io/leveracc-docs/getting-started/leveraccs-solution.md)
- [Pre-funding](https://leveracc.gitbook.io/leveracc-docs/basics/pre-funding.md)
- [Dual Vault Liquidity Engine](https://leveracc.gitbook.io/leveracc-docs/basics/dual-vault-liquidity-engine.md)
- [Algorithmic Circuit Breaker Protection](https://leveracc.gitbook.io/leveracc-docs/basics/algorithmic-circuit-breaker-protection.md): Multi-Layer Risk Containment
- [Account System Security Enhancement](https://leveracc.gitbook.io/leveracc-docs/basics/account-system-security-enhancement.md)
- [Multi-Mode Trading Architecture](https://leveracc.gitbook.io/leveracc-docs/basics/interactive-blocks.md): Unified Access, Flexible Execution
- [Dual-Point Economic System](https://leveracc.gitbook.io/leveracc-docs/basics/dual-point-economic-system.md): Incentive Alignment Engine
- [Roadmap](https://leveracc.gitbook.io/leveracc-docs/resources/roadmap.md)
- [Term of Use](https://leveracc.gitbook.io/leveracc-docs/resources/term-of-use.md): Last Updated: October 13, 2025
- [Privacy Policy](https://leveracc.gitbook.io/leveracc-docs/resources/privacy-policy.md): Last Updated: October 13, 2025


---

# 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, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on a page URL with the `ask` query parameter:
```
GET https://leveracc.gitbook.io/leveracc-docs/readme.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.