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
  1. - Developer Guide -
  2. Technical Details

Key Components

TNA consists of the key components below:

  • Naming Registry: The Naming Registry functions as the database where human-readable names are linked to their corresponding machine-readable identifiers. It is in charge of overseeing the entire lifecycle of these names, which includes registering new names, renewing existing ones, and managing the transfer of their ownership.

  • Resolver System: A resolver in TNA translates the registered human-readable names into their corresponding machine-readable addresses. It is crucial for the actual operational use of the names registered in the naming registry.

  • Ownership Management: This component would allow users to claim, update, and transfer the ownership of names. It could involve integration with wallets or other forms of digital identity to ensure secure and straightforward management of these resources.

  • Self-executing Program: To automate and enforce the rules of the naming system, TNA would implement self-executing programs similar to smart contracts. These would handle the logic for registering names, resolving queries, and managing ownership, among other functions.

  • User Interface (UI): For user accessibility, TNA would introduce a user-friendly interface, allowing users to easily register and manage their names.

  • Indexer: A tool to analyze, track, and index data related to TNA names

  • Reverse Resolution Capability: This feature would allow looking up the human-readable name associated with a given machine-readable identifier, enhancing the service's usability and applications.

  • APIs for Integration: APIs will be provided for developers and third-party services to integrate TNA functionalities into their applications.

PreviousTech FeaturesNextDeveloper APIs

Last updated 11 months ago