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