In this section, we will prepare the DNS and the content of the transferable record to be issued.
Similar to binding the document store to a domain name, you will have to bind the identity of the token registry to a domain name.
To do that simply create a
TXT record on your domain with the following entry:
You will need to replace the token registry address
0x8431012Bc040942B59e3C5bf428221eab0b2f723 with the address you've got from the previous step.
If you like to use our sandbox DNS for the purpose of the exercise, you may instead run the following command, following the instructions from earlier:
If you like more detailed setup instructions, you may refer to the documentation for configuring DNS.
Take note of the domain you are inserting the records on, you will need this later
Similar to creating a verifiable document, you will need to create a raw JSON file with the content of the transferable record first.
Create a file
sample.json in a folder
Remember to replace the
tokenRegistry value with your token registry smart contract address from previous section and
location with the domain you are issuing this document from.
Notice the difference between a transferable record and a verifiable document is the use of
tokenRegistry instead of
documentStore in declaring the smart contract address.
For transferable record, you may not batch process it with other documents. Your directory
raw-documentsmay only contain one file.
With the raw transferable document, you are not ready to issue the document. Simple run the following command to wrap the
sample.json and output it in another directory
You will see a familiar output with the merkle root of the transferable record after running the command:
Keep this value, the merkle root, for later steps.