> For the complete documentation index, see [llms.txt](https://docs.shiftctrl.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftctrl.money/developer/tab-protocol-smart-contract/reserves.md).

# Reserves

### ReserveSafe contract

Tab Protocol stores BTC reserves into a dedicated ReserveSafe contract. \
No one has permission to unlock BTC from the Safe except Governance (for migration) or VaultManager contract, which is only authorized to perform withdrawal by vault owner.

### ReserveRegistry contract

The ShiftCTRL community can propose the addition of new reserves (such as other forms of wrapped or bridged BTC) or the disabling of a reserve already registered through the protocol's governance module. 

At inception, [cbBTC](https://www.coinbase.com/en-gb/cbbtc) (Base Mainnet: [0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf](https://basescan.org/address/0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf)) is pre-registered in the ReserveRegistry contract and can be used to create a vault for minting Tabs. 

{% hint style="info" %}
**Note:** The ReserveRegistry contract supports reserve tokens with varying decimal values. \
For example, while cbBTC operates with 8 decimals, vaults at the protocol level can support up to 18 decimals. The system will call the `ReserveSafe.getNativeTransferAmount` function to retrieve the correct reserve amount based on the reserve type's decimal value.
{% endhint %}

{% hint style="info" %}
**Note:** 

Each Tab type is associated with default configuration values below regardless of Reserve Type in use:

* Minimum reserve ratio: 180%
* Liquidation ratio: 120%

These values can be adjusted by calling the `GovernanceAction.updateTabParams` function.
{% endhint %}


---

# 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.shiftctrl.money/developer/tab-protocol-smart-contract/reserves.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.