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

# sBRD

The BRL yield product, auto-staking on Solana and an ERC-4626 vault on EVM.

sBRD is the BRL-denominated yield product, backed by the same Brazilian Treasury LFTs that reserve the stablecoin. The rate tracks the Brazilian policy rate, currently around 14%.

## How to reach it

Directly with a BRD Digital account, through a partner, or on-chain. See [Yield](/brd-digital-docs/yield.md).

## How the yield reaches you

This depends on the network, and it is the most common point of confusion.

**Solana, auto-staking.** Hold BRD and rewards accrue automatically. No deposit, no staking transaction, no separate token. Your BRD balance grows in place. Accrual applies to verified holders, and there is no sBRD token on Solana. The yield accrues on BRD itself.

**Ethereum and Base, ERC-4626 vault.** Deposit BRD into the vault contract and receive sBRD, vault shares that appreciate against the underlying as yield accrues. ERC-4626 is the standard vault interface, so the shares behave the way integrators expect and compose with lending markets without custom work.

## Contracts

The vault uses deterministic addresses, so sBRD carries the same address on Ethereum and Base.

<table><thead><tr><th width="130">Network</th><th width="110">Standard</th><th>Contract</th></tr></thead><tbody><tr><td><strong>Ethereum</strong></td><td>ERC-4626</td><td><a href="https://etherscan.io/token/0x98cb24420C349DDB5f4cf0BA3f83372C1Dc1b411"><code>0x98cb24420C349DDB5f4cf0BA3f83372C1Dc1b411</code></a></td></tr><tr><td><strong>Base</strong></td><td>ERC-4626</td><td><a href="https://basescan.org/token/0x98cb24420C349DDB5f4cf0BA3f83372C1Dc1b411"><code>0x98cb24420C349DDB5f4cf0BA3f83372C1Dc1b411</code></a></td></tr></tbody></table>

The BRD contracts are on [Stablecoin](/brd-digital-docs/stablecoin.md).

{% hint style="warning" %}
Always verify a contract address against this page or the dashboard before transacting. Never take an address from an email or a direct message.
{% endhint %}

## Terms

* **Underlying:** Brazilian Treasury LFTs, 100%.
* **Rate:** floats with the Brazilian policy rate.
* **Fees:** waived, so the net rate paid to holders is the benchmark rate.
* **Denomination:** BRL. A balance of 1,000 is 1,000 BRD.

## Risk

The collateral is held off-chain and carries no smart-contract risk. Taking the position into a lending market adds that protocol's smart-contract risk, in exchange for the returns looping can produce. See [Yield](/brd-digital-docs/yield.md).

## Related pages

* [Yield](/brd-digital-docs/yield.md), the thesis and the risk breakdown
* sBRDusd, the USD-settled product
* Proof of Reserves, what backs it


---

# 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://brd-digital.gitbook.io/brd-digital-docs/yield/sbrd.md?ask=<question>&goal=<user_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.
