Good morning list,
As my award-winning and supremely notable and
talked-about-by-the-man-on-the-street article "Cyclic Superhubs as Solution
Towards Reasonable Lightning Network Topography" points out, cycles are a good
way to organize the LN in order to allow easier accessibility to the
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
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
> It is a public key hash, yes. But what I refer to is that the
> payee-determined route section, which starts from an introduction point,
> protects the payee from being located by the payer, but how did the payer
> contact the payee in the first place anyway? If it was by IP or non-.onion
Thomas Steenholdt writes:
> Thanks for the explanation - This was exactly the the piece of the
> puzzle I was missing.
>
> I'd be happy to help clarify this in the BOLT10 specification, if that
> makes any type of sense? I can make a pull request for
Hi ZmnSCPxj,
Thank you so much - Exactly what I needed!
/Thomas
From: ZmnSCPxj
Sent: Sunday, March 18, 2018 8:48:57 PM
To: Thomas Steenholdt
Cc: lightning-dev@lists.linuxfoundation.org
Subject: Re: [Lightning-dev] High level fee