Cross-input signature aggregation (BIPs 458–460)
Three 2026 drafts that would let one transaction carry a single aggregated signature for many inputs: half-aggregation (BIP-458), DahLIAS full aggregation (BIP-459) and a SegWit v2 deployment (BIP-460).
The wiki's angle: signature aggregation is the rare soft-fork idea pitched mainly as a fee saving, which makes coinjoins and consolidations cheaper.[3][5]
Contents
The schemes
BIP-458 describes half-aggregation, a non-interactive way to combine many BIP-340 signatures into one aggregate about half their combined size[1]. BIP-459 describes full aggregation based on the DahLIAS interactive scheme, producing an aggregate the size of a single BIP-340 signature[2].
Deployment
BIP-460 proposes cross-input signature aggregation through a new witness version, v2, with Taproot-style key path spends; half-aggregation reduces n signatures from 64n bytes to (n+1)32 bytes, while full aggregation reduces them to 64 bytes but needs interaction[3]. The BIP says activation parameters are to be determined in a future update[3]. All three are Drafts in the BIP repository[4].
References
- primaryBIP 458, “Half-Aggregation of BIP 340 Signatures”, bitcoin/bips
- primaryBIP 459, “DahLIAS fully aggregated signatures for secp256k1”, bitcoin/bips
- primaryBIP 460, “CISA for Taproot Key Path Spends in SegWit v2”, bitcoin/bips
- primarybitcoin/bips repository [archived]
- secondaryBitcoin Optech Newsletter #430, 6 Nov 2026 — “Continued discussion of BIP54”, QSAVE, opt-in replay protection
Related in the wiki
Related articles


