> For the complete documentation index, see [llms.txt](https://tna-btc.gitbook.io/tna-whitepaper-2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tna-btc.gitbook.io/tna-whitepaper-2/ecosystem/tna-faq.md). # TNA FAQ #### Why are TNA names sometimes called Tapnames? TNA names are sometimes termed 'Tapnames' as they are unique, programmable assets initially utilizing the Taproot Assets protocol. Over time, TNA evolves to incorporate other asset protocols, while keeping Taproot at the foundational core of its design. #### Are TNA names exclusively .btc names? Initially, TNA names are confined to .btc names. The introduction of other name formats could be considered in the future, based on community voting and consensus #### What makes TNA names valuable? * Bitcoin Mainnet Assets: Being native assets of the Bitcoin mainnet adds intrinsic value * Uniqueness and Rarity: The Sparse Merkle Tree (SMT) structure used in Taproot Assets ensures efficient validation of uniqueness, contributing to the rarity of TNA names * Asset Upgradability: Owners have complete control over the customization and upgrading of their TNA names, including the ability to issue sub-names and embed various features, such as images or complex business logic * Built-in Programmability: TNA names are distinguished by their built-in programmability, enabling basic functionalities such as dynamic ownership, permission control, certain financial attributes, and identity management without relying on external smart contracts #### How are TNA names utilized? Below are a few examples of how TNA names can be used: * Social Identifiers: They can function as unique identifiers on social media platforms * Asset Issuance Rights: Owners have the prerogative to issue subsidiary names with customizable attributes * Readable Accounts: Integration with wallets and platforms will make TNA names useful for easy transfers and effective asset management * Decentralized IDs (DIDs): Offering diverse use cases in social networks, gaming, and more #### Where can I view my TNA names? Our names are visible within TNA's network. As TNA continues to broaden its integration with a variety of wallets and decentralized applications (dApps), our names will gradually become accessible on multiple networks. #### Why opt for Taproot Assets Protocol (TAP) for Bitcoin names? TNA names, being the first .btc names built on the Taproot Assets protocol, offer an efficient and scalable naming solution: * TAP's Sparse Merkle Tree (SMT) structure guarantees name uniqueness directly at registration, reducing data disputes and complexity * Managing subsidiary names with TNA through SMT is streamlined and economical, avoiding intricate protocol modifications or additional transactions * SMTs enable certain level of programmability tailored for naming services, including functions related to identity management, permission control, etc. #### How do TNA names differ from other crypto names such as ENS names? * TNA names, designed for Bitcoin's ecosystem, are considered 'assets' and cater to Bitcoin-specific utilities, unlike other crypto names like ENS names, which are based on smart contracts * Core features associated with names can be programmed directly into the assets, eliminating the need for external smart contracts * The transaction structure of Bitcoin, which is based on the UTXO model rather than accounts, inherently provides better privacy protection than Ethereum and other networks --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://tna-btc.gitbook.io/tna-whitepaper-2/ecosystem/tna-faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.