data for TLV stream in accept_channel message See bolt02

Feature bits specified in BOLT 9. It has no constructors, use its static members to instantiate.

Feature bits described in BOLT 9 Use HasFeature to see if it has specific feature or not.

Error related to feature bits.

The feature bit in LN can tell other node that specific feature is required or optional. This union is to represent which.

TLV with unknown types. TLV represents Type-Length-Value format. and it is designed to be ignorable if the semantics is not clear to the node. So that P2P messages can be forward compatible. See bolt01 For the detail.

All other concrete TLV types (e.g. InitTLV) has methods To convert to/from this type.

data for tlv_payload defined in bolt04

data for TLV stream in init message See bolt01

stream for reading lightning p2p msg

Simple Wrapper stream for serializing Lightning Network p2p messages. Why not use BitWriter/Reader? Because it does not support big endian and We might want to extend it in the future.

stream for writing lightning p2p msg

data foreach hop_payloads in onion_packet described in bolt04

legacy hop_data payload format described in bolt04

data for TLV stream in open_channel message See bolt02

data for TLV stream in query_channel_range message See bolt07

See query_short_channel_ids msg description in bolt07 For the detail

See query_channel_range msg description in bolt07 For the detail

data for TLV stream in query_short_channel_ids message See bolt07

data for TLV stream in reply_channel_range message. See bolt07

This is a type described in bolt07 as channel_update_checksums

This is a type described in bolt07 as channel_update_timestamps