Skip to content

Commit

Permalink
Drop address descriptor ordering/count limits
Browse files Browse the repository at this point in the history
These aren't enforced in practice anyway so there's little value in
keeping them in the spec.
  • Loading branch information
TheBlueMatt committed Feb 12, 2021
1 parent f38f559 commit 4ebb090
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions 07-routing-gossip.md
Original file line number Diff line number Diff line change
Expand Up @@ -301,13 +301,11 @@ The origin node:
- SHOULD fill `addresses` with an address descriptor for each public network
address that expects incoming connections.
- MUST set `addrlen` to the number of bytes in `addresses`.
- MUST place address descriptors in ascending order.
- SHOULD NOT place any zero-typed address descriptors anywhere.
- SHOULD use placement only for aligning fields that follow `addresses`.
- MUST NOT create a `type 1` OR `type 2` address descriptor with `port` equal
to 0.
- SHOULD ensure `ipv4_addr` AND `ipv6_addr` are routable addresses.
- MUST NOT include more than one `address descriptor` of the same type.
- MUST set `features` according to [BOLT #9](09-features.md#assigned-features-flags)
- SHOULD set `flen` to the minimum length required to hold the `features`
bits it sets.
Expand Down

0 comments on commit 4ebb090

Please sign in to comment.