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

# About b0as

<div align="left"><figure><img src="/files/zbeIubLexjeE78mV1Cvq" alt="" width="563"><figcaption></figcaption></figure></div>

## Introduction

**B0as** is the first ordinals collection deployed as a DMT Blockdrop. The collection is deployed as a blockdrop to Natcats community, meaning that each b0a can only be inscribed by the holder of the Natcat that shares its block number. \
\
Each b0a is a metaverse collectible taking the form of a unique snake with traits revealed at the time of inscription by its holder. B0as are generated using Bitcoin blockchain data, and all b0as have the potential to reveal an ultra-rare trait generated by the blockchain on inscription.&#x20;

The collection will unveil an additional functionality at a future date.\ <br>

## Blockdrop Distribution&#x20;

**Blockdrop** is a distribution method that allows for the deployment of new DMT assets to holders of assets in existing DMT collections.&#x20;

As a blockdrop to Natcats community, b0as can be inscribed exclusively by Natcats holders. Each  holder has the exclusive permissions to inscribe the b0a that shares a block number with the Natcat they hold. *For example, the holder of Natcat 828828 holds the exclusive rights to inscribe b0a 828828.*\
\
Blockdrop permissions persist in time and with the transfer/sale of the parent Natcat until utilized. For this reason, blockdrop supply is likely to be introduced to the market gradually over time. This gradual dynamic plays an important role in the design of rarities within the b0as collection. \
\
Blockdrop is developed by [TAP Protocol](https://x.com/tap_protocol) and [The Block Runner](https://x.com/TheBlockRunner) and marketplace support is provided by [Mscribe.io](https://x.com/mscribeio).\
\
Additional information on blockdrops can be found [here](https://mscribeio.medium.com/how-to-master-the-use-of-dmt-blockdrops-492749ddc995).<br>

## Supply

There is one b0a blockdrop for every Natcat in circulation (8064 at the time of deployment). B0as blockdrops will become available for future Natcats supply automatically. To be revealed, b0as blockdrops must be inscribed by their holders. \
\
For more information on Natcats supply, visit the [Natcats gitbook](https://natcats.gitbook.io/natcats).&#x20;

<br>

## Trait Generation

Each b0a contains unique traits generated through the Bitcoin blockchain. These traits are generated using two data fields, **Bitcoin Block Number** and **Ordinals Inscription ID**.  \
\
Traits generated from Bitcoin Block Number are **known** prior to inscription, while traits generated based on Ordinals Inscription ID are **unknown** - as this field is generated at the time of inscription. These data fields are used for generation across paths in b0as: **Special Traits and Color Pattern.**

*Notably, while the traits generated through inscription ID are unpredictable, these unpredictable outcomes are achieved without requiring a black-box randomization function. Outcomes are verifiable via any* [*Ordinals explorer*](https://ordinals.com/inscription/386b7ab9d6fd418d8757edea8de3fcb937c3bbc38f17b9b3db44fc4123f78be0i0)*.*\
\ <br>

## Special Traits

Special traits are only found in **some b0as**. These traits are unpredictable prior to inscription.

### Special Trait Pattern Definition

Each b0as special trait is assigned to a pattern, defined as a substring of text (e.g. "aaa") which may occur in a b0a's Inscription ID once generated. \
\
For example, the trait "tongue piercing" is associated with the pattern "**aaa**", and can be found in inscription "e95..." but not in inscription "d64..." in the sample inscriptions below.

<table><thead><tr><th width="408">Sample Inscription ID</th><th>Contains "aaa"</th><th>Tongue piercing</th></tr></thead><tbody><tr><td>e95f28b5a2828<mark style="background-color:green;"><strong>aaa</strong></mark>8631e53483dbe37c300fb4398b37c3b727cbd7e0a210966i0</td><td><mark style="background-color:green;">true</mark></td><td><mark style="background-color:green;">yes</mark></td></tr><tr><td>d6460f6a17b927dd6a2e9704001fa88e8ca2ea08f80b625b20aef9ef4b8c408ei0</td><td><mark style="background-color:red;">false</mark></td><td><mark style="background-color:red;">no</mark></td></tr></tbody></table>

### Probability-based Rarity Tiers

Because trait assignment is unpredictable AND because blockdrops are inscribed over an extended timeframe, the exact supply of a given special trait cannot be known at the time of the project's deployment, and will likely never be revealed in full.\
\
For this reason, rarities of traits can be assessed through **probability of occurrence**. Patterns of a given length (e.g. 3 characters such as "aaa", or 4 characters such as "aaaa") have a certain probability of occurring within the Ordinals ID field, which is a 64 digit hexadecimal string.\
\
These probabilities can be used to establish standard rarity tiers for traits generated using this field.&#x20;

<table><thead><tr><th>Pattern Length</th><th width="224">example</th><th width="223">Probability </th><th>Rarity</th></tr></thead><tbody><tr><td>2</td><td>contains "aa"</td><td>1:5</td><td><mark style="background-color:green;">Common</mark></td></tr><tr><td>3</td><td>contains "aaa"</td><td>1:70</td><td><mark style="background-color:blue;">Uncommon</mark></td></tr><tr><td>4</td><td>contains "aaaa"</td><td>1:1k</td><td><mark style="background-color:purple;">Rare</mark></td></tr><tr><td>5</td><td>contains "aaaaa"</td><td>1:10k</td><td><mark style="background-color:red;">Ultra Rare</mark> </td></tr><tr><td>6</td><td>contains "aaaaaa"</td><td>1:500k</td><td><mark style="background-color:orange;">Ultra Rare +</mark></td></tr></tbody></table>

### &#x20;Special Traits

The following special traits can be found in b0as.&#x20;

| Trait                     | Pattern | Probability | Rarity                                                     |
| ------------------------- | ------- | ----------- | ---------------------------------------------------------- |
| **Tongue**                | aa      | 1:5         | <mark style="background-color:green;">Common</mark>        |
| **Tongue piercing**       | aaa     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |
| **Alien tongue piercing** | aaaa    | 1:1000      | <mark style="background-color:purple;">Rare</mark>         |
| **Bow**                   | bbb     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |
| **Alien Bow**             | bbbb    | 1:1000      | <mark style="background-color:purple;">Rare</mark>         |
| **Spikes Choker**         | ccc     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |
| **Alien Spikes Choker**   | cccc    | 1:1000      | <mark style="background-color:purple;">Rare</mark>         |
| **Blood Drips**           | ddd     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |
| **Poison Drips**          | ddddd   | 1:10k       | <mark style="background-color:red;">Ultra Rare</mark>      |
| **Pearls**                | eee     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |
| **Alien Pearls**          | eeee    | 1:1000      | <mark style="background-color:purple;">Rare</mark>         |
| **Sun Hat**               | fff     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |
| **Alien Sun Hat**         | ffff    | 1:1000      | <mark style="background-color:purple;">Rare</mark>         |
| **Tail Bow**              | 888     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |
| **Alien Tail Bow**        | 8888    | 1:1000      | <mark style="background-color:purple;">Rare</mark>         |
| **Tail Piercing**         | 696     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |
| **Alien Tail Piercing**   | 6969    | 1:1000      | <mark style="background-color:purple;">Rare</mark>         |
| **Cig**                   | 420     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |
| **Alien Cig**             | 42024   | 1:10k       | <mark style="background-color:red;">Ultra Rare</mark>      |
| **Venom Cig**             | 420420  | 1:500k      | <mark style="background-color:orange;">Ultra Rare +</mark> |
| **Reverse b0a**           | b0a     | 1:70        | <mark style="background-color:blue;">Uncommon</mark>       |

\
\ <br>

## Color Pattern

Each b0a features a **distinct color pattern** comprised of 39 segments, with 10 possible color variations within each segment.&#x20;

### Color Pattern Definition

The first 32 segments of the color pattern are determined using Inscription ID, and cannot be predicted prior to inscription. The final seven segments are determined using Block Number, and are known prior to inscription.&#x20;

<table><thead><tr><th width="160">Segments</th><th width="145">Determined by</th><th width="219">Definition</th><th>Example</th></tr></thead><tbody><tr><td>1 - 32, starting with/including head</td><td>I<strong>nscription ID</strong></td><td>First 32 values in 64 digit hexadecimal string, reading L to R.</td><td><mark style="background-color:orange;">386b7ab9d6fd418d8757edea8de3fcb9</mark>37c3bbc38f17b9b3db44fc4123f78be0i0</td></tr><tr><td>33 - 39, ending on/including tail</td><td><strong>Block number</strong><br></td><td>All values, reading L to R and treating null as "0".</td><td> <mark style="background-color:orange;">624000</mark></td></tr></tbody></table>

The values present in each digit placement within the inscription ID or block number are used to select from the following **color map**.\*<br>

<table><thead><tr><th width="74"> </th><th width="175">Color</th><th width="491"> Value contains...</th><th data-hidden></th></tr></thead><tbody><tr><td><img src="/files/vQgJodWpKqsqtsuF6Zee" alt="" data-size="original"></td><td>Light blue </td><td>0** or a </td><td></td></tr><tr><td><img src="/files/uYvfktg5YfLCmsvHM6Zo" alt="" data-size="original"></td><td>Indigo</td><td>1</td><td></td></tr><tr><td><img src="/files/otVBZSRnG7zyCbGRT6Dm" alt="" data-size="original"></td><td>Purple</td><td>2</td><td></td></tr><tr><td><img src="/files/Lx4t8p2yMFcmWB3feHeI" alt="" data-size="original"></td><td>Yellow</td><td>3 or b</td><td></td></tr><tr><td><img src="/files/Chqhtp1rtIEeWznvh7UR" alt="" data-size="original"></td><td>Blue</td><td>4 or c</td><td></td></tr><tr><td><img src="/files/MoUB9lCStvR5eLhxihr5" alt="" data-size="original"></td><td>Dark Green</td><td>5</td><td></td></tr><tr><td><img src="/files/QXYCE7KeSGiubUGbMQiZ" alt="" data-size="original"></td><td>Grey</td><td>6</td><td></td></tr><tr><td><img src="/files/SvACjIgjOe4JKi2bPKbw" alt="" data-size="original"></td><td>Green</td><td>7 or d</td><td></td></tr><tr><td><img src="/files/IY6jXl94t9n36tBzxVjr" alt="" data-size="original"></td><td>Pink</td><td>8 or e</td><td></td></tr><tr><td><img src="/files/lOdvZGBaJf6TVqMaKgmI" alt="" data-size="original"></td><td>Orange</td><td>9 or f</td><td></td></tr></tbody></table>

### Hypercommon Color Rarities

In b0as, due to the large array of color segments (39) it is **unlikely** that a given color will **not occur** at least once in the available segments. The value that returns green, for example, has a 99.2% chance of occurence in a b0a.\
\
B0as color traits are therefore common to the degree that they are unlikely or highly unlikely to not occur. These traits can be  described as "hypercommon". The absence of one of these traits therefore becomes a rare feature. For example, only \~1:100 b0as will not contain the color green. \
\
The rarities of b0as that exclude hypercommon traits compounds as additional colors are incorporated. For example, the likelihood that the 41 digit b0a string will not contain yellow OR green is reduced to only 0.004%, or 1:26k.<br>

| Hypercommon Tiers                                       | Probability |
| ------------------------------------------------------- | ----------- |
| excludes x1 single value color (e.g. indigo)            | 1:20        |
| excludes x1 two value color (e.g. green)                | 1:100       |
| excludes x1 single value color AND x1 two pattern color | 1:315       |
| excludes x2 two value color                             | 1:26k       |

### Emergent Color Rarities

Additionally, the wide array of possible variations in color pattern allows for features which are not predetermined to emerge as desireable and/or rare as blockdrops as revealed. These have the potential to be identified by the community and may include counts of colors, certain sequences of colors, etc. \ <br>

## B0as Interactive Reveal as a Proto-Metaverse-Activity

B0as introduces a novel reveal dynamic in which assets and the supply of traits within the collection will be discovered interactively by a decentralized community over an extended timeframe (e.g. 100+ years or more).&#x20;

The community controls the pace of the reveal through participating in blockdrop inscription, while witnessing the collection's evolution over time. Ultra-rare assets have the potential to be introduced at any point in time over the coming decades. \
\
This dynamic is designed to function as a proto-metaverse-activity, in which interactive processes and blockchain-based generation through DMT intersect to produce events originating in the Bitcoin metaspace. \ <br>

## How to Inscribe

Information on how to inscribe b0as blockdrops can be found [here](/b0as/how-to-inscribe.md).

## Acknowledgements

B0as launch partners are [The Block Runner](https://twitter.com/TheBlockRunner) and [Mscribe](https://twitter.com/mscribeio)\
\
DMT is developed and supported by The Block Runner and [TAP Protocol](https://x.com/tap_protocol)\
\
B0as and Natcats are created by [Evonbit.](https://x.com/Evonbit)\
\
Special thanks to the Natcats community and broader DMT community for your support.


---

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

```
GET https://natcats.gitbook.io/b0as/about-b0as.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.