Get desktop application:
View/edit binary Protocol Buffers messages
* The outpoint (txid:index) of the funding transaction. With this value, Bob will be able to generate a signature for Alice's version of the commitment transaction.
/ If true, then the channel will be closed forcibly. This means the current commitment transaction will be signed and broadcast.
/ The target number of blocks that the closure transaction should be confirmed by.
/ A manual fee rate set in sat/byte that should be used when crafting the closure transaction.
/ The pubkey of the node to open a channel with
/ The hex encoded pubkey of the node to open a channel with
/ The number of satoshis the wallet should commit to the channel
/ The number of satoshis to push to the remote side as part of the initial commitment state
/ The target number of blocks that the funding transaction should be confirmed by.
/ A manual fee rate set in sat/byte that should be used when crafting the funding transaction.
/ Whether this channel should be private, not announced to the greater network.
/ The minimum value in millisatoshi we will require for incoming HTLCs on the channel.
/ The delay we require on the remote's commitment transaction. If this is not set, it will be scaled automatically with the channel size.
/ The minimum number of confirmations each one of your outputs used for the funding transaction must satisfy.
/ Whether unconfirmed outputs should be used as inputs for the funding transaction.
/ The balance in satoshis encumbered in pending channels
/ Channels pending opening
/ Channels pending closing
/ Channels pending force closing
/ Channels waiting for closing tx to confirm
* AddInvoice attempts to add a new invoice to the invoice database. Any duplicated invoices are rejected, therefore all invoices *must* have a unique payment preimage.
* A bare-bones invoice for a payment within the Lightning Network. With the details of the invoice, the sender has all the data necessary to send a payment to the recipient.
* The "add" index of this invoice. Each newly created invoice will increment this index making it monotonically increasing. Callers to the SubscribeInvoices call can use this to instantly get notified of all added invoices with an add_index greater than this one.
/ The payment request string to be decoded
* ListInvoices returns a list of all the invoices currently stored within the database. Any active debug invoices are ignored. It has full support for paginated responses, allowing users to query for specific invoices through their add_index. This can be done by using either the first_index_offset or last_index_offset fields included in the response as the index_offset of the next request. The reversed flag is set by default in order to paginate backwards. If you wish to paginate forwards, you must explicitly set the flag to false. If none of the parameters are specified, then the last 100 invoices will be returned.
/ If set, only unsettled invoices will be returned in the response.
* The index of an invoice that will be used as either the start or end of a query to determine which invoices should be returned in the response.
/ The max number of invoices to return in the response to this query.
* If set, the invoices returned will result from seeking backwards from the specified index offset. This can be used to paginate backwards.
* A list of invoices from the time slice of the time series specified in the request.
* The index of the last item in the set of returned invoices. This can be used to seek further, pagination style.
* The index of the last item in the set of returned invoices. This can be used to seek backwards, pagination style.
/ The list of payments
/ Lightning address of the peer, in the format `<pubkey>@host`
* If set, the daemon will attempt to persistently connect to the target peer. Otherwise, the call will be synchronous.
* Whether unannounced channels are included in the response or not. If set, unannounced channels are included. Unannounced channels are both private channels, and public channels that are not yet announced to the network.
/ Returns a new instance of the directed channel graph.
/ The list of `LightningNode`s in this channel graph
/ The list of `ChannelEdge`s in this channel graph
/ The identity pubkey of the current node.
/ If applicable, the alias of the current node, e.g. "bob"
/ Number of pending channels
/ Number of active channels
/ Number of peers
/ The node's current view of the height of the best block
/ The node's current view of the hash of the best block
/ Whether the wallet's view is synced to the main chain
/ Whether the current node is connected to testnet
/ A list of active chains the node is connected to
/ The URIs of the current node.
/ Timestamp of the block best known to the wallet
/ The version of the LPD software that the node is running.
/ Number of inactive channels
/ The 33-byte hex-encoded public key for the payment destination
/ The amount to send expressed in satoshis
/ The max number of routes to return.
/ An optional CLTV delta from the current height that should be used for the timelock of the final hop
* The maximum number of satoshis that will be paid as a fee of the payment. This value can be represented either as a percentage of the amount being sent, or as a fixed amount of the maximum fee the user is willing the pay to send the payment.
* SignMessage signs a message with this node's private key. The returned signature string is `zbase32` encoded and pubkey recoverable, meaning that only the message digest and signature are needed for verification.
Used in:
Used in:
Used in:
* The unique channel ID for the channel. The first 3 bytes are the block height, the next 3 the index within the block, and the last 2 bytes are the output index for the channel.
Used in:
Used in:
Used in: ,
/ Txid of the funding transaction
/ Hex-encoded string representing the funding transaction
/ The index of the output of the funding transaction
Used in: ,
Used in: ,
/ The fee limit expressed as a fixed amount of satoshis.
/ The fee limit expressed as a percentage of the payment amount.
Used in:
Used in:
* The unique channel ID for the channel. The first 3 bytes are the block height, the next 3 the index within the block, and the last 2 bytes are the output index for the channel.
* An optional public key of the hop. If the public key is given, the payment can be executed without relying on a copy of the channel graph.
Used in:
/ The public key of the node at the start of the channel.
/ The unique identifier of the channel.
/ The base fee of the channel denominated in millisatoshis.
* The fee rate of the channel for sending one satoshi across it denominated in millionths of a satoshi.
/ The time-lock delta of the channel.
Used as request type in: PaymentService.AddInvoice
Used as field type in:
* An optional memo to attach along with the invoice. Used for record keeping purposes for the invoice's creator, and will also be set in the description field of the encoded payment request if the description_hash field is not being used.
/ An optional cryptographic receipt of payment
* The hex-encoded preimage (32 byte) which will allow settling an incoming HTLC payable to this preimage
/ The hash of the preimage
/ The value of this invoice in satoshis
/ Whether this invoice has been fulfilled
/ When this invoice was created
/ When this invoice was settled
* A bare-bones invoice for a payment within the Lightning Network. With the details of the invoice, the sender has all the data necessary to send a payment to the recipient.
* Hash (SHA-256) of a description of the payment. Used if the description of payment (memo) is too long to naturally fit within the description field of an encoded payment request.
/ Payment request expiry time in seconds. Default is 3600 (1 hour).
/ Fallback on-chain address.
/ Delta to use for the time-lock of the CLTV extended to the final hop.
* Route hints that can each be individually used to assist in reaching the invoice's destination.
/ Whether this invoice should include routing hints for private channels.
* The "add" index of this invoice. Each newly created invoice will increment this index making it monotonically increasing. Callers to the SubscribeInvoices call can use this to instantly get notified of all added invoices with an add_index greater than this one.
* The "settle" index of this invoice. Each newly settled invoice will increment this index making it monotonically increasing. Callers to the SubscribeInvoices call can use this to instantly get notified of all settled invoices with an settle_index greater than this one.
/ Deprecated, use amt_paid_sat or amt_paid_msat.
* The amount that was accepted for this invoice, in satoshis. This will ONLY be set if this invoice has been settled. We provide this field as if the invoice was created with a zero value, then we need to record what amount was ultimately accepted. Additionally, it's possible that the sender paid MORE that was specified in the original invoice. So we'll record that here as well.
* The amount that was accepted for this invoice, in millisatoshis. This will ONLY be set if this invoice has been settled. We provide this field as if the invoice was created with a zero value, then we need to record what amount was ultimately accepted. Additionally, it's possible that the sender paid MORE that was specified in the original invoice. So we'll record that here as well.
Used in:
/ The network location of the lightning node, e.g. `69.69.69.69:1337` / localhost alias is not supported yet, use 127.0.0.1
Used in:
Used in: , , , , , ,
Used in:
Used in:
/ The payment hash
/ Deprecated, use value_sat or value_msat.
/ The date of this payment
/ The path this payment took
/ The fee paid for this payment in satoshis
/ The payment preimage
/ The value of the payment in satoshis
/ The value of the payment in milli-satoshis
Used in:
/ The identity pubkey of the peer
/ Network address of the peer; eg `127.0.0.1:10011`
/ Bytes of data transmitted to this peer
/ Bytes of data transmitted from this peer
/ Satoshis sent to this peer
/ Satoshis received from this peer
/ A channel is inbound if the counterparty initiated the channel
/ Ping time to this peer
Used in:
/ The pending channel to be closed
/ The transaction id of the closing transaction
Used in:
/ The pending channel to be force closed
/ The transaction id of the closing transaction
/ The balance in satoshis encumbered in this pending channel
/ The height at which funds can be sweeped into the wallet
Remaining # of blocks until the commitment output can be swept. Negative values indicate how many blocks have passed since becoming mature.
/ The total value of funds successfully recovered from this channel
Used in: , , ,
Used in:
/ The pending channel
/ The height at which this channel will be confirmed
* The amount calculated to be paid in fees for the current set of commitment transactions. The fee amount is persisted with the channel in order to allow the fee amount to be removed and recalculated with each channel state update, including updates that happen after a system restart.
/ The weight of the commitment transaction
* The required number of satoshis per kilo-weight that the requester will pay at all times, for both the funding transaction and commitment transaction. This value can later be updated once the channel is open.
Used in:
/ The pending channel waiting for closing tx to confirm
/ The balance in satoshis encumbered in this channel
Used in:
/ The direction within the channel that the htlc was sent
/ The total value of the htlc
/ The final output to be swept back to the user's wallet
/ The next block height at which we can spend the current stage
* The number of blocks remaining until the current stage can be swept. Negative values indicate how many blocks have passed since becoming mature.
/ Indicates whether the htlc is in its first or second stage of recovery
Used in: ,
Used in: ,
* The cumulative (final) time lock across the entire route. This is the CLTV value that should be extended to the first hop in the route. All other hops will decrement the time-lock as advertised, leaving enough time for all hops to wait for or present the payment preimage to complete the payment.
* The sum of the fees paid at each hop within the final route. In the case of a one-hop payment, this value will be zero as we don't need to pay a fee it ourself.
* The total amount of funds required to complete a payment over this route. This value includes the cumulative fees at each hop. As a result, the HTLC extended to the first-hop in the route will need to have at least this many satoshis, otherwise the route will fail at an intermediate node due to an insufficient amount of fees.
* Contains details concerning the specific forwarding details at each hop.
* The total fees in millisatoshis.
* The total amount in millisatoshis.
Used in: ,
* A list of hop hints that when chained together can assist in reaching a specific destination.
Used in:
Used in: , , , , , , , ,
Used as request type in: PaymentService.SendPayment, PaymentService.SendPaymentSync
/ The identity pubkey of the payment recipient
/ The hex-encoded identity pubkey of the payment recipient
/ Number of satoshis to send.
/ The hash to use within the payment's HTLC
/ The hex-encoded hash to use within the payment's HTLC
* A bare-bones invoice for a payment within the Lightning Network. With the details of the invoice, the sender has all the data necessary to send a payment to the recipient.
* The CLTV delta from the current height that should be used to set the timelock for the final hop.
* The maximum number of satoshis that will be paid as a fee of the payment. This value can be represented either as a percentage of the amount being sent, or as a fixed amount of the maximum fee the user is willing the pay to send the payment.
Used as response type in: PaymentService.SendPayment, PaymentService.SendPaymentSync
Used as request type in: ChannelService.Pending, PaymentService.ListPayments, RoutingService.GetInfo, RoutingService.ListPeers
Used as response type in: RoutingService.ConnectPeer
(message has no fields)