# Why is it best practice to store a single Ordinal Inscriptions per Taproot address?

It is best practice to store a single Ordinal Inscription per Taproot address for several reasons:

1. Security: Storing a single Ordinal Inscription per address helps to ensure the security of the asset. If multiple Ordinal Inscriptions were stored on a single address, then the security of all the assets would be dependent on the security of that single address. By using a separate address for each Ordinal Inscription, the risk of loss or theft of all assets is reduced.
2. Privacy: By using a separate address for each Ordinal Inscription, the privacy of the asset is enhanced. If multiple assets were stored on a single address, then any transaction involving one asset would also reveal the presence of the other assets on the same address. By using separate addresses, the privacy of each asset is maintained.
3. Scalability: Storing a single Ordinal Inscription per address also improves the scalability of the Bitcoin network. Each transaction on the Bitcoin network involves a certain amount of data that must be verified and stored by all nodes on the network. By using separate addresses, the amount of data required to store and verify transactions is reduced, which improves the overall efficiency and scalability of the network.
4. Flexibility: Storing a single Ordinal Inscription per address also provides greater flexibility for asset management. If an asset needs to be transferred or managed separately from other assets, it can be easily moved to a separate address without affecting the other assets.

In summary, storing a single Ordinal Inscription per Taproot address enhances the security, privacy, scalability, and flexibility of digital asset management on the Bitcoin network.

It is also possible to store several ordinals in a single Taproot address. Leather also supports that.


---

# Agent Instructions: 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:

```
GET https://leather.gitbook.io/guides/bitcoin/why-is-it-best-practice-to-store-a-single-ordinal-inscriptions-per-taproot-address.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.