[BOLT Draft] Onion Routing Spec

Aug 5 - Aug 5, 2016

  • A proposal was made to combine the "header" and "per-hop payload" into a single 40-byte field since they are not meaningfully distinct for lightning.

However, it was suggested that ephemeral key and mac make sense as a header, but a different next hop address format could be used for different networks. An explicit network byte makes sense since multiple networks can be eventually supported. A flag for the terminal node is needed anyway. The author proposed some terminology changes such as using HTLC-hash and HTLC-preimage instead of r-hash.An alternative approach to replay avoidance using privkeys with point addition scheme was suggested which no longer makes having two HTLCs with the same pubkey an issue. However, it is not clear how one can switch to priv/pub key-based HTLC's without modifying Bitcoin Script.

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