> For the complete documentation index, see [llms.txt](https://digital-matter-theory.gitbook.io/digital-matter-theory/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/non-arbitrary-tokens-nats/nat-deployment-format.md).

# NAT Deployment Format

## Creating Your Own Non-Arbitrary Token Hybrid

Deploying a NAT is a simple JSON inscription that references an `.element` inscription that you want to use for the foundation of your NAT. 

#### Step 1. Token Deploy

Use  the following JSON to deploy your NAT using any text inscription platform. Locate the inscription ID of the element

{% hint style="warning" %}
The first deployment of a ticker is the only one that has claim to the ticker. Tickers are not case sensitive (DOGE = doge). 
{% endhint %}

<pre class="language-json"><code class="lang-json">{
"p": "tap",
<strong>"op": "dmt-deploy",
</strong>"elem": "&#x3C;inscriptionID>",
"tick": "&#x3C;name>",
"prj": "&#x3C;0.bitmap inscriptionID>",
"dim": "h | v | d | a",
"dt": "h | n | x | s | b",
"id": "&#x3C;content inscriptionID>"
}
</code></pre>

<table data-full-width="true"><thead><tr><th width="115"></th><th width="110" data-type="checkbox">Required</th><th width="105" data-type="checkbox">Optional</th><th>Description</th></tr></thead><tbody><tr><td>p</td><td>true</td><td>false</td><td>Protocol: TAP</td></tr><tr><td>op</td><td>true</td><td>false</td><td>Operation: Event (<strong>dmt-deploy</strong>, token-mint, token-transfer)</td></tr><tr><td>elem</td><td>true</td><td>false</td><td>Element: Reference to the <code>.element</code> inscriptionID</td></tr><tr><td>tick</td><td>true</td><td>false</td><td>Ticker: 3 and 5 to 32 (UTF16)</td></tr><tr><td>prj</td><td>false</td><td>true</td><td>Project: Reference to existing project's (i.e. <code>0.bitmap</code>) inscriptionID</td></tr><tr><td>dim</td><td>false</td><td>true</td><td>Dimension: Only required if you're recognizing a pattern in a given field. (horizontal, vertical, diagonal, add) 'add' represents the sum of 'h', 'v', and 'd', counts of the given pattern.</td></tr><tr><td>dt</td><td>false</td><td>true</td><td>Data Types: "h" hex, "n" numeric, "x" unix time, "s" string, "b" boolean. If the "dt" field is left out, the data type set within the block data is used by default. <br><br>⚠️ If the element you choose has a pattern, "dt" in your deploy inscription is required. ⚠️</td></tr><tr><td>id</td><td>false</td><td>true</td><td>ID: this is the inscription id of your UNAT content. (generative script art, 3d model, app)</td></tr></tbody></table>

***

#### Step 2.  Ready for Mint

Deployment inscriptions represent the start of your NAT. Once inscribed, there are several methods for you to create a project around your NAT. Please refer to [NAT use cases](/digital-matter-theory/introduction/nat-use-cases.md) for an in depth look at some of the ways Minting your token can occur.  When you're ready to Mint head over to [NAT Minting](/digital-matter-theory/introduction/non-arbitrary-tokens-nats/nat-minting.md) to see how. <br>