Check out posts actively getting replies and inspiring conversations.
Addressing remaining points on BIP 54
12 repliesBy Antoine Poinsot
bitcoin-dev
Involving Antoine Riard, Matt Corallo+3 others
Original post on December 30, 2025 15:59 UTC
Last reply on January 30, 2026 04:08 UTC
bitcoin-dev
BIP 54 debate resurfaces with critiques on coinbase transaction nLockTime optimization loss.
Jeremy Rubin suggests a new sparse Merkle tree to address 64-byte transaction limits.
Consensus emphasizes pragmatic solutions over major protocol changes for Bitcoin's stability.
Algorithm Agility for Bitcoin to maintain security in the face of quantum and classic breaks in the signature algorithms
1 replyBy Ethan Heilman
bitcoin-dev
Involving Erik Aronesty, Brandon Black+2 others
Original post on February 9, 2026 14:20 UTC
Last reply on February 10, 2026 23:13 UTC
bitcoin-dev
The proposal enhances Bitcoin's security against quantum computing and algorithm breaks.
It introduces a dual signature system with a primary and a secondary algorithm for emergencies.
The system includes infrastructure updates and uses BIP 360 for future cryptographic threats.
Bip54: add sequence, timestamp (and version) to GBT
By Sjors Provoost
bitcoin-dev
Involving Melvin Carvalho
Original post on February 9, 2026 19:37 UTC
Last reply on February 9, 2026 19:37 UTC
bitcoin-dev
BIP54 aims to standardize `nLockTime` and `nSequence` in the coinbase transaction to aid future compatibility.
It introduces `coinbase_locktime`, `coinbase_sequence`, and `coinbase_version` keys for better transaction guidelines.
Compliance with these changes ensures mining software is prepared for potential protocol adjustments without further updates.
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback