# Digital Elements

Any piece of block data can be used to identify a pattern on Bitcoin's blockchain. Patterns recognized are inherently open source, anyone can point to that pattern and create a project derivative that references the existence of that pattern.&#x20;

{% hint style="danger" %}
Naming an element is a registry. Naming an element can only be done once and you can not reuse the same name to represent another element.&#x20;
{% endhint %}

The decision-making journey when postulating the existence of a desired sequence or pattern within these fields of information is executed through a process we've labeled as "**Bitinformatics**". A nod to the interdisciplinary life sciences field of Bioinformatics which develops methods for understanding biological data to interpret genomic sequences that influence biological processes.

Through Bitinformatics, an element discoverer is actively embedding a set of instructions onto the Bitcoin blockchain through Ordinal Inscriptions based on the [`.element` registry specification](/digital-matter-theory/introduction/digital-elements/.element-registry.md). This action allows independent indexers to identify the quantifiable existence of the pattern and account for new supply introduction upon the minting of new blocks. This introduces many new root value information sources that can be deployed and utilized by digital token creators, adding an optional non-arbitrary immutable variable to ecosystem design.


---

# 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://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/digital-elements.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.
