@ -75,7 +75,7 @@ Whenever nodes communicate with each other, whether through invoices or other me
For example, the `channel_announcement` and `node_announcement` messages described in BOLT #7 have a predefined `features` field reserved for this information.
The `features` field will take the form of a string of paired bits that will look something like this:
[feature_bits_example]
[feature-bits-example]
----
00101000001000000000
----
@ -90,18 +90,23 @@ The rule of thumb is: "it's ok to be odd".
Using BOLT #9 we can break down the above string as follows:
| 18/19 | `option_support_large_channel` | 00 | Not enabled
|===
If Alice sees this string in a node announcement message from Bob's node, then it knows from bits 16 and 17 that Bob's node supports multi-part payments.
And because the pair is odd, Alice's node knows that the feature is backwards-compatible.