Get desktop application:
View/edit binary Protocol Buffers messages
* lncli: `abandonchannel` AbandonChannel removes all channel state from the database except for a close summary. This method can be used to get rid of permanently unusable channels due to bugs fixed in newer versions of lnd. Only available when in debug builds of lnd.
(message has no fields)
* lncli: `addinvoice` 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.
* lncli: `channelbalance` ChannelBalance returns the total funds available across all open channels in satoshis.
(message has no fields)
/ Sum of channels balances denominated in satoshis
/ Sum of channels pending balances denominated in satoshis
* lncli: `closechannel` CloseChannel attempts to close an active channel identified by its channel outpoint (ChannelPoint). The actions of this method can additionally be augmented to attempt a force close after a timeout period in the case of an inactive peer. If a non-force close (cooperative closure) is requested, then the user can specify either a target number of blocks until the closure transaction is confirmed, or a manual fee rate. If neither are specified, then a default lax, block confirmation target is used.
* 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.
* lncli: `closedchannels` ClosedChannels returns a description of all the closed channels that this node was a participant in.
* lncli: `connect` ConnectPeer attempts to establish a connection to a remote peer. This is at the networking level, and is used for communication between nodes. This is distinct from establishing a channel with a peer.
/ 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.
(message has no fields)
* lncli: `debuglevel` DebugLevel allows a caller to programmatically set the logging verbosity of lnd. The logging can be targeted according to a coarse daemon-wide logging level, or in a granular fashion to specify the logging for a target sub-system.
* lncli: `decodepayreq` DecodePayReq takes an encoded payment request string and attempts to decode it, returning a full description of the conditions encoded within the payment request.
/ The payment request string to be decoded
* DeleteAllPayments deletes all outgoing payments from DB.
(message has no fields)
(message has no fields)
* lncli: `describegraph` DescribeGraph returns a description of the latest graph state from the point of view of the node. The graph information is partitioned into two components: all the nodes/vertexes, and all the edges that connect the vertexes themselves. As this is a directed graph, the edges also contain the node directional specific routing policy which includes: the time lock delta, fee information, etc.
* 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
* lncli: `disconnect` DisconnectPeer attempts to disconnect one peer from another identified by a given pubKey. In the case that we currently have a pending or active channel with the target peer, then this action will be not be allowed.
/ The pubkey of the node to disconnect from
(message has no fields)
* lncli: `estimatefee` EstimateFee asks the chain backend to estimate the fee rate and total fees for a transaction that pays to multiple specified outputs.
/ The map from addresses to amounts for the transaction.
/ The target number of blocks that this transaction should be confirmed by.
/ The total fee in satoshis.
/ The fee rate in satoshi/byte.
* ExportAllChannelBackups returns static channel backups for all existing channels known to lnd. A set of regular singular static channel backups for each channel are returned. Additionally, a multi-channel backup is returned as well, which contains a single encrypted blob containing the backups of each channel.
(message has no fields)
* lncli: `exportchanbackup` ExportChannelBackup attempts to return an encrypted static channel backup for the target channel identified by it channel point. The backup is encrypted with a key generated from the aezeed seed of the user. The returned backup can either be restored using the RestoreChannelBackup method once lnd is running, or via the InitWallet and UnlockWallet methods from the WalletUnlocker service.
/ The target channel point to obtain a back up for.
* lncli: `feereport` FeeReport allows the caller to obtain a report detailing the current fee schedule enforced by the node globally for each channel.
(message has no fields)
/ An array of channel fee reports which describes the current fee schedule for each channel.
/ The total amount of fee revenue (in satoshis) the switch has collected over the past 24 hrs.
/ The total amount of fee revenue (in satoshis) the switch has collected over the past 1 week.
/ The total amount of fee revenue (in satoshis) the switch has collected over the past 1 month.
* lncli: `fwdinghistory` ForwardingHistory allows the caller to query the htlcswitch for a record of all HTLCs forwarded within the target time range, and integer offset within that time range. If no time-range is specified, then the first chunk of the past 24 hrs of forwarding history are returned. A list of forwarding events are returned. The size of each forwarding event is 40 bytes, and the max message size able to be returned in gRPC is 4 MiB. As a result each message can only contain 50k entries. Each response has the index offset of the last entry. The index offset can be provided to the request to allow the caller to skip a series of records.
/ Start time is the starting point of the forwarding history request. All records beyond this point will be included, respecting the end time, and the index offset.
/ End time is the end point of the forwarding history request. The response will carry at most 50k records between the start time and the end time. The index offset can be used to implement pagination.
/ Index offset is the offset in the time series to start at. As each response can only contain 50k records, callers can use this to skip around within a packed time series.
/ The max number of events to return in the response to this query.
/ A list of forwarding events from the time slice of the time series specified in the request.
/ The index of the last time in the set of returned forwarding events. Can be used to seek further, pagination style.
* lncli: `getchaninfo` GetChanInfo returns the latest authenticated network announcement for the given channel identified by its channel ID: an 8-byte integer which uniquely identifies the location of transaction's funding output within the blockchain.
* 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.
* lncli: `getinfo` GetInfo returns general information concerning the lightning node including it's identity pubkey, alias, the chains it is connected to, and information concerning the number of open+pending channels.
(message has no fields)
/ 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. This field is deprecated and the network field should be used instead
/ The URIs of the current node.
/ Timestamp of the block best known to the wallet
/ The version of the LND software that the node is running.
/ Number of inactive channels
/ A list of active chains the node is connected to
/ The color of the current node in hex code format
* lncli: `getnetworkinfo` GetNetworkInfo returns some basic stats about the known channel graph from the point of view of the node.
(message has no fields)
* lncli: `getnodeinfo` GetNodeInfo returns the latest advertised, aggregated, and authenticated channel information for the specified node identified by its public key.
/ The 33-byte hex-encoded compressed public of the target node
/ If true, will include all known channels associated with the node.
* An individual vertex/node within the channel graph. A node is connected to other nodes by one or more channel edges emanating from it. As the graph is directed, a node will also have an incoming edge attached to it for each outgoing edge.
/ The total number of channels for the node.
/ The sum of all channels capacity for the node, denominated in satoshis.
/ A list of all public channels for the node.
* lncli: `listchaintxns` GetTransactions returns a list describing all the known transactions relevant to the wallet.
/ The list of transactions relevant to the wallet.
* lncli: `listchannels` ListChannels returns a description of all the open channels that this node is a participant in.
/ The list of active channels
* lncli: `listinvoices` 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. By default, the first 100 invoices created will be returned. Backwards pagination is also supported through the Reversed flag.
/ 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.
* lncli: `listpayments` ListPayments returns a list of all outgoing payments.
* If true, then return payments that have not yet fully completed. This means that pending payments, as well as failed payments will show up if this field is set to True.
/ The list of payments
* lncli: `listpeers` ListPeers returns a verbose listing of all currently active peers.
(message has no fields)
/ The list of currently connected peers
* lncli: `listunspent` ListUnspent returns a list of all utxos spendable by the wallet with a number of confirmations between the specified minimum and maximum.
/ The minimum number of confirmations to be included.
/ The maximum number of confirmations to be included.
/ A list of utxos
* lncli: `lookupinvoice` LookupInvoice attempts to look up an invoice according to its payment hash. The passed payment hash *must* be exactly 32 bytes, if not, an error is returned.
* The hex-encoded payment hash of the invoice to be looked up. The passed payment hash must be exactly 32 bytes, otherwise an error is returned.
/ The payment hash of the invoice to be looked up.
* lncli: `newaddress` NewAddress creates a new address under control of the local wallet.
/ The address type
/ The newly generated wallet address
* lncli: `openchannel` OpenChannel attempts to open a singly funded channel specified in the request to a remote peer. Users are able to specify a target number of blocks that the funding transaction should be confirmed in, or a manual fee rate to us for the funding transaction. If neither are specified, then a lax block confirmation target is used.
* OpenChannelSync is a synchronous version of the OpenChannel RPC call. This call is meant to be consumed by clients to the REST proxy. As with all other sync calls, all byte slices are intended to be populated as hex encoded strings.
* lncli: `pendingchannels` PendingChannels returns a list of all the channels that are currently considered "pending". A channel is pending if it has finished the funding workflow and is waiting for confirmations for the funding txn, or is in the process of closure, either initiated cooperatively or non-cooperatively.
(message has no fields)
/ 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
* lncli: `queryroutes` QueryRoutes attempts to query the daemon's Channel Router for a possible route to a target destination capable of carrying a specific amount of satoshis. The returned route contains the full details required to craft and send an HTLC, also including the necessary information that should be present within the Sphinx packet encapsulated within the HTLC.
/ The 33-byte hex-encoded public key for the payment destination
/ The amount to send expressed in satoshis
/ 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.
* A list of nodes to ignore during path finding.
* A list of edges to ignore during path finding.
* The source node where the request route should originated from. If empty, self is assumed.
* lncli: `restorechanbackup` RestoreChannelBackups accepts a set of singular channel backups, or a single encrypted multi-chan backup and attempts to recover any funds remaining within the channel. If we are able to unpack the backup, then the new channel will be shown under listchannels, as well as pending channels.
(message has no fields)
* lncli: `sendcoins` SendCoins executes a request to send coins to a particular address. Unlike SendMany, this RPC call only allows creating a single output at a time. If neither target_conf, or sat_per_byte are set, then the internal wallet will consult its fee model to determine a fee for the default confirmation target.
/ The address to send coins to
/ The amount in satoshis to send
/ The target number of blocks that this transaction should be confirmed by.
/ A manual fee rate set in sat/byte that should be used when crafting the transaction.
* If set, then the amount field will be ignored, and lnd will attempt to send all the coins under control of the internal wallet to the specified address.
/ The transaction ID of the transaction
* lncli: `sendmany` SendMany handles a request for a transaction that creates multiple specified outputs in parallel. If neither target_conf, or sat_per_byte are set, then the internal wallet will consult its fee model to determine a fee for the default confirmation target.
/ The map from addresses to amounts
/ The target number of blocks that this transaction should be confirmed by.
/ A manual fee rate set in sat/byte that should be used when crafting the transaction.
/ The id of the transaction
* lncli: `sendpayment` SendPayment dispatches a bi-directional streaming RPC for sending payments through the Lightning Network. A single RPC invocation creates a persistent bi-directional stream allowing clients to rapidly send payments through the Lightning Network with a single persistent connection.
* SendPaymentSync is the synchronous non-streaming version of SendPayment. This RPC is intended to be consumed by clients of the REST proxy. Additionally, this RPC expects the destination's public key and the payment hash (if any) to be encoded as hex strings.
* lncli: `sendtoroute` SendToRoute is a bi-directional streaming RPC for sending payment through the Lightning Network. This method differs from SendPayment in that it allows users to specify a full route manually. This can be used for things like rebalancing, and atomic swaps.
* SendToRouteSync is a synchronous version of SendToRoute. It Will block until the payment either fails or succeeds.
* lncli: `signmessage` 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.
/ The message to be signed
/ The signature for the given message
* lncli: `stop` StopDaemon will send a shutdown request to the interrupt handler, triggering a graceful shutdown of the daemon.
(message has no fields)
(message has no fields)
* SubscribeChannelBackups allows a client to sub-subscribe to the most up to date information concerning the state of all channel backups. Each time a new channel is added, we return the new set of channels, along with a multi-chan backup containing the backup info for all channels. Each time a channel is closed, we send a new update, which contains new new chan back ups, but the updated set of encrypted multi-chan backups with the closed channel(s) removed.
(message has no fields)
* lncli: `subscribechannelevents` SubscribeChannelEvents creates a uni-directional stream from the server to the client in which any updates relevant to the state of the channels are sent over. Events include new active channels, inactive channels, and closed channels.
(message has no fields)
* SubscribeChannelGraph launches a streaming RPC that allows the caller to receive notifications upon any changes to the channel graph topology from the point of view of the responding node. Events notified include: new nodes coming online, nodes updating their authenticated attributes, new channels being advertised, updates in the routing policy for a directional channel edge, and when channels are closed on-chain.
(message has no fields)
* SubscribeInvoices returns a uni-directional stream (server -> client) for notifying the client of newly added/settled invoices. The caller can optionally specify the add_index and/or the settle_index. If the add_index is specified, then we'll first start by sending add invoice events for all invoices with an add_index greater than the specified value. If the settle_index is specified, the next, we'll send out all settle events for invoices with a settle_index greater than the specified value. One or both of these fields can be set. If no fields are set, then we'll only send out the latest add/settle events.
* If specified (non-zero), then we'll first start by sending out notifications for all added indexes with an add_index greater than this value. This allows callers to catch up on any events they missed while they weren't connected to the streaming RPC.
* If specified (non-zero), then we'll first start by sending out notifications for all settled indexes with an settle_index greater than this value. This allows callers to catch up on any events they missed while they weren't connected to the streaming RPC.
* SubscribeTransactions creates a uni-directional stream from the server to the client in which any newly discovered transactions relevant to the wallet are sent over.
* lncli: `updatechanpolicy` UpdateChannelPolicy allows the caller to update the fee schedule and channel policies for all channels globally, or a particular channel.
/ If set, then this update applies to all currently active channels.
/ If set, this update will target a specific channel.
/ The base fee charged regardless of the number of milli-satoshis sent.
/ The effective fee rate in milli-satoshis. The precision of this value goes up to 6 decimal places, so 1e-6.
/ The required timelock delta for HTLCs forwarded over the channel.
(message has no fields)
* VerifyChanBackup allows a caller to verify the integrity of a channel backup snapshot. This method will accept either a packed Single or a packed Multi. Specifying both will result in an error.
(message has no fields)
* lncli: `verifymessage` VerifyMessage verifies a signature over a msg. The signature must be zbase32 encoded and signed by an active node in the resident node's channel database. In addition to returning the validity of the signature, VerifyMessage also returns the recovered pubkey from the signature.
/ The message over which the signature is to be verified
/ The signature to be verified over the given message
/ Whether the signature was valid over the given message
/ The pubkey recovered from the signature
* lncli: `walletbalance` WalletBalance returns total unspent outputs(confirmed and unconfirmed), all confirmed unspent outputs and all unconfirmed unspent outputs under control of the wallet.
(message has no fields)
/ The balance of the wallet
/ The confirmed balance of a wallet(with >= 1 confirmations)
/ The unconfirmed balance of a wallet(with 0 confirmations)
The WalletUnlocker service is used to set up a wallet password for lnd at first startup, and unlock a previously set up wallet.
* lncli: `changepassword` ChangePassword changes the password of the encrypted wallet. This will automatically unlock the wallet database if successful.
* current_password should be the current valid passphrase used to unlock the daemon.
* new_password should be the new passphrase that will be needed to unlock the daemon.
(message has no fields)
* GenSeed is the first method that should be used to instantiate a new lnd instance. This method allows a caller to generate a new aezeed cipher seed given an optional passphrase. If provided, the passphrase will be necessary to decrypt the cipherseed to expose the internal wallet seed. Once the cipherseed is obtained and verified by the user, the InitWallet method should be used to commit the newly generated seed, and create the wallet.
* aezeed_passphrase is an optional user provided passphrase that will be used to encrypt the generated aezeed cipher seed.
* seed_entropy is an optional 16-bytes generated via CSPRNG. If not specified, then a fresh set of randomness will be used to create the seed.
* cipher_seed_mnemonic is a 24-word mnemonic that encodes a prior aezeed cipher seed obtained by the user. This field is optional, as if not provided, then the daemon will generate a new cipher seed for the user. Otherwise, then the daemon will attempt to recover the wallet state linked to this cipher seed.
* enciphered_seed are the raw aezeed cipher seed bytes. This is the raw cipher text before run through our mnemonic encoding scheme.
* InitWallet is used when lnd is starting up for the first time to fully initialize the daemon and its internal wallet. At the very least a wallet password must be provided. This will be used to encrypt sensitive material on disk. In the case of a recovery scenario, the user can also specify their aezeed mnemonic and passphrase. If set, then the daemon will use this prior state to initialize its internal wallet. Alternatively, this can be used along with the GenSeed RPC to obtain a seed, then present it to the user. Once it has been verified by the user, the seed can be fed into this RPC in order to commit the new wallet.
* wallet_password is the passphrase that should be used to encrypt the wallet. This MUST be at least 8 chars in length. After creation, this password is required to unlock the daemon.
* cipher_seed_mnemonic is a 24-word mnemonic that encodes a prior aezeed cipher seed obtained by the user. This may have been generated by the GenSeed method, or be an existing seed.
* aezeed_passphrase is an optional user provided passphrase that will be used to encrypt the generated aezeed cipher seed.
* recovery_window is an optional argument specifying the address lookahead when restoring a wallet seed. The recovery window applies to each individual branch of the BIP44 derivation paths. Supplying a recovery window of zero indicates that no addresses should be recovered, such after the first initialization of the wallet.
* channel_backups is an optional argument that allows clients to recover the settled funds within a set of channels. This should be populated if the user was unable to close out all channels and sweep funds before partial or total data loss occurred. If specified, then after on-chain recovery of funds, lnd begin to carry out the data loss recovery protocol in order to recover the funds in each channel from a remote force closed transaction.
(message has no fields)
* lncli: `unlock` UnlockWallet is used at startup of lnd to provide a password to unlock the wallet database.
* wallet_password should be the current valid passphrase for the daemon. This will be required to decrypt on-disk material that the daemon requires to function properly.
* recovery_window is an optional argument specifying the address lookahead when restoring a wallet seed. The recovery window applies to each individual branch of the BIP44 derivation paths. Supplying a recovery window of zero indicates that no addresses should be recovered, such after the first initialization of the wallet.
* channel_backups is an optional argument that allows clients to recover the settled funds within a set of channels. This should be populated if the user was unable to close out all channels and sweep funds before partial or total data loss occurred. If specified, then after on-chain recovery of funds, lnd begin to carry out the data loss recovery protocol in order to recover the funds in each channel from a remote force closed transaction.
(message has no fields)
* `AddressType` has to be one of: - `p2wkh`: Pay to witness key hash (`WITNESS_PUBKEY_HASH` = 0) - `np2wkh`: Pay to nested witness key hash (`NESTED_PUBKEY_HASH` = 1)
Used in: ,
Used in:
/ The blockchain the node is on (eg bitcoin, litecoin)
/ The network the node is on (eg regtest, testnet, mainnet)
Used as request type in: Lightning.VerifyChanBackup
Used as response type in: Lightning.ExportAllChannelBackups, Lightning.SubscribeChannelBackups
Used as field type in: ,
* The set of new channels that have been added since the last channel backup snapshot was requested.
* A multi-channel backup that covers all open channels currently known to lnd.
Used in: ,
/ Whether this channel is active or not
/ The identity pubkey of the remote node
* 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.
* 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.
/ The total amount of funds held in this channel
/ This node's current balance in this channel
/ The counterparty's current balance in this channel
* 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.
/ The unsettled balance in this channel
* The total number of satoshis we've sent within this channel.
* The total number of satoshis we've received within this channel.
* The total number of updates conducted within this channel.
* The list of active, uncleared HTLCs currently pending within the channel.
* The CSV delay expressed in relative blocks. If the channel is force closed, we will need to wait for this many blocks before we can regain our funds.
/ Whether this channel is advertised to the network or not.
/ True if we were the ones that created the channel.
/ A set of flags showing the current state of the channel.
Used as response type in: Lightning.ExportChannelBackup
Used as field type in:
* Identifies the channel that this backup belongs to.
* Is an encrypted single-chan backup. this can be passed to RestoreChannelBackups, or the WalletUnlocker Init and Unlock methods in order to trigger the recovery protocol.
Used in: ,
* A set of single-chan static channel backups.
Used in: ,
/ The outpoint (txid:index) of the funding transaction.
/ The unique channel ID for the channel.
/ The hash of the genesis block that this channel resides within.
/ The txid of the transaction which ultimately closed this channel.
/ Public key of the remote peer that we formerly had a channel with.
/ Total capacity of the channel.
/ Height at which the funding transaction was spent.
/ Settled balance at the time of channel closure
/ The sum of all the time-locked outputs at the time of channel closure
/ Details on how the channel was closed.
Used in:
Used in:
* A fully authenticated channel along with all its unique attributes. Once an authenticated channel announcement has been processed on the network, then an instance of ChannelEdgeInfo encapsulating the channels attributes is stored. The other portions relevant to routing policy of a channel are stored within a ChannelEdgePolicy for each direction of the channel.
Used as response type in: Lightning.GetChanInfo
Used as field type 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:
* 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:
/ The channel that this fee report belongs to.
/ The base fee charged regardless of the number of milli-satoshis sent.
/ The amount charged per milli-satoshis transferred expressed in millionths of a satoshi.
/ The effective fee rate in milli-satoshis. Computed by dividing the fee_per_mil value by 1 million.
Used in:
Used as response type in: Lightning.OpenChannelSync
Used as field type in: , , , , , , , , ,
/ Txid of the funding transaction
/ Hex-encoded string representing the funding transaction
/ The index of the output of the funding transaction
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:
/ The short channel id of this edge.
* The direction of this edge. If direction_reverse is false, the direction of this edge is from the channel endpoint with the lexicographically smaller pub key to the endpoint with the larger pub key. If direction_reverse is is true, the edge goes the other way.
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:
/ Timestamp is the time (unix epoch offset) that this circuit was completed.
/ The incoming channel ID that carried the HTLC that created the circuit.
/ The outgoing channel ID that carried the preimage that completed the circuit.
/ The total amount (in satoshis) of the incoming HTLC that created half the circuit.
/ The total amount (in satoshis) of the outgoing HTLC that created the second half of the circuit.
/ The total fee (in satoshis) that this payment circuit carried.
/ The total fee (in milli-satoshis) that this payment circuit carried.
Used as request type in: Lightning.GetTransactions, Lightning.SubscribeTransactions
(message has no fields)
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: Lightning.AddInvoice
Used as response type in: Lightning.LookupInvoice, Lightning.SubscribeInvoices
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.
* Deprecated. An optional cryptographic receipt of payment which is not implemented.
* 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.
* The state the invoice is in.
Used in:
Used in:
/ The identity pubkey of the Lightning node
/ The network location of the lightning node, e.g. `69.69.69.69:1337` or `localhost:10011`
* An individual vertex/node within the channel graph. A node is connected to other nodes by one or more channel edges emanating from it. As the graph is directed, a node will also have an incoming edge attached to it for each outgoing edge.
Used in: ,
Used in:
* Is the set of all channels that are included in this multi-channel backup.
* A single encrypted blob containing all the static channel backups of the channel listed above. This can be stored as a single file or blob, and safely be replaced with any prior/future versions.
Used in:
Used in:
Used as request type in: Lightning.OpenChannel, Lightning.OpenChannelSync
/ 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.
Used in:
/ Raw bytes representing the transaction id.
/ Reversed, hex-encoded string representing the transaction id.
/ The index of the output on the transaction.
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
/ The optional payment request being fulfilled.
The status of the payment.
Used in:
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
The type of sync we are currently performing with this peer.
Used in:
* Denotes that we cannot determine the peer's current sync type.
* Denotes that we are actively receiving new graph updates from the peer.
* Denotes that we are not receiving new graph updates from the 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 swept 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: ,
* A path through the channel graph which runs over one or more channels in succession. This struct carries all the information required to craft the Sphinx onion packet, and send the payment along the first hop in the path. A route is only selected as valid if all the channels have sufficient capacity to carry the initial payment amount after fees are accounted for.
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 to ourselves.
* 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 as request type in: Lightning.SendPayment, Lightning.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.
* The channel id of the channel that must be taken to the first hop. If zero, any channel may be used.
* An optional maximum total time lock for the route. If zero, there is no maximum enforced.
Used as response type in: Lightning.SendPayment, Lightning.SendPaymentSync, Lightning.SendToRoute, Lightning.SendToRouteSync
Used as request type in: Lightning.SendToRoute, Lightning.SendToRouteSync
/ The payment hash to use for the HTLC.
/ An optional hex-encoded payment hash to be used for the HTLC.
/ Route that should be used to attempt to complete the payment.
Used as response type in: Lightning.SubscribeTransactions
Used as field type in:
/ The transaction hash
/ The transaction amount, denominated in satoshis
/ The number of confirmations
/ The hash of the block this transaction was included in
/ The height of the block this transaction was included in
/ Timestamp of this transaction
/ Fees paid for this transaction
/ Addresses that received funds for this transaction
/ The raw transaction hex.
Used in:
/ The type of address
/ The address
/ The value of the unspent coin in satoshis
/ The pkscript in hex
/ The outpoint in format txid:n
/ The number of confirmations for the Utxo