Bitcoin merges three BIPs aiming to cut transaction fees up to 27%

Bitcoin’s core developers merged three new Bitcoin Improvement Proposals—BIP458, BIP459 and BIP460—into the project’s proposal repository between November 2 and November 4, 2026. The drafts introduce signature aggregation mechanisms designed to shrink transaction size and, consequently, lower fees for certain payment patterns. According to CryptoSlate, the proposals could reduce fees by up to 27 % in consolidation scenarios, though full activation will depend on wallet upgrades and network consensus.

How the aggregation proposals work

BIP458 and BIP459 outline two aggregation modes. Half‑aggregation combines independently generated signatures, turning n × 64‑byte signatures into 32 × (n+1) bytes, while full aggregation requires coordinated signing and produces a single 64‑byte signature for the entire group. For a ten‑input, ten‑output transaction, half‑aggregation would shrink the virtual size from 1,016 vB to 944 vB (a 7.1 % fee drop), whereas full aggregation would bring it down to 872 vB (a 14.2 % drop). In a larger consolidation example—100 inputs merged into one output—the fee reduction could reach 13.6 % with half‑aggregation and 27.3 % with full aggregation.

Implementation hurdles and activation

The proposals leave key activation parameters unspecified. BIP460, which proposes a new witness version (currently v2), requires coordination with other ongoing upgrades. Wallets must add support for a new output type; existing Taproot outputs will not automatically benefit because aggregation is limited to direct signature‑based or key‑path spends. Script‑path spends cannot join aggregation groups, and eligible inputs may opt out. Full aggregation also demands a stateful two‑round signing protocol, raising security concerns around nonce reuse that could expose private keys. Consequently, hardware‑wallet and air‑gapped implementations will need careful design.

What to watch next

The Bitcoin community will need to define activation thresholds and coordinate a network‑wide rollout before the fee‑saving benefits materialize. Observers should monitor upcoming developer meetings for decisions on witness version upgrades and any consensus‑layer signaling mechanisms. Additionally, wallet developers are expected to release early‑stage support for the new output type, which will be a prerequisite for users to experience lower fees.