> 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-minting.md).

# NAT Minting

## Minting Tokens From dmt-deploy Inscriptions

Minting a NAT from a deploy inscription is a single operation. Use the following JSON data to inscribe a block associated with the ticker name. 

#### Step 1. Token Mint

Use the following JSON to mint your NAT using any text inscription platform. Locate the inscription ID of the `token-deploy` inscription and add that to the "dep" between the quotes, always remove `<>` the greater-than and less-than sign when replacing the content within the quotes. .&#x20;

```json
{
"p": "tap",
"op": "dmt-mint",
"dep": "<inscriptionID>",
"tick": "<name>",
"blk": "#"
}
```

<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 (dmt-deploy, <strong>dmt-mint</strong>, token-transfer)</td></tr><tr><td>dep</td><td>true</td><td>false</td><td>Deploy: Reference to the <code>dmt-deploy</code> inscriptionID. Note: "dep" will be optional from a block height TBA)</td></tr><tr><td>tick</td><td>true</td><td>false</td><td>Ticker: Matches the ticker in the <code>dmt-deploy</code> inscription</td></tr><tr><td>blk</td><td>true</td><td>false</td><td>Block: Inscribe a block number of your choosing. ⚠️ <strong>First is first.</strong> </td></tr></tbody></table>

## Hybrid Token Minting

When minting hybrid NATs, you are owning blocks that represent the `dmt-deploy` inscription. When you own a block, you own all the [fungible tokens](/digital-matter-theory/introduction/non-arbitrary-tokens-nats/hybrid-token-model.md) of the pattern set from the `dmt-deploy` inscription. When minting a UNAT from a deployment with "id" as part of the JSON, your mint inscription represents a ownership of unique content generated from the "id" inscription ID. In addition to the unique content from minting a UNAT, you also own the fungible NAT from the same `dmt-deploy`.