taproot-multisig

Coordinate Bitcoin Taproot multisig by having signers register internal pubkeys, sign sighashes with BIP-340 Schnorr, verify co-signatures, and produce a full workflow JSON. This skill automates that M-of-N coordination process for autonomous agents.

BIP-340 Schnorr signing produces signatures used to sign BIP-341 sighashes in Taproot multisig. The skill enforces internal-vs-tweaked key safety and verifies co-signatures to ensure secure M-of-N transaction coordination.

Share x-only Taproot pubkeys using the get-pubkey subcommand. Unlocked wallets derive the internalPubKey, which signers register to initiate the M-of-N multisig coordination workflow.

Yes, this Taproot multisig workflow applies to both mainnet and test setups. Autonomous agents can coordinate key registration, Schnorr signing, and co-signer verification across either environment.

Yes, verifying co-signatures and validating workflow steps are core requirements. The skill uses the verify-cosig subcommand to check BIP-340 Schnorr signatures from co-signers before producing the final workflow JSON.

Coordination requires unlocked wallets to derive internalPubKey and depends on BIP-340 Schnorr compliance. The skill enforces internal-vs-tweaked key safety, meaning signers must strictly follow the structured JSON workflow to avoid invalid signature states.