Exploring Extended Relative Timelocks

Posted by pyth

Jul 16, 2025/09:27 UTC

The process of managing Bitcoin transactions involves a technique known as refreshing the relative lock. This method allows users to transfer their funds to a different wallet, where they can then reset the nLockTime value. A specific application that utilizes this mechanism is BitcoinKeeper. However, employing this strategy comes with certain challenges. Each time the timelock is refreshed or "rolled," it necessitates the creation of a new descriptor. The implications of this requirement are twofold. Firstly, there is an essential need to create a comprehensive backup of the new descriptor. This step is crucial for maintaining access to and control over the funds associated with that descriptor. Secondly, it becomes necessary to register and validate the updated policy on all signing devices involved in the transaction process. Without completing these steps, the integrity and security of the transaction could be compromised, highlighting the importance of thoroughness in managing these procedures.

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