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

# Hello $BUNNY☆

## PHASE ONE

### ☆ Abstract

The Tokenized Asset Protocol (TAP) on the Bitcoin blockchain is an extendible OrdFi-enabling system that uses 'tapping' for transaction verification without L2 chains, complementing BRC-20 and evolving through community-driven development. One of the challenges within the TAP ecosystem has been the absence of a universally accepted trading pair. $BUNNY seeks to pioneer the world of asset hopping within the Tap Protocol ecosystem. 

### ☆ Problem and Solution

**Problem:** The TAP ecosystem currently lacks a universally accepted trading pair, leading to fragmented and potentially less efficient trading experiences.

**Solution:** $BUNNY aims to serve as a popular trading pair within the TAP environment, facilitating efficient transitions between different assets and a streamline hopping experience.

### ☆ Core Features

1. **$BUNNY as Intermediary**: $BUNNY acts as an intermediary token to enhance liquidity within the TAP ecosystem. By having a standard token like $BUNNY that many hoppers are willing to accept, it simplifies trade decisions and can potentially reduce price confusion.
2. **Direct Token Swaps**: Utilizing the TAP protocol's "token-trade" function, users can engage in direct token hops, trading their desired tokens for $BUNNY or vice versa.
3. **Potential for Optimized Trading**: With $BUNNY serving as a common intermediary, there's potential for more streamlined trading routes in the TAP ecosystem. The efficiency gains will depend on the uptake of $BUNNY as a preferred trading token and the development of mechanisms like dynamic fee structures.
4. **(Concept) Hybrid Multi-Hopping**: Empowers users with the freedom to choose between direct hops and multi-stage hops for optimal trading pair transitions.

## TOKEN DETAILS

**Token Ticker:** BUNNY

**Progress:** 100.00%

**Maximum Supply:** 1,000,000,000

**Limit:** 1,000,000,000

**Decimals:** 18

**Transaction ID:** bf7d222141b7ae9efa2b3eceb088e0bcfa7407bb4e6e4ace8529c83943bcb27b

**Number:** 25665466

**Timestamp:** 8/21/2023, 1:24:16 AM

**Block:** 804189

**Inscription:** bf7d222141b7ae9efa2b3eceb088e0bcfa7407bb4e6e4ace8529c83943bcb27bi0

**Cursed:** No

<figure><img src="/files/nHZI9nKn6TtGTYInNMJo" alt=""><figcaption><p>$BUNNY BANK</p></figcaption></figure>

***

## TAP PROTOCOL BASICS

{% hint style="info" %}
Refer to tap protocol specs: <https://github.com/BennyTheDev/tap-protocol-specs>
{% endhint %}

### ☆ Tap Protocol: Creating a Trade

To inscribe a trade, a seller has to inscribe a text inscription in the following format:

```
{
  "p" : "tap",
  "op" : "token-trade",
  "side" : "0",
  "tick" : "tap",
  "amt" : "1",
  "accept" : [
    {
      "tick" : "benny",
      "amt" : "1"
    },
    {
      "tick" : "BUNNY",
      "amt" : "1"
    }
  ],
  "valid" : "900000"
}
```

{% hint style="info" %}
Make sure to[ TAP!](#wtf-is-tapping)&#x20;

After inscribing the function, sellers have to send the inscription to themselves to approve (tapping).
{% endhint %}

### ☆ Tap Protocol: Cancelling a Trade

In order to cancel an existing, non-expired trade. The following function has to be inscribed and tapped (sent to yourself):

```
{
  "p" : "tap",
  "op" : "token-trade",
  "side" : "0",
  "trade" : "<inscription id>"
}
```

{% hint style="info" %}
Make sure to[ TAP!](#wtf-is-tapping)\
After inscribing the function, sellers have to send the inscription to themselves to approve (tapping).
{% endhint %}

### ☆ Tap Protocol: Fill a Trade

Valid trades are fillable by inscribing a token-trade inscription that specifies which offered token to purchase, with a reference to the original trade inscription. Additionally, an optional fee receiver may be specified. The fee receiver will earn fixed 0.3% of the token that the buyer is purchasing. The fee is applied on top of the purchase amount.

```
{
  "p" : "tap",
  "op" : "token-trade",
  "side" : "1",
  "trade" : "<inscription id>",
  "tick" : "BUNNY",
  "amt" : "1",
  "fee_rcv" : "<fee receiver address>"
}
```

{% hint style="info" %}
Make sure to[ TAP!](#wtf-is-tapping)\
After inscribing the function, buyers have to send the inscription to themselves to approve (tapping).
{% endhint %}

### ☆ WTF IS TAPPING?

<https://x.com/tap_protocol>

***

<figure><img src="/files/HVTHzMYlURsqQwCLgN54" alt=""><figcaption><p>$BUNNY</p></figcaption></figure>

### ☆ Future Developments

The $BUNNY ecosystem aims to become the go-to platform for asset hopping.

***

**Summary** Unlock seamless token hops with $BUNNY! Our hybrid direct-hopping mechanism will guide you in choosing the best path for trading within the Tap Protocol ecosystem.&#x20;

{% hint style="info" %}
Follow [@ordinalOS](https://x.com/ordinalos) for more information
{% endhint %}