Coin Brief ENDE

BIP 460 merged as draft: cross-input signature aggregation for Taproot spends in witness v2

BIP 460, "CISA for Taproot Key Path Spends in SegWit v2", has been merged into the Bitcoin BIPs repository as a draft. The pull request by Fabian Jahr went in on 4 November at 03:33 UTC. The proposal is a consensus change, a soft fork, and requires BIPs 340, 341, 458 and 459.

It introduces a new witness version 2 that works like Taproot's key path, with cross-input signature aggregation added. Two schemes are supported. Half-aggregation is non-interactive and reduces n signatures from 64·n bytes to (n+1)·32 bytes. Full-aggregation reduces them to a constant 64 bytes but needs the signers to interact. Each aggregated input carries only its share of the aggregate signature data and an optional sighash byte; the last input of a group adds a marker byte, 0xbc for half-aggregation and 0xbd for full-aggregation. A transaction can hold at most one group of each kind.

Inputs can opt out by using a plain 64- or 65-byte BIP 341 signature. The text says this exists for protocols that need a specific signature to appear on chain, such as some adaptor-signature schemes, and it means wallets that do not aggregate can still use witness v2 outputs without new signing logic. The aggregation mode is committed to in the signature message, which protects opted-out inputs from being aggregated by third parties. Script path spends are not aggregated.

The authors list CoinJoin and PayJoin, consolidation and batching, and Lightning channel opens and splices as the main beneficiaries.

BIP 460 merged as draft: cross-input signature aggregation for Taproot spends in witness v2
BIP 460 merged as draft: cross-input signature aggregation for Taproot spends in witness v2 — Coin Brief

What it means

Merging a BIP is not activation; it gives the proposal a number and a reviewed text. What it sets out is a fee discount for any transaction with several inputs, largest for collaborative ones, which is why privacy tools are named first.