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_switch_ephkey` and `option_og_amp` require understanding extended onion packet types, would it not be better to merge them into `option_extra_onion_packet_types`? Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, November 13, 2018 7:49 AM, Rusty Russell <[email protected]> wrote: > 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 > (which can affect HTLCs and are thus also advertised to other > nodes). > > You might want to promote your local bit to a global bit so you can > advertize them (wumbo?)? But if it's expected that every node will > eventually support a bit, then it should probably stay local. > > Please edit your bits as appropriate, so I can assign bit numbers soon: > > https://github.com/lightningnetwork/lightning-rfc/wiki/Lightning-Specification-1.1-Proposal-States > > Thanks! > Rusty. > > Lightning-dev mailing list > [email protected] > https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev _______________________________________________ Lightning-dev mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
