Bitcoin Forum
June 14, 2021, 04:00:52 AM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Transaction exchange process in Lightning Network  (Read 77 times)
user512
Newbie
*
Offline Offline

Activity: 12
Merit: 6


View Profile
May 31, 2019, 03:57:48 PM
 #1

Hello,
how is ensured that secret and new commitment transaction exchange take place at the same time? If for example Alice sends Bob the new commitment transaction only if he sends her a secret for penalization transaction activation, and she lies, it can end by balance freeze forever, because at now Alice has secret and Bob has nothing, so Bob can't send a transaction to blockchain (if he does it, Alice uses his secret to take all his money from the channel) and Alice does not do it because she wants Bob broke even if her money are freezed too.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1623643252
Hero Member
*
Offline Offline

Posts: 1623643252

View Profile Personal Message (Offline)

Ignore
1623643252
Reply with quote  #2

1623643252
Report to moderator
achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 2506
Merit: 3845


Just writing some code


View Profile WWW
June 01, 2019, 10:07:15 PM
 #2

If for example Alice sends Bob the new commitment transaction only if he sends her a secret for penalization transaction activation, and she lies
The secret is sent in response to the new commitment, not the other way around. The new commitment is committed to first before the previous commitment is revoked. Otherwise you run into this issue. There is nothing that prevents this except for the fact that the protocol specifies that commitments must be sent first. So compliant software will wait for the commitment to be sent before they send the secret.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!