accept_channel in bolt02

announcement_signatures in bolt07

channel_announcement in bolt07

channel_reestablish in bolt02

channel_update in bolt07

closing_signed in bolt02

commitment_signed in bolt02

Struct used to return valeus from revoke_and_ack messages, cotaining a bunch of commitment transaction updates if they were pending.

data_loss_protect in channel_reestablish which exists only when option_data_lock_protect is negotiated see bolt02

failuremsg in bolt04

inner data for failure msg described in bolt04

funding_created in bolt02

funding_locked in bolt02

funding_signed in bolt02

gossip_timestamp_filter in bolt07

The marker interface to annotate the type p2p messages for managing the channel itself e.g. opening/closure/update. but not for htlc payment.

The marker interface to annotate the p2p message related to HTLC update.

The marker interface to annotate the type for p2p serialization.

Extension methods for ILightningMsg

The type serializable for lightning p2p network. Should throw FormatException when it fails.

Extension methods for ILightningSerializable

init in bolt01

Pair of Address and port.

The marker interface to annotate the p2p message related to querying the information to other nodes.

The marker interface to annotate the p2p message related to routing

The marker interface to annotate the type for very basic p2p messaging. e.g. ping/pong, error.

The marker interface to annotate the p2p message related to channel update (including htlc creation/revocation).

Functions to work with LightningMsg

ip address for Lightning Node's p2p connection.

node_announcement in bolt07

onion_packet described in bolt04 todo: add methods to parse OnionPayload from HopData field.

Pair of Address and port.

Onion address v3 contains information more than v2 or normal ipv4/v6 address e.g. Checksum and the version number.

open_channel in bolt02

Before TLV gets standardized. Optional fields are defined directly in bolt. This a type annotation to make clear that the field is such an optional type. The actual type is just a standard FSharpOption.

ping in bolt01

pong in bolt01

query_channel_range in bolt07

query_short_channel_ids in bolt07

reply_channel_range in bolt07

reply_short_channel_ids_end in bolt07

revoke_and_ack in bolt02

shutdown in bolt02

channel_announcement in bolt07 without signatures

channel_update in bolt07 without signatures

node_announcement in bolt07 without signatures. Features are stored as byte array because node_announcement with invalid or unknown features should not raise exception on deserialization. They can be accessed using Features property

update_add_htlc in bolt02

update_fail_htlc in bolt02

update_fail_malformed_htlc in bolt02

update_fee in bolt02

update_fulfill_htlc in bolt02