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
  • TAP Protocol
  • Attributes of an .element
  1. Introduction
  2. Supported Token Protocols

TAP Protocol

TAP is an extendible OrdFi-enabling protocol that includes - but is not limited to - the TAP token standard.

PreviousSupported Token ProtocolsNextResources

Last updated 1 year ago

TAP Protocol

In collaboration with Trac Systems the TAP protocol is the first protocol recognizing NATs. TAP will receive an extension that formally recognizes details described in this document. To learn more about TAP, visit their github .

Parameters
TAP
NAT
TAP New Features

Allowed ticker lengths

3 and 5 to 32 (UTF16)

3 and 5 to 32 (UTF16)

No Change

Protocol

tap

tap

No Change

Deploy op

token-deploy

dmt-deploy

NEW

Mint op

token-mint

dmt-mint

NEW

Transfer op

token-transfer

token-transfer

No Change

This newly added functionality to the TAP ecosystem allows Trac Systems to index NATs and formally recognizes the expansionary supply nature of NATs.

Attributes of an .element

When an .element is inscribed, attributes of the data set that represents that element can be leveraged by the deployer

here