> 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/zcash-multisig/technical-specifications.md). # Technical Specifications Our multisig implementation on Zcash is designed to support both **shielded** and **transparent** transaction flows, taking into account the unique cryptographic architecture of the Zcash protocol. #### **Transparent Multisig** Transparent Zcash addresses follow the standard Bitcoin-style UTXO scripting model, enabling familiar M-of-N multisig via P2SH and legacy scripts. This provides full compatibility with existing wallets and infrastructure. #### **Shielded Multisig (Coming soon)** Shielded pools (Sapling and Orchard) do not support on-chain scripts or native M-of-N spending logic. To enable multisig, we use **FROST**, Zcash’s threshold Schnorr signature scheme. FROST allows multiple key holders to collaboratively produce a **single valid shielded spend signature** without reconstructing the spend key or revealing that multisig was used. The resulting signature is indistinguishable from a normal shielded spend, preserving privacy and protocol compatibility. --- # 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/zcash-multisig/technical-specifications.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.