Re: [Lightning-dev] AMP via HD, BN+SS, and TR

2018-03-20 Thread ZmnSCPxj via Lightning-dev
Good morning list, It is possible to mean atomic in multiple meanings: 1. The payee is completely unable to claim any partial payments until all partial payments arrive at the payee. 2. The payee is not incentivized to claim partial payments until all partial payments arrive at the payee.

Re: [Lightning-dev] AMP via HD, BN+SS, and TR

2018-03-19 Thread ZmnSCPxj via Lightning-dev
Good morning Andrew, > Hi ZmnSCPxj, > > Yep, I'm pretty sure this works the way you describe -- essentially replace > > the hash challenges with adaptor signatures which are reblinded at each layer. Thank you very much your confirmation. > For example, with adaptor signatures + Graftroot

Re: [Lightning-dev] AMP via HD, BN+SS, and TR

2018-03-19 Thread Andrew Poelstra
Hi ZmnSCPxj, Yep, I'm pretty sure this works the way you describe -- essentially replace the hash challenges with adaptor signatures which are reblinded at each layer. Because adaptor signatures can make arbitrary sets of signatures atomic (and don't require any precommitments in the

[Lightning-dev] AMP via HD, BN+SS, and TR

2018-03-18 Thread ZmnSCPxj via Lightning-dev
Good morning list, I sketch here the idea, of making atomic multipath payment (AMP), with the properties: 1. Has a proof-of-payment. 2. Multipath decorrelation. Note: I am not a mathematician. Thus, it is likely, that there is a mistake here, and we cannot make this work. First, we look