# Definitions

## Digital Matter Theory

The block runner team summarized the concept as:

> "Digital Matter Theory proposes that it is possible to create a form of digital substance by leveraging the inherent patterns present in data."

The concept of a Non-Arbitrary Space proposed in this book falls within this theory.

## **Non-Arbitrary Tokens**

Non-Arbitrary Tokens or *NATs* are a new type of cryptographic token that are associated with a user-defined pattern called an *element.*

A NAT can be minted if (and only if) a block on the blockchain matches the pattern defined in the associated element.

For example, an element may define the pattern of “42” matching the transaction count of a block. A NAT for this element can only be minted if the pattern “42” is contained in the *tx\_count* field of the block. Matching fields in the instance would include “42”, “142” or “3428”.

As blocks are immutable (both in contained data and in location on the blockchain), this results in each NAT type having a distribution and quantity that is defined by blockchain data, hence it is *non-arbitrary* in nature.

## **Non-Arbitrary Spaces**

As the bitcoin blockchain grows, it adds new blocks to the chain. The concept of Non-Arbitrary Spaces (NAS) proposes to arrange these blocks in a non-arbitrary manner to create a usable ‘world’ for applications such as gaming.

The image below shows a proposed relationship between BITMAPs, NATs, NASs, and elements.

## Dependencies

The flowchart below illustrates the dependencies between this data structures

<figure><img src="/files/06I1yz6X6r1ceWyf7wuJ" alt=""><figcaption><p>Figure 1: Relationship between data structures</p></figcaption></figure>


---

# 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://nas-2.gitbook.io/nonarbitraryspaces/definitions.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.
