Christian Decker

> I think you can safely use values > 255, I don't expect us to finalize that amount of features in the foreseeable future :D > Or simply reserve bits...

The rationale behind not making `description` mandatory is that we wanted to either have `description` or `description_hash` be set, but not both.

> As an example, this can be a very small stand alone document that describes the motivation and what changes it requires (just a new TLV). That can then be...

> Maybe I missed something, but what's the point of mentioning non-final feature bits in the title @rustyrussell ? It's there so we can detect these clashes early on, before...

Agreed with @TheBlueMatt: the gossip is intended as a best effort system, and striving for completeness or timeliness is likely a far deeper Rabbit Hole than we're willing to tackle...

Adding this to the "someday" milestone since we need to first figure out a number of things. For once we need to agree on a format to specify recurring payment...

Notice that the only way we currently can perform atomic cross-channel is through HTLCs. Since the swap from one channel to another needs to be atomic we likely must actually...

I think we have this partially covered with the `error` messages in BOLT 01, which allows us to close a channel and report a human readable error description. What is...

https://github.com/lightningnetwork/lightning-rfc/pull/593 has two test vectors, one for the normal onion and one for the onion error :wink:

We should probably follow the existing guidelines for responsible disclosures such as the ones outlined here: https://www.hackerone.com/blog/Vulnerability-Disclosure-Policy-Basics-5-Critical-Components In addition we'll need to have some guidelines on how to triage the...