> For the complete documentation index, see [llms.txt](https://asigna.gitbook.io/asigna/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asigna.gitbook.io/asigna/bitcoin-multisig/technical-specifications.md).

# Technical Specifications

Our multisig addresses on Bitcoin leverage the Taproot Bitcoin Upgrade, enabling the use of Ordinals, BRC-20 tokens, and optimizing gas fees for efficient transactions.

For an in-depth look at the Taproot proposal, you can refer to the official documentation [here](https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki).

It’s important to note that every Taproot address requires an internal public key to be passed as a single spender, which is not inherently compatible with a multisig setup.

To overcome this, Asigna utilizes MuSig public key aggregation, which derives a unified public key from all owners' public keys. This effectively creates an “everyone agrees” branch, ensuring seamless multisig compatibility without introducing additional risks for multisig owners.


---

# 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://asigna.gitbook.io/asigna/bitcoin-multisig/technical-specifications.md?ask=<question>&goal=<endgoal>
```

`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.