Modules§
- amount
- Nested message and enum types in
Amount
. - feerate
- Nested message and enum types in
Feerate
. - hsm_
client - Generated client implementations.
- hsm_
server - Generated server implementations.
- incoming_
payment - Nested message and enum types in
IncomingPayment
. - invoice_
identifier - Nested message and enum types in
InvoiceIdentifier
. - node_
client - Generated client implementations.
- node_
server - Generated server implementations.
- payment_
identifier - Nested message and enum types in
PaymentIdentifier
. - trampoline_
pay_ response - Nested message and enum types in
TrampolinePayResponse
.
Structs§
- Address
- Aliases
- Amount
- Bitcoin
Address - Channel
- Close
Channel Request - Close
Channel Response - Confirmation
- Connect
Request - Connect
Response - Custommsg
- Disconnect
Request - Disconnect
Response - Empty
- Feerate
- Fund
Channel Request - Fund
Channel Response - GetInfo
Request - GetInfo
Response - GlConfig
- The
GlConfig
is used to pass greenlight-specific startup parameters to the node. Thegl-plugin
will look for a serialized config object in the node’s datastore to load these values from. Please refer to the individual fields to learn what they do. - HsmRequest
- HsmRequest
Context - HsmResponse
- Htlc
- Incoming
Payment - Invoice
- Invoice
Identifier - Invoice
Request - Keysend
Request - List
Funds Channel - List
Funds Output - List
Funds Request - List
Funds Response - List
Invoices Request - List
Invoices Response - List
Payments Request - Request a list of payments that this node has performed. Optionally the query can be narrowed to a single payment by providing an identifier.
- List
Payments Response - The response matching
ListPaymentRequest
. It returns a list of PayResponses, i.e., the same format asPay
returned its result. - List
Peers Request - List
Peers Response - LogEntry
- NewAddr
Request - NewAddr
Response - Node
Config - The
NodeConfig
is used to pass startup parameters to the node. Thegl-plugin
will look for a file in its directory to load these values from. Please refer to the individual fields to learn what they do. - OffChain
Payment - Outpoint
- PayRequest
- Payment
- Payment
Identifier - A payment identifier is a way to reference a unique payment, either by its bolt11 string or just the payment hash. Only one of the two may be provided at once, since having multiple ones may conflict with each other.
- Peer
- Pending
Request - This represents a grpc request that is currently pending, along with the pubkey of the client issuing the request and a matching signature. This allows the signer to verify that the state changes implied in a signature request correspond to authentic grpc commands, and were not injected somewhere along the way.
- Routehint
- Routehint
Hop - A single hop in a Routehint
- Signer
State Entry - Startup
Message - A message that we know will be requested by
lightningd
at startup, and that we stash a response to on the scheduler. This allows the scheduler to start a node without requiring the signer to connect first. Messages are stored in full, including type prefix, but without the length prefix. - Stop
Request - Stop
Response - Stream
Custommsg Request - Stream
Incoming Filter - Options to stream_incoming to specify what to stream.
- Stream
LogRequest - Timeout
- TlvField
- Trampoline
PayRequest - Trampoline
PayResponse - Withdraw
Request - Withdraw
Response
Enums§
- BtcAddress
Type - Close
Channel Type - Feerate
Preset - Let the node decide what feerate to apply based on its internal view of the network’s current feerate.
- Invoice
Status - NetAddress
Type - Output
Status - PayStatus