Digital Matter Theory
  • Introduction
    • Digital Matter Theory
    • Digital Elements
      • .element Registry
      • Example Element
    • Non-Arbitrary Tokens (NATs)
      • Hybrid Token Model
      • NAT Deployment Format
      • NAT Minting
      • NAT Token Transfer
    • NAT Use Cases
      • $NAT (Method 1) - Live
      • $BMT (Method 3)
    • UNAT Use Cases
      • $dmt-natcats
      • $dmt-nat
    • Supported Token Protocols
      • TAP Protocol
    • Resources
      • FAQ
      • Videos
      • Guides
        • $BMT Blockdrop Claim
        • How to convert your NAT deployment into a UNAT (Reinscription Guide)
      • $NAT Mint Process
      • Rendering a UNAT
Powered by GitBook
On this page
  • Transferring Tokens From token-mint Inscriptions
  • Token Transfer & Balance
  • UNAT Transfer
  1. Introduction
  2. Non-Arbitrary Tokens (NATs)

NAT Token Transfer

Token Mint -> Token Transfer

Transferring Tokens From token-mint Inscriptions

Transferring an NAT from a token-mint inscription is a single operation. Use the following JSON data to inscribe a block associated with the ticker name.

{
"p": "tap",
"op": "token-transfer",
"tick": "dmt-<name>",
"amt": "#"
}
Required
Optional
Description

p

Protocol: TAP

op

Operation: Event (dmt-deploy, token-mint, token-transfer)

tick

Ticker: Matches the ticker in the token-mint inscription

amt

Amount: Chose an amount of NATs to transfer. ⚠️ Can Not Exceed Account Balance

Token Transfer & Balance

Trac Systems is indexing all inscriptions from The TAP ecosystem from end to end including transfer inscriptions.

UNAT Transfer

When transferring a UNAT, you are only transferring a mint inscription. It does NOT transfer the fungible tokens with it. The non-fungible UNAT and the fungible NATs are separate and independent assets.

The non-fungible UNAT and the fungible NATs are separate and independent assets.

PreviousNAT MintingNextNAT Use Cases

Last updated 1 year ago