Expand description
Lightning and Bitcoin primitives.
Structs§
- Amount
- A non-negative Bitcoin amount in satoshis. Serialized as a string-encoded
decimal to avoid floating-point precision loss (e.g.
"1234.567"). - Channel
Id - A newtype for
lightning::ln::types::ChannelId. - Invoice
- A BOLT 11 Lightning invoice. Serialized as a bech32-encoded string
(e.g.
"lnbc1..."). - Lnurl
PayRequest - The validated and parsed LNURL-pay request (“payRequest”).
- Lnurl
PayRequest Metadata - The metadata inside a
LnurlPayRequest. - Lnurl
Withdraw Request - LUD-03 LNURL-withdraw request.
- Offer
- A Lightning BOLT12 offer.
- OutPoint
- A reference to a specific transaction output: the
txidof the transaction together with theindexof the output within that transaction. - Txid
- A Bitcoin transaction ID. Serialized as a 64-character hex string in
conventional (reversed) byte order, e.g.
"a1075db55d416d3ca199f55b6084e2115b9345e16c5cf302fc80e9d5fbf5d48d". - User
Channel Id - A client-generated id that identifies a channel throughout its entire
lifecycle, including before the channel is confirmed on-chain and assigned
its
ChannelId.
Enums§
- Claim
Method - A single “claim method” – each kind here should correspond with a single linear (inbound) payment flow for a user, where there are no other alternate methods.
- Confirmation
Priority - Transaction confirmation priority for on-chain payments:
"high"(~1 block),"normal"(~3 blocks), or"background"(~72 blocks). - Payment
Method - A single “payment method” – each kind here should correspond with a single linear (outbound) payment flow for a user, where there are no other alternate methods.