TNA Whitepaper
  • - TNA Intro -
    • Overview
    • Decentralized Names for Bitcoin
    • Taproot and Lightning Network
    • Supporting Multiple Asset Types
    • Omni-Chain Name Assets
  • - Developer Guide -
    • Technical Details
      • Tech Features
      • Key Components
    • Developer APIs
      • Resolution
        • Get Name Info
        • Get Names from an Address
        • Mint a Name
        • Burn a Name
        • Transfer a Name
      • Data Availability
        • Get Tree Status
        • Get Proof
        • Verify Proof
        • Add Block Txs
        • Get Block Height
        • Get Block Hash
        • Get Block Txids
  • - TNA Core -
    • TNA Core Overview
    • Yellowpaper: TNA Core - a Bitcoin DA framework
  • - Ecosystem -
    • Tokenomics
    • Roadmap
    • TNA FAQ
  • - Social Links -
    • Twitter
    • Telegram
    • Medium
Powered by GitBook
On this page
  • Programmability
  • Asset Connectivity
  1. - Developer Guide -
  2. Technical Details

Tech Features

Programmability

TNA is built on the Taproot protocol, allowing for programming of applications and business logic rules using Taproot addresses and transaction scripts. For example, in the issuance of Taproot Assets, the provided script operation codes can be used to encode and program aspects such as the total token supply and issuance time, which are then written into UTXOs as spending conditions. To issue a token like "ABC", the asset issuer creates a multi-signature address (addr_msigner) from a wallet address (addr_issuer). This address (addr_msigner) can then be used to distribute ABC tokens to various addresses, such as sending 1,000 tokens to user addresses, 1,000 tokens for community airdrops, and so on. The addresses receiving tokens are typically on the Lightning Network, enabling efficient, high-frequency, and low-cost interaction channels between the asset issuer's address and these recipient addresses.

Asset Connectivity

TNA names - assets issued on the TNA protocol share common attributes with other assets on Bitcoin and the Lightning Network. However, they introduce a significant and distinctive capability: the capacity to connect diverse asset types and create logical and application-level interconnections. For example, TNA names can be mapped to Lightning Network channel addresses, enabling user-friendly payments and settlements; to the address of a BRC20 asset holder, combined with programmable signature logic, to facilitate swift transactions; to a Web2 payment URL to allow direct transaction sending and payment; to IPFS associating on-chain assets with off-chain data.

TNA names can also be mapped to each other, enabling multi-level asset associations and exchanges. For instance, mapping Tapname1 to Lightning Network address 1, Tapname2 to address 2, and Tapname3 to the deposit address of DEX1 on a Layer 2 Network creates mappings from Tapname1 to Tapname2 and from Tapname2 to Tapname3. This first allows cross-channel transfer payments between channels 1 and 2 on the Lightning Network. Then, after closing channel 2, assets can be transferred and added as liquidity to DEX1 to earn transaction fees and liquidity rewards.

PreviousTechnical DetailsNextKey Components

Last updated 11 months ago