Merge pull request #1109 from rustyrussell/define-negotiated

BOLT 1: define what `offered` and `negotiated` mean.
lightning · Oct 23, 2023 · 7620072 · 7620072
2 parents 4dcc377 + 95f2bbf
commit 7620072
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/01-messaging.md b/01-messaging.md
@@ -255,6 +255,8 @@ Once authentication is complete, the first message reveals the features supporte
 
 [BOLT #9](09-features.md) specifies lists of features. Each feature is generally represented by 2 bits. The least-significant bit is numbered 0, which is _even_, and the next most significant bit is numbered 1, which is _odd_.  For historical reasons, features are divided into global and local feature bitmasks.
 
+A feature is *offered* if a peer set it in the `init` message for the current connection (as either even or odd).  A feature is *negotiated* if either both peers offered it, or the local node offered it as even: it can assume the peer supports it, as it did not disconnect as it would be required to do.
+
 The `features` field MUST be padded to bytes with 0s.
 
 1. type: 16 (`init`)