Re: [Lightning-dev] [bitcoin-dev] eltoo: A Simplified update Mechanism for Lightning and Off-Chain Contracts

2018-06-19 Thread David A. Harding
On Tue, Jun 19, 2018 at 04:46:32PM +0200, Christian Decker wrote: > That is true, we can't prevent S_2 to make it into the blockchain, but > we can make sure it doesn't have any effect (aside from wasting some > fees), by simply binding S_3 to it immediately afterwards. Right, but I'm picking on

Re: [Lightning-dev] [bitcoin-dev] eltoo: A Simplified update Mechanism for Lightning and Off-Chain Contracts

2018-06-19 Thread Christian Decker
"David A. Harding" writes: > I finished a re-read of y'alls excellent paper describing Eltoo, and > there was something that confused me: > >> If the update transaction represents the last agreed upon state it can >> use relatively low fees being certain that it will not be replaced. > > I don't

Re: [Lightning-dev] [bitcoin-dev] eltoo: A Simplified update Mechanism for Lightning and Off-Chain Contracts

2018-06-19 Thread David A. Harding
Hi, I finished a re-read of y'alls excellent paper describing Eltoo, and there was something that confused me: > If the update transaction represents the last agreed upon state it can > use relatively low fees being certain that it will not be replaced. I don't understand why this is "certain"?