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

# Overview

Our **FLOOP** and **CAVIAR** tokens are associated with our different DeFi products and serve as utility and DAO tokens for them as follows.

{% hint style="info" %}
All simple trading products are part of the FLOOP ecosystem
{% endhint %}

The **FLOOP** token:

* Aggregator
* LSU Pools
* Limit Orders
* Shape Liquidity
* Simple Pools

{% hint style="info" %}
The more complex products are part of the CAVIAR ecosystem, e.g. oracle based trading products, derivatives, trackers etc.
{% endhint %}

The **CAVIAR** token:

* HyperStake

## The CaviarNine Bridge:

FLOOP and CAVIAR were minted prior to the Babylon upgrade and the start of dApps on Radix. Holders of such legacy tokens are able to bridge them 1:1 to the Babylon versions that power our products.

The FLOOP and CAVIAR (one-way) bridges are hosted at caviarnine.com. The new Babylon FLOOP and CAVIAR tokens have two key differences:

* They are burnable (by anyone)
* We can update the metadata like name and description (if needed)

As per usual their supply remains unchanged and the are NOT mintable. The bridge mints the entire supply on initialisation and allows old for new forever.

<figure><img src="/files/Kd4948moZtKDDEWgpYND" alt=""><figcaption><p>One-way bridge for CAVIAR and FLOOP to the new burnable Babylon versions</p></figcaption></figure>

## Do I have to bridge CAVIAR or FLOOP?

Nope! You certainly don't have to at all. In fact some people might want to keep the legacy tokens as collector items though they will not have any future utility like their Babylon equivalents.


---

# 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.caviarnine.com/tokens/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.