Crate lightning_invoice
Expand description
This crate provides data structures to represent lightning BOLT11 invoices and functions to create, encode and decode these. If you just want to use the standard en-/decoding functionality this should get you started:
- For parsing use
str::parse::<Bolt11Invoice>(&self)
(seeBolt11Invoice::from_str
) - For constructing invoices use the
InvoiceBuilder
- For serializing invoices use the
Display
/ToString
traits
Modules§
- Tag constants as specified in BOLT11
- Convenient utilities for paying Lightning invoices.
- Convenient utilities to create an invoice.
Structs§
- Represents a syntactically and semantically correct lightning BOLT11 invoice.
- Recoverable signature
- Description string
- Positive duration that defines when (relatively to the timestamp) in the future the invoice expires
- Builder for
Bolt11Invoice
s. It’s the most convenient and advised way to use this library. It ensures that only a semantically and syntactically correct invoice can be built using it. min_final_cltv_expiry_delta
to use for the last HTLC in the route- Payee public key
- payment_secret type, use to authenticate sender to the receiver and tie MPP HTLCs together
- A timestamp that refers to a date after 1 January 1970.
- Private routing information
- Represents an syntactically correct
Bolt11Invoice
for a payment on the lightning network, but without the signature information. Decoding and encoding should not lead to information loss but may lead to different hashes. - Data of the
RawBolt11Invoice
that is encoded in the data part - Data of the
RawBolt11Invoice
that is encoded in the human readable part. - A list of hops along a payment path terminating with a channel to the recipient.
- A channel descriptor for a hop along a payment path.
- Fees for routing via a given channel or a node
- SHA-256 hash
- Represents a signed
RawBolt11Invoice
with cached hash. The signature is not checked and may be invalid.
Enums§
- Represents the description of an invoice which has to be either a directly included string or a hash of a description provided out of band.
- Errors that indicate what is wrong with the invoice. They have some granularity for debug reasons, but should generally result in an “invalid BOLT11 invoice” message for the user.
- Errors that may occur when converting a
RawBolt11Invoice
to aBolt11Invoice
. They relate to the requirements sections in BOLT #11 - Errors that may occur when constructing a new
RawBolt11Invoice
orBolt11Invoice
- Enum representing the crypto currencies (or networks) supported by this library
- Fallback address in case no LN payment is possible
- Indicates that something went wrong while parsing or validating the invoice. Parsing errors should be mostly seen as opaque and are only there for debugging reasons. Semantic errors like wrong signatures, missing fields etc. could mean that someone tampered with the invoice.
- Tagged field which may have an unknown tag
- SI prefixes for the human readable part
- When signing using a fallible method either an user-supplied
SignError
or aCreationError
may occur. - Tagged field with known tag
Constants§
- Default expiry time as defined by BOLT 11.
- Default minimum final CLTV expiry as defined by BOLT 11.
- The maximum timestamp as
Duration::as_secs
since the Unix epoch allowed by [BOLT 11
].