> For the complete documentation index, see [llms.txt](https://docs.tenderize.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tenderize.me/core-architecture/overview.md).

# Overview

{% hint style="info" %}
At its core, a liquid staking protocol needs three key components: a mechanism to mint tokenized version of staked assets, a liquid market to trade these tokenized assets, and a mechanism to collateralize the tokenized assets.
{% endhint %}

In Tenderize V2, these core components are:

* **TenderVault -** Liquid staking vault that accepts user deposits, staking them to a the validator chosen by the user, minting and burning tTokens.
* **TenderSwap** - A decentralized exchange featuring shared, fractional liquidity which can be accessed by any TenderToken holder.
* **BeefBank** - A borrowing facility to deposit tTokens as collaterl to mint SteaksDollar, a stablecoin pegged to the US dollar. 

Additional components include:

* **TenderTokens (tTokens)** - Elastic supply ERC-20 tokens which represent staked assets and earned rewards 1:1. Price is pegged to the underlying, unstaked asset. 
* **Productive Treasury** - Protocol revenue is directed to the on-chain treasury, once there, it is compounded by providing liquidity on TenderSwap.


---

# 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.tenderize.me/core-architecture/overview.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.