> For the complete documentation index, see [llms.txt](https://devdocs.silo.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devdocs.silo.finance/protocol-architecture/silo-assets.md).

# Silo Assets

For each asset in a Silo, there are three ERC-20 tokens deployed via Tokens Factory:

* shares token that will represent a collateral
* shares token that will represent protected collateral (cannot be borrowed)
* debt token that will be minted to represent a debt

When the user deposits into a Silo they can decide where their deposit can be borrowed by other users to earn interest. Protected deposits are also called "collateral only" and other users cannot borrow them.\
\
Silo uses the mint and burn functions to operate these underlying tokens. Meanwhile, the transfer is still available and can be used by any third-party application (MetaMask, DEX, etc...). Underlying tokens support hooks and can notify about the basic tokens operations (mint, burn, transfer) third party smart contract if those will be configured in the Silo Repository as a notification receiver for the Silo where operation occurs.\
\
For better understanding, see basic Silo operations with assets state visualization

![Underlying Silo assets state visualization](/files/f9NCRFKds37MgfaJaErJ)


---

# 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://devdocs.silo.finance/protocol-architecture/silo-assets.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.