> 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/tna-intro/supporting-multiple-asset-types.md). # Supporting Multiple Asset Types While utilizing the Taproot Assets protocol, TNA's naming standard is designed to accommodate a diverse range of asset types within the Bitcoin ecosystem, including but not limited to RGB, BRC20, ERC721, and more. Unlike traditional naming systems that are restricted to specific asset types, TNA embraces the versatility of blockchain assets and aims to leverage the unique strengths of each type to enrich its naming capabilities. TNA can harness the programmability offered by asset types like RGB and ERC721, enabling dynamic functionalities and interactions within the naming system. This programmability allows for the creation of unique and versatile naming solutions that extend beyond simple address mappings. Moreover, TNA recognizes the importance of Bitcoin nativeness and the widespread adoption of asset types like BRC20 and ARC20 within the Bitcoin ecosystem. By incorporating support for these native Bitcoin assets, TNA ensures compatibility with existing infrastructure and maximizes the utility of its naming standard. The overarching goal of TNA is to serve as a comprehensive framework that interconnects various asset types, enabling seamless communication and interoperability across the Bitcoin network. By leveraging the strengths of each asset type, TNA aims to create a robust and versatile naming system that can cater to the diverse needs of users and applications within the Bitcoin ecosystem. Below, we present an example illustrating how a TNA name can be linked to a BRC-20 token: * **Target Field Association:** The Tapname's 'target' field is designated to store the transaction ID or hash of the BRC-20 token minting. This creates a direct link between the Tapname and the BRC-20 identifier, allowing for a one-to-one mapping that can be verified across the network. * **SMT for Secure Verification:** TNA employs a Taproot SMT to efficiently and securely record the above associations, enabling transparent and reliable verification processes. --- # 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/tna-intro/supporting-multiple-asset-types.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.