> For the complete documentation index, see [llms.txt](https://docs.hashstack.finance/developers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashstack.finance/developers/supply-and-borrow/introduction.md).

# Introduction

The protocol allows anyone to be a supplier. These supplied funds are then used to issue loans for the borrower. We make use of the ERC 4626 standard for our supply vault. When a user deposits funds to the corresponding vault, rTokens of that particular asset (Representational tokens) are minted to the user. These rTokens represent user shares in the deposit vault. We follow a similar logic in borrow token contract, though it is not designed to follow the 4626 standard (as it is not a vault). User will receive dTokens (Debt tokens) for borrowing and these tokens represent the share of total debt owed by the user to the protocol.

<figure><img src="/files/mcLix8i4AXQ3gdgFbHQP" alt=""><figcaption><p>Fig. 1 - Interaction between supply and borrow contracts</p></figcaption></figure>

The above diagrams describe the basic actions a supplier and borrow can do. It shows how to borrow and supply contracts interact with each other.


---

# 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://docs.hashstack.finance/developers/supply-and-borrow/introduction.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.