Posted by Nicolas Dorier
Feb 7, 2017/02:39 UTC
The discussion revolves around a proposal to create a time-locked transaction. The proposed solution is for TX2 to be nTimelocked after the bounty's expiration. If Alice sees Bob not signing it, she can reclaim the bounty fast. If Bob signs it, Alice cannot broadcast it immediately. Nicolas Dorier suggests that there is no need for a second timeout. TX2 would be signed by Bob only when he could get back the second output of TX1. However, Alice must have a fully-signed version of TX2 before the timeout finishes. If she doesn't, Bob can reclaim TX1/1 once the timeout expires and refuse to sign TX2. Alice needs a signed version of TX2 to broadcast it and immediately close the channel (claiming TX1/0). Once accepted, she can then claim TX1/1. Overall, the proposal aims to create a secure and efficient time-locked transaction system.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback