|
June 03, 2019, 10:44:34 AM |
|
Hello, I see in Lightning Network some small issue which besides defends the transfer of big amount of BTC. I use the example with café. Have you noticed that in case of sending secret, two transactions are actually valid and two would pass? The third transaction from the front is invalidated by the exchange of the secret, but not the two most recent before the exchange of the secret. That is why the waitress will bring the third coffee only when the secret is exchanged for the second transaction (the customer might broadcast older transaction without penalty at now). The process is always one "paying" as if behind. But before that, there are two transactions - the two latest. In the exchange of the second transaction commitment, the third transaction is already signed and the waitress can broadcast it and have her coffee paid for, without waiting for a secret.
Can this small problem be solved by atomicity - namely, between signing a second commitment, exchanging secret from first commitment and serving a second coffee (these actions must be totally contemporary (atomic) for maximum safety and how?
I speak about big amount of BTC at the beginning because if you are transferring more bitcoins, then the receiver is paid in advance and that is not safety.
|