# CAVIAR

`resource_rdx1tkk83magp3gjyxrpskfsqwkg4g949rmcjee4tu2xmw93ltw2cz94sq`

[`explorer link`](https://dashboard.radixdlt.com/resource/resource_rdx1tkk83magp3gjyxrpskfsqwkg4g949rmcjee4tu2xmw93ltw2cz94sq)

<figure><img src="https://2889101437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHNlgl7ttywm5Xh8uj9vm%2Fuploads%2FUTLaOGBjKKDLCS74hDBS%2Fimage.png?alt=media&#x26;token=5b28dc8c-a787-4e20-8d7a-ceadaba3ac99" alt=""><figcaption></figcaption></figure>

## Products

CAVIAR powers the following products:

* HyperStake - A very concentrated LSULP/XRD pool that self-adjusts using on chain oracle data.

### Tokenomics and features <a href="#tokenomics-and-features" id="tokenomics-and-features"></a>

* Like the legacy mainnet token, the Babylon CAVIAR has a fixed (unmutable) supply of 1BIO Tokens
* Unlike the legacy version, new Babylon CAVIAR is *burnable* which cannot be changed
* You can bridge the legacy CAVIAR for Babylon CAVIAR for a 1-to-1 basis. This is one way only!
* CAVIAR was burned in the one off Surge airdrop waves program, reducing it's supply significantly to approximately 904M

### CAVIAR Utility - Key points <a href="#floop-utility-key-points" id="floop-utility-key-points"></a>

* Protocol Fees: All protocol fees generated from the aforementioned products are directly transferred from the smart contracts to the CAVIAR fee vaults in an atomic manner.
* Fee Management: Currently, the fees are entirely used to burn CAVIAR, thereby reducing its supply to zero. The fee vaults are configured to burn 100% of the CAVIAR.
* Future Outlook: In the future, as the fees increase significantly and/or the CAVIAR supply diminishes substantially and once it is deemed regulatory safe, the fee vaults may transition from burning to earning. At that point, CAVIAR staking will be enabled and stakers will have the opportunity to claim the fees directly, transforming CAVIAR into a yield-bearing token.


---

# Agent Instructions: 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:

```
GET https://docs.caviarnine.com/tokens/caviar.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.