delvingbitcoin

Contract-level Relative Timelocks

Contract-level Relative Timelocks

Original Postby instagibbs

Posted on: January 2, 2025 19:30 UTC

John Law has incorporated two distinct relative timelocks into his payment channel constructions, as detailed in his work available on GitHub.

These timelocks, utilized via separate unspent transaction outputs (UTXOs), are crucial for the operation and security of the payment channels. The use of TXID stability is highlighted as a significant feature within this system.

The mechanism involving these timelocks creates dual "lanes" for managing timeouts: one specifically designed for the revocation of commitment transactions and the other for handling Hash Time-Locked Contracts (HTLCs), possibly also related to revocation processes. This structure ensures that once the conditions of both relative timelocks have been met, HTLC-payment transactions can proceed without the risk of one timelock resetting the duration of the other. An interesting aspect of this configuration is the designation of one output as a dust output, which serves no purpose other than to facilitate control within the system.

This method represents a relatively straightforward example of employing txid stability to enhance the functionality and reliability of payment channels, showcasing an innovative approach to managing transactions and contractual obligations within such networks.

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