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

# Home

## Origins of the protocol

The protocol's underlying mechanism dynamically adjusts $CREAM's supply, pushing its price up or down relative to the price of $AVAX.

Inspired by the original idea behind Tomb.Finance as well as its predecessors (bDollar and soup), IceCream Finance is a multi-token protocol which consists of the following three tokens:

* Cream ($CREAM).
* &#x20;Cream Shares ($CSHARE)
* Cream Bonds ($CBOND).

## What differentiates $CREAM from other algorithmic tokens?

Unlike previous algorithmic tokens, $CREAM is not pegged to a stable coin— it is instead pegged to $AVAX the network token of Avalanche. \
\
Why is this?\
\
We believe in the potential of the Avalanche Network, and have chosen to align its mission to both provide value to and derive value from $AVAX's future growth. As a result our pegged token $CREAM can benefit from the appreciation of the network token.

One of the primary shortcomings of past algorithmic tokens has been a lack of use cases, leaving no good reason for somebody to want to use or hold them. In order to successfully maintain the peg in the long-run, we plan to maintain a focus on innovation by rolling out the implementation of arbitrage boughts as well as using revenue from yield optimization to buy back and burn $CREAM


---

# 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://icecreamfinancial.gitbook.io/icecream-finance/home.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.
