> 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/resources/guides/how-to-convert-your-nat-deployment-into-a-unat-reinscription-guide.md).
# How to convert your NAT deployment into a UNAT (Reinscription Guide)
If you have already deployed a Non-Arbitrary Token and you want to attach content such as art for every mint inscription that already exists, you're in luck. The following guide will show you how to do this in just 3 simple steps.
A typical deployment of an NAT looks like the following:
```json
{
"p": "tap",
"op": "dmt-deploy",
"elem": "63b5bd2e28c043c4812981718e65d202ab8f68c0f6a1834d9ebea49d8fac7e62i0",
"tick": "nat",
"dt": "n"
}
```
A UNAT deployment looks like this:
```json
{
"p": "tap",
"op": "dmt-deploy",
"elem": "63b5bd2e28c043c4812981718e65d202ab8f68c0f6a1834d9ebea49d8fac7e62i0",
"tick": "nat",
"dt": "n",
"id": "61756c3e2dbcfbdb889f7176014e583e94800721a7379a616ec2c031563a5000i0"
}
```
The only thing that's missing from the original inscription is the following:
```json
"id": "61756c3e2dbcfbdb889f7176014e583e94800721a7379a616ec2c031563a5000i0"
```
To add this line into the deployment JSON, you need to [reinscribe](https://github.com/ordinals/ord/discussions/2200) on top of your original deployment inscription with a new JSON structure that includes the "id" attribute within the JSON.
## Step 1 - Inscribe your generative art
Visit [Mscribe.io](https://mscribe.io/inscribe) or any other text inscription site and inscribe your script as text.
## Step 2 - Prepare your JSON for reinscription
Grab the inscription ID of your art script from step 1 and add that into a new JSON structure that you'll use to reinscribe your original deployment.
```json
"id": "61756c3e2dbcfbdb889f7176014e583e94800721a7379a616ec2c031563a5000i0"
```
Your reinscription JSON should look like this:
```json5
{
"p": "tap",
"op": "dmt-deploy",
"elem": "63b5bd2e28c043c4812981718e65d202ab8f68c0f6a1834d9ebea49d8fac7e62i0",
"tick": "nat",
"dt": "n",
"id": "61756c3e2dbcfbdb889f7176014e583e94800721a7379a616ec2c031563a5000i0"
}
```
{% hint style="warning" %}
Do not forget the extra " , " added to the 2nd to last line of your JSON, otherwise the JSON is not valid.
{% endhint %}
## Step 3 - Reinscribe your new JSON deployment
To complete the process, you'll need to reinscribe your old JSON deployment with the updated JSON that includes the "id" attribute. This is a 2 transaction process where you'll pay the inscription fee to process a reinscription. The 2nd part is where you'll send the original deployment inscription to the address provided by Chisel.xyz.
Visit [Chisel.xyz](https://chisel.xyz/) and follow the diagram below to reinscribe your deployment
You'll be taken to the payments page where you can use Unisat or Xverse wallet to pay the reinscription fee.
{% hint style="danger" %}
Make sure your destination address is correct or you may lose your original deployment inscription.
{% endhint %}
The final step to reinscribing after the first transaction clears is to send the original deployment inscription to the address provided by Chisel.xyz.
## Successful reinscription
A successful reinscription looks like the following:
{% embed url="" %}
To see the above, search for your inscription ID of your original deployment on [Ordinals.com](https://ordinals.com/) and click on Sat link