# Home

## The Big Picture

The $HOPE algorithmic token serves as the backbone of a rapidly growing ecosystem aimed at bringing liquidity and new use cases to the Arbitrum network.<br>

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

Inspired by the original idea behind Basis as well as its predecessors (bDollar and soup), Hope Finance is a multi-token protocol that consists of the following three tokens:\
-HOPE ($HOPE).\
-HOPE Shares ($DREAM)\
-HOPE Bonds ($WISH).

## What differentiates $HOPE from other algorithmic tokens?

Unlike previous algorithmic tokens, $HOPE is not pegged to a stable coin— it is instead pegged to $ETH.&#x20;

Why is this?\
Hope Finance believes in the potential of the Arbitrum network, and has chosen to align its mission to both provide value to and derive value from $ETH's future growth. In addition to existing and future use cases such as ETH Pad, $HOPE aims to make ETH the main medium of exchange on the Arbitrum network: this will be achieved by providing a mirrored, liquid asset to $ETH.

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, the Hope Finance team will maintain a focus on innovation around enhanced functionality and use cases.


---

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