Corné Plooy via Lightning-dev
writes:
> The only reasons I see for keeping the global/local distinction is that
> you might not want to gossip everything, either to keep the gossip data
> small, or for some privacy reasons. Apparently, that's all very
> theoretical so far, as current features don'
The only reasons I see for keeping the global/local distinction is that
you might not want to gossip everything, either to keep the gossip data
small, or for some privacy reasons. Apparently, that's all very
theoretical so far, as current features don't seem to need either.
Ideally you'd like to
Good morning,
I believe this is simply an argument about meanings of words; to me spontaneous
means that the payee does not generate a new secret to be sold as a valuable
good in exchange for money, using the mechanisms for routing on Lightning.
In any case, it would still be possible to perform
> OG AMP is inherently spontaneous in nature, therefore invoice might not
exist
> to put the feature on.
That is incorrect. One can use an invoice along with AMP as is, in order to
tag
a payment. As an example, I want to deposit to an exhcange, so I get an
invoice
from them. I note that the invoic
Pierre writes:
> Hi Rusty,
>
>>The feature masks are split into local features (which only
>>affect the protocol between these two nodes) and global features
>>(which can affect HTLCs and are thus also advertised to other
>>nodes).
>
> I don't think that definition
Hi Rusty,
>The feature masks are split into local features (which only
>affect the protocol between these two nodes) and global features
>(which can affect HTLCs and are thus also advertised to other
>nodes).
I don't think that definition makes a lot of sense. For
Good Morning Rusty,
OG AMP is inherently spontaneous in nature, therefore invoice might not exist
to put the feature on.
Thus it should be global feature.
Do we tie spontaneous payment to OG AMP or do we support one which is payable
by base AMP or normal singlepath?
Given that both `option_swi
Hi all,
I went through the wiki and made up option names (not yet
numbers, that comes next). I re-read our description of global vs local
bits:
The feature masks are split into local features (which only
affect the protocol between these two nodes) and global features
