# DomoDucks

## **Introduction**

**DomoDucks** is a Bitcoin Ordinals collection wherein each component is cohesively and immutably linked, not merely by marketplace trust or social consensus, but by on-chain provenance.&#x20;

[**Inscription #256**](https://www.ord.io/256) was the first representation of a duck inscribed on Bitcoin. This inscription serves as the parent of the collection. This parent has been combined with generative coding to create the data required for the children of the collection thus establishing a parent-child relationship that will allow collectors to verify the validity of each inscription in the collection. And since the parent inscription is #256, the collection contains 256 children that were created by hashing a random seed value with SHA-256, and each of these children are displayed on a canvas of 2560 pixels, with the collection comprising a palette of 256 colors. And for the icing on the cake, since 256 is divisible by 9 numbers (*i.e.*, 1, 2, 4, 8, 16, 32, 64, 128, and 256), **each child has been inscribed on a Block 9 sat**!

<figure><img src="/files/cwpXmixHstssgNaAaXXi" alt=""><figcaption></figcaption></figure>

This collection is called **DomoDucks** to honor [**Domo**](https://x.com/domodata): the creator of [**ORDI**](https://x.com/domodata/status/1633658974686855168) and of the BRC-20 token standard, [**who kick-started the Goosinals movement with a single X post**](https://x.com/DomoDucks/status/1983890071158665302) (HONK). And, of course, the next logical step from geese is obviously ducks (QUAQ). While Domo is not officially involved in this project, he graciously granted us permission to title this collection after him. Thank you, Domo!

{% columns %}
{% column width="50%" %}
{% embed url="<https://x.com/domodata/status/1709258717902897224>" %}
Domo kick-started Goosinals
{% endembed %}
{% endcolumn %}

{% column width="50%" %}
{% embed url="<https://x.com/domodata/status/1764313544298766438>" %}
Domo supports DomoDucks
{% endembed %}

{% endcolumn %}
{% endcolumns %}

***

<p align="center">👇 <strong>Here's a detailed history for those who want to peek a bit further behind the curtain.</strong> 🫣</p>

{% columns %}
{% column width="16.666666666666664%" %}

{% endcolumn %}

{% column width="66.66666666666667%" %}
{% embed url="<https://x.com/DomoDucks/status/2028137466851398025>" %}
{% endcolumn %}

{% column width="16.666666666666675%" %}

{% endcolumn %}
{% endcolumns %}


---

# 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://domoducks.gitbook.io/domoducks/domoducks.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.
