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

# Getting Started with Sovryn

{% embed url="<https://youtu.be/X4h-TEsCs8s>" %}

**What is Sovryn?**\
\
Sovryn is a non-custodial and permissionless smart contract-based system for Bitcoin lending, borrowing and margin trading.\
\
**What can I do with Sovryn?**\
\
With Sovryn, you can perform margin trades for Bitcoin with up to 5x leverage, swap between Bitcoin, stablecoins and other tokenized assets, and lend Bitcoin, tokens or stablecoins to earn interest. You can read more about it [here](https://sovryn.app/blog/how-to-earn-and-leverage-bitcoin.html).\
\
**Built on Bitcoin Layer 2**

Sovryn is built on the Rootstock Bitcoin-sidechain, which is validated by Bitcoin PoW miners, while also compatible with the Ethereum Virtual Machine. Sovryn has the best of both worlds- Bitcoin’s security, with solidity smart contracts. Transactions are swift, and low-gas (typically in the $1 range).<br>


---

# 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://sovryn-1.gitbook.io/sovryn/master.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.