> For the complete documentation index, see [llms.txt](https://learn.ember.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.ember.so/ember-protocol/tutorial.md).
# Tutorial
### **How to Deploy Capital**
1. Head over to and click on Launch App
2. Choose a Vault from the list of available strategies
3. Deposit your assets:
* Deposit directly into the selected vault.
* You’ll receive a **receipt token** that represents your shares of the vault (e.g. egUSDC, eSUI, eBTC)
4. **Composability**: Deploy your receipt tokens to Lending
* Supply that receipt token on **Bluefin Lending (**) - you’ll instantly unlock **up to 80%** of your deposited capital as borrowable liquidity.
5. **Loop for Maximum Yield**
* Borrow USDC agasint your egUSDC supply, and use the borrowed funds to redeposit and compound your exposure - enabling **leveraged yield** in a single ecosystem.
6. **Track & Realize Gains**
* Your vault yield is reflected in the **share price** of your position.
* When you withdraw, the difference in share price = your realized gain. For example: if you deposited $1,000,000 on Sept 28 at share price = 1.0040 and now on Oct 28 the share price = 1.0132, you are up to 1.0132/1.0040\*$1,000,000 = $1,009,163 (+0.92% in 30 days, +11.04% annualized). If you are supplying to lending looping, your return will be higher!
* The vaults are updated two times a week on Tuesday and Fridays, and the share price depends on the yield generated by the curator.
7. **Monitor Your Positions**
Switch to the positions tab to see how your positions are doing and to be able to manage them.
---
# 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://learn.ember.so/ember-protocol/tutorial.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.
