lightning-dev

Anchor transaction for no expiration channels without segwit

Anchor transaction for no expiration channels without segwit

Original Postby Tier Nolan

Posted on: February 6, 2017 10:14 UTC

The context describes a step-by-step protocol for setting up a channel between Alice and Bob.

The protocol includes two transactions, TX1 and TX2. Alice creates TX1 and signs it, then sends it to Bob. Bob signs TX1 and sends the tx hash back to Alice. Alice creates TX2, signs it, and sends it to Bob. Bob signs TX2 and sends it back to Alice. If any party refuses to complete a step, there are safe aborts built into the protocol. If the timeout expires before all steps are completed, Alice can try to double spend her input into TX1 or spend her output from TX1. After the timeout has expired, Alice could broadcast two transactions: TX2 to close the channel paying Alice 100%, and a transaction to spend TX1/1 (i.e., Alice + Alice secret). Bob would be broadcasting his transaction to claim TX1/1 at around the same time. Adding an extra timeout with a later expiry to TX1/0 means that Alice cannot broadcast TX2 until Bob has a chance to claim his output.

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