Exploring Extended Relative Timelocks

Posted by rafael

Jul 21, 2025/13:45 UTC

Implementing a soft fork involves changes that are backward compatible with older versions of the blockchain protocol. In this scenario, the proposed soft fork would introduce a flag that modifies the timelock parameter to be 8 times longer than its current setting. This alteration means that transactions incorporating this new flag would require a significantly extended period before they could be executed, compared to transactions under the existing rules.

A critical risk associated with not moving coins within the original 1x timelock period is highlighted. Since older nodes in the network, which have not updated to recognize the new flag, would continue to operate under the legacy rules, they might inadvertently accept and propagate transactions that attempt to spend the coins before the extended timelock expires. Consequently, there exists a possibility for miners who have not upgraded to the new protocol version to include these prematurely spent transactions in a block, thus undermining the security intended by the extended timelock.

This situation underscores the inherent challenges and potential vulnerabilities associated with implementing soft forks on blockchain networks. It serves as a reminder of the delicate balance between advancing technological improvements and ensuring network security and consensus among participants.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiBitcoin Transcripts Review
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project?

Give Feedback