> For the complete documentation index, see [llms.txt](https://leverage-protocol.gitbook.io/leverage-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leverage-protocol.gitbook.io/leverage-protocol/protocol-overview/how-it-started.md).

# How it started?

<figure><img src="/files/OQ1ZMjZvVqiQx4Msn5v3" alt=""><figcaption></figcaption></figure>

Leverage Protocol was born out of a desire to address the limitations and shortcomings of existing centralised exchanges. As the cryptocurrency market has grown in size and popularity, it has become increasingly clear that centralized exchanges have significant drawbacks, including the need to entrust assets to third-party custodians and the potential for centralised control to be abused.

We recognized the need for a decentralised alternative that would give users complete control over their assets and transactions, and we set out to create a platform that would provide a secure, transparent, and efficient way to trade cryptocurrencies with leverage directly from users' wallets.

Our team has extensive experience in both traditional finance and the cryptocurrency industry, and we are passionate about the potential of decentralised finance to transform the financial industry. With Leverage Protocol, we aim to empower traders and lenders by providing a fully decentralised platform that enables leveraged trading and lending with complete control over their funds.

We believe that the future of finance is decentralised and that the transition to a native financial layer on the internet is critical for humanity. We are committed to advancing this vision by continuing to innovate and develop cutting-edge solutions that enable decentralised trading and lending for everyone.


---

# 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, and the optional `goal` query parameter:

```
GET https://leverage-protocol.gitbook.io/leverage-protocol/protocol-overview/how-it-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.