lnrpc: receive custom message

This commit is contained in:
Joost Jager
2021-05-31 12:06:48 +02:00
parent ae959b16ae
commit ade50d0b2c
16 changed files with 4406 additions and 3836 deletions

View File

@@ -205,7 +205,23 @@ If you use a strange system or changed group membership of the group running LND
you may want to check your system to see if it introduces additional risk for
you.
## Safety
## Custom peer messages
Lightning nodes have a connection to each of their peers for exchanging
messages. In regular operation, these messages coordinate processes such as
channel opening and payment forwarding.
The lightning spec however also defines a custom range (>= 32768) for
experimental and application-specific peer messages.
With this release, [custom peer message
exchange](https://github.com/lightningnetwork/lnd/pull/5346) is added to open up
a range of new possibilities. Custom peer messages allow the lightning protocol
with its transport mechanisms (including tor) and public key authentication to
be leveraged for application-level communication. Note that peers exchange these
messages directly. There is no routing/path finding involved.
# Safety
* Locally force closed channels are now [kept in the channel.backup file until
their time lock has fully matured](https://github.com/lightningnetwork/lnd/pull/5528).
@@ -504,6 +520,7 @@ change](https://github.com/lightningnetwork/lnd/pull/5613).
* Hampus Sjöberg
* Harsha Goli
* Jesse de Wit
* Joost Jager
* Martin Habovstiak
* Naveen Srinivasan
* Oliver Gugger