lightning-dev

Protocol for multiple in-flight updates.

Protocol for multiple in-flight updates.

Original Postby Joseph Poon

Posted on: February 3, 2016 05:01 UTC

In a message thread from February 3, 2016, Rusty Russell discussed the use of a signature to cover an HTLC ID and how it pertains to request IDs.

They concluded that it is more like a request "staging" ID and that two IDs sent in the commitment message allow for simultaneous action on accept/reject/etc. It's important to note that all messages sent must be in order, and if the replyer skips the requester's Add Requests when replying, the skipped are assumed to be request rejections (or an outright channel closeout) since it should never happen. This is to enforce accept/reject order as we need to know which modifications are included in the signature/transaction and not have that change after-the-fact.

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