package walletrpc
Get desktop application:
View/edit binary Protocol Buffers messages
service WalletKit
walletkit.proto:30WalletKit is a service that gives access to the core functionalities of the daemon's wallet.
rpc BumpFee (, )
walletkit.proto:352lncli: `wallet bumpfee` BumpFee is an endpoint that allows users to interact with lnd's sweeper directly. It takes an outpoint from an unconfirmed transaction and sends it to the sweeper for potential fee bumping. Depending on whether the outpoint has been registered in the sweeper (an existing input, e.g., an anchor output) or not (a new input, e.g., an unconfirmed wallet utxo), this will either be an RBF or CPFP attempt. When receiving an input, lnd’s sweeper needs to understand its time sensitivity to make economical fee bumps - internally a fee function is created using the deadline and budget to guide the process. When the deadline is approaching, the fee function will increase the fee rate and perform an RBF. When a force close happens, all the outputs from the force closing transaction will be registered in the sweeper. The sweeper will then handle the creation, publish, and fee bumping of the sweeping transactions. Everytime a new block comes in, unless the sweeping transaction is confirmed, an RBF is attempted. To interfere with this automatic process, users can use BumpFee to specify customized fee rate, budget, deadline, and whether the sweep should happen immediately. It's recommended to call `ListSweeps` to understand the shape of the existing sweeping transaction first - depending on the number of inputs in this transaction, the RBF requirements can be quite different. This RPC also serves useful when wanting to perform a Child-Pays-For-Parent (CPFP), where the child transaction pays for its parent's fee. This can be done by specifying an outpoint within the low fee transaction that is under the control of the wallet.
message
walletkit.proto:1421optional outpoint = 1
The input we're attempting to bump the fee of.
uint32 target_conf = 2
Optional. The conf target the underlying fee estimator will use to estimate the starting fee rate for the fee function.
uint32 sat_per_byte = 3
Deprecated, use sat_per_vbyte. The fee rate, expressed in sat/vbyte, that should be used to spend the input with.
bool force = 4
Deprecated, use immediate. Whether this input must be force-swept. This means that it is swept immediately.
uint64 sat_per_vbyte = 5
Optional. The starting fee rate, expressed in sat/vbyte, that will be used to spend the input with initially. This value will be used by the sweeper's fee function as its starting fee rate. When not set, the sweeper will use the estimated fee rate using the `target_conf` as the starting fee rate.
bool immediate = 6
Optional. Whether this input will be swept immediately. When set to true, the sweeper will sweep this input without waiting for the next block.
uint64 budget = 7
Optional. The max amount in sats that can be used as the fees. Setting this value greater than the input's value may result in CPFP - one or more wallet utxos will be used to pay the fees specified by the budget. If not set, for new inputs, by default 50% of the input's value will be treated as the budget for fee bumping; for existing inputs, their current budgets will be retained.
uint32 deadline_delta = 8
Optional. The deadline delta in number of blocks that the output should be spent within. This translates internally to the width of the fee function that the sweeper will use to bump the fee rate. When the deadline is reached, ALL the budget will be spent as fees.
message
walletkit.proto:1474string status = 1
The status of the bump fee operation.
rpc BumpForceCloseFee (, )
walletkit.proto:358lncli: `wallet bumpforceclosefee` BumpForceCloseFee is an endpoint that allows users to bump the fee of a channel force close. This only works for channels with option_anchors.
message
walletkit.proto:1479optional chan_point = 1
The channel point which force close transaction we are attempting to bump the fee rate for.
uint32 deadline_delta = 2
Optional. The deadline delta in number of blocks that the anchor output should be spent within to bump the closing transaction. When the deadline is reached, ALL the budget will be spent as fees
uint64 starting_feerate = 3
Optional. The starting fee rate, expressed in sat/vbyte. This value will be used by the sweeper's fee function as its starting fee rate. When not set, the sweeper will use the estimated fee rate using the target_conf as the starting fee rate.
bool immediate = 4
Optional. Whether this cpfp transaction will be triggered immediately. When set to true, the sweeper will consider all currently registered sweeps and trigger new batch transactions including the sweeping of the anchor output related to the selected force close transaction.
uint64 budget = 5
Optional. The max amount in sats that can be used as the fees. For already registered anchor outputs if not set explicitly the old value will be used. For channel force closes which have no HTLCs in their commitment transaction this value has to be set to an appropriate amount to pay for the cpfp transaction of the force closed channel otherwise the fee bumping will fail.
uint32 target_conf = 6
Optional. The conf target the underlying fee estimator will use to estimate the starting fee rate for the fee function.
message
walletkit.proto:1519string status = 1
The status of the force close fee bump operation.
rpc DeriveKey (, )
walletkit.proto:78DeriveKey attempts to derive an arbitrary key specified by the passed KeyLocator.
rpc DeriveNextKey (, )
walletkit.proto:72DeriveNextKey attempts to derive the *next* key within the key family (account in BIP43) specified. This method should return the next external child within this branch.
message
walletkit.proto:523int32 key_finger_print = 1
Is the key finger print of the root pubkey that this request is targeting. This allows the WalletKit to possibly serve out keys for multiple HD chains via public derivation.
int32 key_family = 2
The target key family to derive a key from. In other contexts, this is known as the "account".
rpc EstimateFee (, )
walletkit.proto:308lncli: `wallet estimatefeerate` EstimateFee attempts to query the internal fee estimator of the wallet to determine the fee (in sat/kw) to attach to a transaction in order to achieve the confirmation target.
message
walletkit.proto:1019int32 conf_target = 1
The number of confirmations to shoot for when estimating the fee.
message
walletkit.proto:1025int64 sat_per_kw = 1
The amount of satoshis per kw that should be used in order to reach the confirmation target in the request.
int64 min_relay_fee_sat_per_kw = 2
The current minimum relay fee based on our chain backend in sat/kw.
rpc FinalizePsbt (, )
walletkit.proto:445lncli: `wallet psbt finalize` FinalizePsbt expects a partial transaction with all inputs and outputs fully declared and tries to sign all inputs that belong to the wallet. Lnd must be the last signer of the transaction. That means, if there are any unsigned non-witness inputs or inputs without UTXO information attached or inputs without witness data that do not belong to lnd's wallet, this method will fail. If no error is returned, the PSBT is ready to be extracted and the final TX within to be broadcast. NOTE: This method does NOT publish the transaction once finalized. It is the caller's responsibility to either publish the transaction on success or unlock/release any locked UTXOs in case of an error in this method.
message
walletkit.proto:1817bytes funded_psbt = 1
A PSBT that should be signed and finalized. The PSBT must contain all required inputs, outputs, UTXO data and partial signatures of all other signers.
string account = 5
The name of the account to finalize the PSBT with. If empty, the default wallet account is used.
message
walletkit.proto:1831bytes signed_psbt = 1
The fully signed and finalized transaction in PSBT format.
bytes raw_final_tx = 2
The fully signed and finalized transaction in the raw wire format.
rpc FundPsbt (, )
walletkit.proto:415lncli: `wallet psbt fund` FundPsbt creates a fully populated PSBT that contains enough inputs to fund the outputs specified in the template. There are three ways a user can specify what we call the template (a list of inputs and outputs to use in the PSBT): Either as a PSBT packet directly with no coin selection (using the legacy "psbt" field), a PSBT with advanced coin selection support (using the new "coin_select" field) or as a raw RPC message (using the "raw" field). The legacy "psbt" and "raw" modes, the following restrictions apply: 1. If there are no inputs specified in the template, coin selection is performed automatically. 2. If the template does contain any inputs, it is assumed that full coin selection happened externally and no additional inputs are added. If the specified inputs aren't enough to fund the outputs with the given fee rate, an error is returned. The new "coin_select" mode does not have these restrictions and allows the user to specify a PSBT with inputs and outputs and still perform coin selection on top of that. For all modes this RPC requires any inputs that are specified to be locked by the user (if they belong to this node in the first place). After either selecting or verifying the inputs, all input UTXOs are locked with an internal app ID. A non-zero input_release_after_spend_confs applies a confirmation-controlled lifetime to every input lease this RPC acquires. Those leases ignore wall-clock expiration and release at the requested spend depth or through ReleaseOutput. The RPC fails if the wallet cannot apply this option. Wallet capability is checked even when coin selection does not need to acquire an input lease. A custom_lock_id is required for a confirmation-controlled lease. NOTE: If this method returns without an error, it is the caller's responsibility to either spend the locked UTXOs (by finalizing and then publishing the transaction) or to unlock/release the locked UTXOs in case of an error on the caller's side.
message
walletkit.proto:1590oneof template
bytes psbt = 1
Use an existing PSBT packet as the template for the funded PSBT. The packet must contain at least one non-dust output. If one or more inputs are specified, no coin selection is performed. In that case every input must be an UTXO known to the wallet that has not been locked before. The sum of all inputs must be sufficiently greater than the sum of all outputs to pay a miner fee with the specified fee rate. A change output is added to the PSBT if necessary.
raw = 2
Use the outputs and optional inputs from this raw template.
coin_select = 9
Use an existing PSBT packet as the template for the funded PSBT. The difference to the pure PSBT template above is that coin selection is performed even if inputs are specified. The output amounts are summed up and used as the target amount for coin selection. A change output must either already exist in the PSBT and be marked as such, otherwise a new change output of the specified output type will be added. Any inputs already specified in the PSBT must already be locked (if they belong to this node), only newly added inputs will be locked by this RPC. In case the sum of the already provided inputs exceeds the required output amount, no new coins are selected. Instead only the fee and change amount calculation is performed (e.g. a change output is added if requested or the change is added to the specified existing change output, given there is any non-dust change). This can be identified by the returned locked UTXOs being empty.
oneof fees
uint32 target_conf = 3
The target number of blocks that the transaction should be confirmed in.
uint64 sat_per_vbyte = 4
The fee rate, expressed in sat/vbyte, that should be used to spend the input with.
uint64 sat_per_kw = 11
The fee rate, expressed in sat/kWU, that should be used to spend the input with.
string account = 5
The name of the account to fund the PSBT with. If empty, the default wallet account is used.
int32 min_confs = 6
The minimum number of confirmations each one of your outputs used for the transaction must satisfy.
bool spend_unconfirmed = 7
Whether unconfirmed outputs should be used as inputs for the transaction.
ChangeAddressType change_type = 8
The address type for the change. If empty, P2WPKH addresses will be used for default accounts and single imported public keys. For custom accounts, no change type should be provided as the coin selection key scope will always be used to generate the change address.
lnrpc.CoinSelectionStrategy coin_selection_strategy = 10
The strategy to use for selecting coins during funding the PSBT.
double max_fee_ratio = 12
The max fee to total output amount ratio that this psbt should adhere to.
bytes custom_lock_id = 13
The custom lock ID to use for the inputs in the funded PSBT. The value if set must be exactly 32 bytes long. If empty, the default lock ID will be used. This field is required when input_release_after_spend_confs is non-zero. In that mode it must not be all zero or LND's reserved internal lock ID. The caller must persist this ID before funding and use ReleaseOutput to unlock an abandoned PSBT whose spend never confirms.
uint64 lock_expiration_seconds = 14
If set, then time-controlled input leases in the funded PSBT will be locked for the specified duration in seconds. If not set, the default lock duration is used. A non-zero input_release_after_spend_confs makes this deadline informational only.
uint32 input_release_after_spend_confs = 15
Keep each acquired input lease until its spending transaction reaches this confirmation count or the owner explicitly releases it. A reorganization resets maturity progress. A non-zero value ignores lock_expiration_seconds; zero preserves time-controlled lease behavior.
message
walletkit.proto:1694bytes funded_psbt = 1
The funded but not yet signed PSBT packet.
int32 change_output_index = 2
The index of the added change output or -1 if no change was left over.
repeated locked_utxos = 3
The list of lock leases that were acquired for the inputs in the funded PSBT packet. Only inputs added to the PSBT by this RPC are locked, inputs that were already present in the PSBT are not locked.
rpc GetTransaction (, )
walletkit.proto:88lncli: `wallet gettx` GetTransaction returns details for a transaction found in the wallet.
rpc ImportAccount (, )
walletkit.proto:235lncli: `wallet accounts import` ImportAccount imports an account backed by an account extended public key. The master key fingerprint denotes the fingerprint of the root key corresponding to the account public key (also known as the key with derivation path m/). This may be required by some hardware wallets for proper identification and signing. The address type can usually be inferred from the key's version, but may be required for certain keys to map them into the proper scope. For BIP-0044 keys, an address type must be specified as we intend to not support importing BIP-0044 keys into the wallet using the legacy pay-to-pubkey-hash (P2PKH) scheme. A nested witness address type will force the standard BIP-0049 derivation scheme, while a witness address type will force the standard BIP-0084 derivation scheme. For BIP-0049 keys, an address type must also be specified to make a distinction between the standard BIP-0049 address schema (nested witness pubkeys everywhere) and our own BIP-0049Plus address schema (nested pubkeys externally, witness pubkeys internally). NOTE: Events (deposits/spends) for keys derived from an account will only be detected by lnd if they happen after the import. Rescans to detect past events will be supported later on.
message
walletkit.proto:778string name = 1
A name to identify the account with.
string extended_public_key = 2
A public key that corresponds to a wallet account represented as an extended key. It must conform to a derivation path of the form m/purpose'/coin_type'/account'.
bytes master_key_fingerprint = 3
The fingerprint of the root key (also known as the key with derivation path m/) from which the account public key was derived from. This may be required by some hardware wallets for proper identification and signing. The bytes must be in big-endian order.
AddressType address_type = 4
An address type is only required when the extended account public key has a legacy version (xpub, tpub, etc.), such that the wallet cannot detect what address scheme it belongs to.
bool dry_run = 5
Whether a dry run should be attempted when importing the account. This serves as a way to confirm whether the account is being imported correctly by returning the first N addresses for the external and internal branches of the account. If these addresses match as expected, then it should be safe to import the account as is.
message
walletkit.proto:813optional account = 1
The details of the imported account.
repeated string dry_run_external_addrs = 2
The first N addresses that belong to the external branch of the account. The external branch is typically used for external non-change addresses. These are only returned if a dry run was specified within the request.
repeated string dry_run_internal_addrs = 3
The first N addresses that belong to the internal branch of the account. The internal branch is typically used for change addresses. These are only returned if a dry run was specified within the request.
rpc ImportPublicKey (, )
walletkit.proto:248lncli: `wallet accounts import-pubkey` ImportPublicKey imports a public key as watch-only into the wallet. The public key is converted into a simple address of the given type and that address script is watched on chain. For Taproot keys, this will only watch the BIP-0086 style output script. Use ImportTapscript for more advanced key spend or script spend outputs. NOTE: Events (deposits/spends) for a key will only be detected by lnd if they happen after the import. Rescans to detect past events will be supported later on.
message
walletkit.proto:832bytes public_key = 1
A compressed public key represented as raw bytes.
AddressType address_type = 2
The type of address that will be generated from the public key.
message
walletkit.proto:839string status = 1
The status of the import operation.
rpc ImportTapscript (, )
walletkit.proto:264ImportTapscript imports a Taproot script and internal key and adds the resulting Taproot output key as a watch-only output script into the wallet. For BIP-0086 style Taproot keys (no root hash commitment and no script spend path) use ImportPublicKey. NOTE: Events (deposits/spends) for a key will only be detected by lnd if they happen after the import. Rescans to detect past events will be supported later on. NOTE: Taproot keys imported through this RPC currently _cannot_ be used for funding PSBTs. Only tracking the balance and UTXOs is currently supported.
message
walletkit.proto:844bytes internal_public_key = 1
The internal public key, serialized as 32-byte x-only public key.
oneof script
full_tree = 2
The full script tree with all individual leaves is known and the root hash can be constructed from the full tree directly.
partial_reveal = 3
Only a single script leaf is known. To construct the root hash, the full inclusion proof must also be provided.
bytes root_hash_only = 4
Only the root hash of the Taproot script tree (or other form of Taproot commitment) is known.
bool full_key_only = 5
Only the final, tweaked Taproot key is known and no additional information about the internal key or type of tweak that was used to derive it. When this is set, the wallet treats the key in internal_public_key as the Taproot key directly. This can be useful for tracking arbitrary Taproot outputs without the goal of ever being able to spend from them through the internal wallet.
message
walletkit.proto:907string p2tr_address = 1
The resulting pay-to-Taproot address that represents the imported internal key with the script committed to it.
rpc LabelTransaction (, )
walletkit.proto:374lncli: `wallet labeltx` LabelTransaction adds a label to a transaction. If the transaction already has a label the call will fail unless the overwrite bool is set. This will overwrite the existing transaction label. Labels must not be empty, and cannot exceed 500 characters.
message
walletkit.proto:1556bytes txid = 1
The txid of the transaction to label. Note: When using gRPC, the bytes must be in little-endian (reverse) order.
string label = 2
The label to add to the transaction, limited to 500 characters.
bool overwrite = 3
Whether to overwrite the existing label, if it is present.
message
walletkit.proto:1568string status = 1
The status of the label operation.
rpc LeaseOutput (, )
walletkit.proto:52lncli: `wallet leaseoutput` LeaseOutput locks an output to the given ID, preventing it from being available for any future coin selection attempts. The absolute time of the lock's expiration is returned. The expiration of the lock can be extended by successive invocations of this RPC. Outputs can be unlocked before their expiration through `ReleaseOutput`. A non-zero release_after_spend_confs selects a confirmation-controlled lifetime. Such a lease ignores its wall-clock expiration and releases at the requested spend depth or through ReleaseOutput. The RPC fails if the wallet cannot apply this option. Renewing the same lease with the same ID and a zero depth preserves an existing non-zero depth.
message
walletkit.proto:472bytes id = 1
An ID of 32 random bytes that must be unique for each distinct application using this RPC which will be used to bound the output lease to.
optional outpoint = 2
The identifying outpoint of the output being leased.
uint64 expiration_seconds = 3
The time in seconds before a time-controlled lock expires. If set to zero, the default lock duration is used. A non-zero release_after_spend_confs makes this deadline informational only.
uint32 release_after_spend_confs = 4
Keep the lease until the transaction spending the output reaches this confirmation count or the owner explicitly releases it. A reorganization that disconnects the spending block resets maturity progress. A non-zero value ignores expiration_seconds; zero preserves the time-controlled lease behavior.
message
walletkit.proto:495uint64 expiration = 1
The absolute expiration of a time-controlled output lease represented as a unix timestamp. Confirmation-controlled leases return the stored value for compatibility but do not apply it.
uint32 release_after_spend_confs = 2
The effective persisted spend maturity depth. A zero-depth renewal returns the retained non-zero depth of an existing confirmation-controlled lease. If that informational lookup fails after the lease succeeds, this field is zero and ListLeases can refresh it.
rpc ListAccounts (, )
walletkit.proto:95lncli: `wallet accounts list` ListAccounts retrieves all accounts belonging to the wallet by default. A name and key scope filter can be provided to filter through all of the wallet accounts and return only those matching.
message
walletkit.proto:666string name = 1
An optional filter to only return accounts matching this name.
AddressType address_type = 2
An optional filter to only return accounts matching this address type.
message
walletkit.proto:674repeated accounts = 1
rpc ListAddresses (, )
walletkit.proto:167lncli: `wallet addresses list` ListAddresses retrieves all the addresses along with their balance. An account name filter can be provided to filter through all of the wallet accounts and return the addresses of only those matching.
message
walletkit.proto:722string account_name = 1
An optional filter to only return addresses matching this account.
bool show_custom_accounts = 2
An optional flag to return LND's custom accounts (Purpose=1017) public key along with other addresses.
message
walletkit.proto:731repeated account_with_addresses = 1
A list of all the accounts and their addresses.
rpc ListLeases (, )
walletkit.proto:65lncli: `wallet listleases` ListLeases lists all currently locked utxos.
message
walletkit.proto:1839(message has no fields)
message
walletkit.proto:1842repeated locked_utxos = 1
The list of currently leased utxos.
rpc ListSweeps (, )
walletkit.proto:366lncli: `wallet listsweeps` ListSweeps returns a list of the sweep transactions our node has produced. Note that these sweeps may not be confirmed yet, as we record sweeps on broadcast, not confirmation.
message
walletkit.proto:1524bool verbose = 1
Retrieve the full sweep transaction details. If false, only the sweep txids will be returned. Note that some sweeps that LND publishes will have been replaced-by-fee, so will not be included in this output.
int32 start_height = 2
The start height to use when fetching sweeps. If not specified (0), the result will start from the earliest sweep. If set to -1 the result will only include unconfirmed sweeps (at the time of the call).
message
walletkit.proto:1540oneof sweeps
transaction_details = 1
transaction_ids = 2
rpc ListUnspent (, )
walletkit.proto:37ListUnspent returns a list of all utxos spendable by the wallet with a number of confirmations between the specified minimum and maximum. By default, all utxos are listed. To list only the unconfirmed utxos, set the unconfirmed_only to true.
message
walletkit.proto:448int32 min_confs = 1
The minimum number of confirmations to be included.
int32 max_confs = 2
The maximum number of confirmations to be included.
string account = 3
An optional filter to only include outputs belonging to an account.
bool unconfirmed_only = 4
When min_confs and max_confs are zero, setting false implicitly overrides max_confs to be MaxInt32, otherwise max_confs remains zero. An error is returned if the value is true and both min_confs and max_confs are non-zero. (default: false)
message
walletkit.proto:467repeated utxos = 1
A list of utxos satisfying the specified number of confirmations.
rpc NextAddr (, )
walletkit.proto:83NextAddr returns the next unused address within the wallet.
message
walletkit.proto:538string account = 1
The name of the account to retrieve the next address of. If empty, the default wallet account is used.
AddressType type = 2
The type of address to derive.
bool change = 3
Whether a change address should be derived.
message
walletkit.proto:555string addr = 1
The address encoded using a bech32 format.
rpc PendingSweeps (, )
walletkit.proto:320lncli: `wallet pendingsweeps` PendingSweeps returns lists of on-chain outputs that lnd is currently attempting to sweep within its central batching engine. Outputs with similar fee rates are batched together in order to sweep them within a single transaction. NOTE: Some of the fields within PendingSweepsRequest are not guaranteed to remain supported. This is an advanced API that depends on the internals of the UtxoSweeper, so things may change.
message
walletkit.proto:1411(message has no fields)
message
walletkit.proto:1414repeated pending_sweeps = 1
The set of outputs currently being swept by lnd's central batching engine.
lncli: `wallet publishtx` PublishTransaction attempts to publish the passed transaction to the network. Once this returns without an error, the wallet will continually attempt to re-broadcast the transaction on start up, until it enters the chain.
message
walletkit.proto:915bytes tx_hex = 1
The raw serialized transaction. Despite the field name, this does need to be specified in raw bytes (or base64 encoded when using REST) and not in hex. To not break existing software, the field can't simply be renamed.
string label = 2
An optional label to save with the transaction. Limited to 500 characters.
message
walletkit.proto:929string publish_error = 1
If blank, then no error occurred and the transaction was successfully published. If not the empty string, then a string representation of the broadcast error. TODO(roasbeef): map to a proper enum type
rpc ReleaseOutput (, )
walletkit.proto:60lncli: `wallet releaseoutput` ReleaseOutput unlocks an output, allowing it to be available for coin selection if it remains unspent. The ID should match the one used to originally lock the output. A retained release-after-spend lease can also be released after its spending transaction has been observed.
message
walletkit.proto:510bytes id = 1
The unique ID that was used to lock the output.
optional outpoint = 2
The identifying outpoint of the output being released.
message
walletkit.proto:518string status = 1
The status of the release operation.
rpc RemoveTransaction (, )
walletkit.proto:293lncli: `wallet removetx` RemoveTransaction attempts to remove the provided transaction from the internal transaction store of the wallet.
message
walletkit.proto:982string status = 1
The status of the remove transaction operation.
rpc RequiredReserve (, )
walletkit.proto:159lncli: `wallet requiredreserve` RequiredReserve returns the minimum amount of satoshis that should be kept in the wallet in order to fee bump anchor channels if necessary. The value scales with the number of public anchor channels but is capped at a maximum.
message
walletkit.proto:712uint32 additional_public_channels = 1
The number of additional channels the user would like to open.
message
walletkit.proto:717int64 required_reserve = 1
The amount of reserve required.
rpc SendOutputs (, )
walletkit.proto:301SendOutputs is similar to the existing sendmany call in Bitcoind, and allows the caller to create a transaction that sends to several outputs at once. This is ideal when wanting to batch create a set of transactions.
message
walletkit.proto:987int64 sat_per_kw = 1
The number of satoshis per kilo weight that should be used when crafting this transaction.
repeated outputs = 2
A slice of the outputs that should be created in the transaction produced.
string label = 3
An optional label for the transaction, limited to 500 characters.
int32 min_confs = 4
The minimum number of confirmations each one of your outputs used for the transaction must satisfy.
bool spend_unconfirmed = 5
Whether unconfirmed outputs should be used as inputs for the transaction.
lnrpc.CoinSelectionStrategy coin_selection_strategy = 6
The strategy to use for selecting coins during sending the outputs.
message
walletkit.proto:1012bytes raw_tx = 1
The serialized transaction sent out on the network.
lncli: `wallet addresses signmessage` SignMessageWithAddr returns the compact signature (base64 encoded) created with the private key of the provided address. This requires the address to be solely based on a public key lock (no scripts). Obviously the internal lnd wallet has to possess the private key of the address otherwise an error is returned. This method aims to provide full compatibility with the bitcoin-core and btcd implementation. Bitcoin-core's algorithm is not specified in a BIP and only applicable for legacy addresses. This method enhances the signing for additional address types: P2WKH, NP2WKH, P2TR. For P2TR addresses this represents a special case. ECDSA is used to create a compact signature which makes the public key of the signature recoverable.
message
walletkit.proto:741bytes msg = 1
The message to be signed. When using REST, this field must be encoded as base64.
string addr = 2
The address which will be used to look up the private key and sign the corresponding message.
message
walletkit.proto:751string signature = 1
The compact ECDSA signature for the given message encoded in base64.
rpc SignPsbt (, )
walletkit.proto:430lncli: `wallet psbt sign` SignPsbt expects a partial transaction with all inputs and outputs fully declared and tries to sign all unsigned inputs that have all required fields (UTXO information, BIP32 derivation information, witness or sig scripts) set. If no error is returned, the PSBT is ready to be given to the next signer or to be finalized if lnd was the last signer. NOTE: This RPC only signs inputs (and only those it can sign), it does not perform any other tasks (such as coin selection, UTXO locking or input/output/fee value validation, PSBT finalization). Any input that is incomplete will be skipped.
rpc SubmitPackage (, )
walletkit.proto:287lncli: `wallet submitpackage` SubmitPackage submits a package of related transactions (topologically sorted, unconfirmed parents first and the child last) for atomic validation and acceptance. Real package submission is only performed by the bitcoind backend, via the node's submitpackage RPC, which lets a zero-fee v3/TRUC parent be accepted via its fee-paying CPFP child. The btcd backend does not support submitpackage and returns an error. A neutrino light client has no mempool and cannot atomically accept a package; as a best effort it broadcasts the transactions individually and relies on a peer's 1p1c package relay, returning an unverified result (not a package-accept verdict).
message
walletkit.proto:940repeated bytes raw_txs = 1
The raw serialized transactions forming the package, topologically sorted with unconfirmed parents first and the child last.
optional uint64 sat_per_vbyte = 2
Optional per-transaction fee-rate ceiling in sat/vByte (mapped onto the submitpackage maxfeerate). When unset the node's default is used; an explicit 0 means no limit, which is required for a CPFP child whose standalone feerate is high.
message
walletkit.proto:971string package_msg = 1
A summary message; "success" when the whole package was accepted.
map<string, > tx_results = 2
Per-transaction results keyed by wtxid (hex).
repeated string replaced_transactions = 3
The txids of transactions evicted via package RBF.
lncli: `wallet addresses verifymessage` VerifyMessageWithAddr returns the validity and the recovered public key of the provided compact signature (base64 encoded). The verification is twofold. First the validity of the signature itself is checked and then it is verified that the recovered public key of the signature equals the public key of the provided address. There is no dependence on the private key of the address therefore also external addresses are allowed to verify signatures. Supported address types are P2PKH, P2WKH, NP2WKH, P2TR. This method is the counterpart of the related signing method (SignMessageWithAddr) and aims to provide full compatibility to bitcoin-core's implementation. Although bitcoin-core/btcd only provide this functionality for legacy addresses this function enhances it to the address types: P2PKH, P2WKH, NP2WKH, P2TR. The verification for P2TR addresses is a special case and requires the ECDSA compact signature to compare the reovered public key to the internal taproot key. The compact ECDSA signature format was used because there are still no known compact signature schemes for schnorr signatures.
message
walletkit.proto:756bytes msg = 1
The message to be signed. When using REST, this field must be encoded as base64.
string signature = 2
The compact ECDSA signature to be verified over the given message ecoded in base64.
string addr = 3
The address which will be used to look up the public key and verify the the signature.
message
walletkit.proto:770bool valid = 1
Whether the signature was valid over the given message.
bytes pubkey = 2
The pubkey recovered from the signature.
rpc XCreateAccount (, )
walletkit.proto:152lncli: `wallet accounts create` XCreateAccount is an experimental API that creates a new named account within the wallet, deriving the account's keys from the wallet's master key. In contrast to ImportAccount, which registers a watch-only account from an externally supplied extended public key, the account created here is fully owned by the wallet: it derives its own addresses and can sign for its own outputs. That makes it usable as an isolated pocket of funds inside a single wallet, because coin selection, change, balance and address derivation can all be scoped to it by name. NOTE: The X prefix marks this API as experimental: it may change or be removed without the usual deprecation period. It additionally requires i_know_what_i_am_doing on release builds, because a seed-only restore does not rediscover the funds an account created here holds; see the recovery note below. That second gate comes off once recovery handles these accounts, at which point the X can be dropped too. NOTE: The wallet must be unlocked, as deriving the account key requires access to the master private key. NOTE: The call is not idempotent, and the account is created before the response is sent. A client that cancels or times out may still have had the account created, in which case its retry fails with "already exists" — indistinguishable from a genuine name clash. Check ListAccounts before retrying. NOTE: The account's address type is permanent and also fixes the type of its change outputs. lnd resolves a custom account name within the key scope implied by the requested address type, so every later call must ask for the address type that maps to the same scope or the account will appear not to exist. NextAddr and NewAddress take lnrpc.AddressType, which has no HYBRID_NESTED_WITNESS_PUBKEY_HASH member: an account created as HYBRID_NESTED_WITNESS_PUBKEY_HASH must be addressed with NESTED_PUBKEY_HASH, which maps to the same BIP-0049Plus scope. TAPROOT_PUBKEY and WITNESS_PUBKEY_HASH map across unchanged. NOTE: Funds held in an account created here are not rediscovered by a seed-only recovery, because lnd's recovery scan only rederives addresses for the wallet's default account (btcwallet's RecoveryManager hardcodes waddrmgr.DefaultAccountNum). They are still recoverable, but only by reconstructing the account first, and the account name is not what has to be reproduced: accounts are derived from an index that btcwallet assigns sequentially per key scope, shared with accounts created by ImportAccount. To keep an account recoverable, record its key scope, the account index (the account's derivation_path in the response), and how many addresses it has issued. To restore: re-create every account in that key scope in their original order so the index counter lands on the same value, re-derive at least as many addresses as were previously issued with NextAddr — a rescan only searches for addresses already present in the wallet database, and a freshly created account has none — and only then rescan with --reset-wallet-transactions.
message
walletkit.proto:678string name = 1
The name to identify the new account with. The name must not be empty and must not already be in use by another account, in any key scope. The names of the wallet's built-in accounts ("default" and "imported") are reserved and cannot be used.
AddressType address_type = 2
The type of addresses the account should hold, which selects the BIP-0043 key scope the account is created under. A custom account only ever exists within a single key scope, so this permanently fixes both the account's address type and the address type of its change outputs. If unset, an account holding taproot addresses is created. NESTED_WITNESS_PUBKEY_HASH is not accepted: a wallet-derived account carries no address schema of its own, so it would silently behave as HYBRID_NESTED_WITNESS_PUBKEY_HASH. Ask for that type explicitly if it is what you want.
bool i_know_what_i_am_doing = 3
Override the requirement for being in dev mode by setting this to true and confirming the user knows what they are doing: funds held in an account created here are not rediscovered by a seed-only restore, so recovering them requires having recorded the account's key scope and index and the number of addresses it issued.
message
walletkit.proto:707optional account = 1
The newly created account.
message
walletkit.proto:569Used in: , ,
string name = 1
The name used to identify the account.
AddressType address_type = 2
The type of addresses the account supports.
string extended_public_key = 3
The public key backing the account that all keys are derived from represented as an extended key. This will always be empty for the default imported account in which single public keys are imported into.
bytes master_key_fingerprint = 4
The fingerprint of the root key from which the account public key was derived from. This will always be zero for the default imported account in which single public keys are imported into. The bytes are in big-endian order.
string derivation_path = 5
The derivation path corresponding to the account public key. This will always be empty for the default imported account in which single public keys are imported into.
uint32 external_key_count = 6
The number of keys derived from the external branch of the account public key. This will always be zero for the default imported account in which single public keys are imported into.
uint32 internal_key_count = 7
The number of keys derived from the internal branch of the account public key. This will always be zero for the default imported account in which single public keys are imported into.
bool watch_only = 8
Whether the wallet stores private keys for the account.
message
walletkit.proto:643Used in:
string name = 1
The name used to identify the account.
AddressType address_type = 2
The type of addresses the account supports.
string derivation_path = 3
The derivation path corresponding to the account public key. This will always be empty for the default imported account in which single public keys are imported into.
repeated addresses = 4
List of address, its type internal/external & balance. Note that the order of addresses will be random and not according to the derivation index, since that information is not stored by the underlying wallet.
message
walletkit.proto:616Used in:
string address = 1
The address encoded using the appropriate format depending on the address type (base58, bech32, bech32m). Note that lnd's internal/custom keys for channels and other functionality are derived from the same scope. Since they aren't really used as addresses and will never have an on-chain balance, we'll show the public key instead (only if the show_custom_accounts flag is provided).
bool is_internal = 2
Denotes if the address is a change address.
int64 balance = 3
The balance of the address.
string derivation_path = 4
The full derivation path of the address. This will be empty for imported addresses.
bytes public_key = 5
The public key of the address. This will be empty for imported addresses.
Used in: , , , , , ,
UNKNOWN = 0
WITNESS_PUBKEY_HASH = 1
NESTED_WITNESS_PUBKEY_HASH = 2
HYBRID_NESTED_WITNESS_PUBKEY_HASH = 3
TAPROOT_PUBKEY = 4
The possible change address types for default accounts and single imported public keys. By default, P2WPKH will be used. We don't provide the possibility to choose P2PKH as it is a legacy key scope, nor NP2WPKH as no key scope permits to do so. For custom accounts, no change type should be provided as the coin selection key scope will always be used to generate the change address.
Used in:
CHANGE_ADDRESS_TYPE_UNSPECIFIED = 0
CHANGE_ADDRESS_TYPE_UNSPECIFIED indicates that no change address type is provided. We will then use P2WPKH address type for change (BIP0084 key scope).
CHANGE_ADDRESS_TYPE_P2TR = 1
CHANGE_ADDRESS_TYPE_P2TR indicates to use P2TR address for change output (BIP0086 key scope).
message
walletkit.proto:736Used as request type in: WalletKit.GetTransaction, WalletKit.RemoveTransaction
string txid = 1
The txid of the transaction.
message
walletkit.proto:1541Used in:
repeated string transaction_ids = 1
Reversed, hex-encoded string representing the transaction ids of the sweeps that our node has broadcast. Note that these transactions may not have confirmed yet, we record sweeps on broadcast, not confirmation.
message
walletkit.proto:1331Used in:
optional outpoint = 1
The outpoint of the output we're attempting to sweep.
WitnessType witness_type = 2
The witness type of the output we're attempting to sweep.
uint32 amount_sat = 3
The value of the output we're attempting to sweep.
uint32 sat_per_byte = 4
Deprecated, use sat_per_vbyte. The fee rate we'll use to sweep the output, expressed in sat/vbyte. The fee rate is only determined once a sweeping transaction for the output is created, so it's possible for this to be 0 before this.
uint32 broadcast_attempts = 5
The number of broadcast attempts we've made to sweep the output.
uint32 next_broadcast_height = 6
Deprecated. The next height of the chain at which we'll attempt to broadcast the sweep transaction of the output.
bool force = 7
Deprecated, use immediate. Whether this input must be force-swept. This means that it is swept immediately.
uint32 requested_conf_target = 8
Deprecated, use deadline. The requested confirmation target for this output, which is the deadline used by the sweeper.
uint32 requested_sat_per_byte = 9
Deprecated, use requested_sat_per_vbyte. The requested fee rate, expressed in sat/vbyte, for this output.
uint64 sat_per_vbyte = 10
The current fee rate we'll use to sweep the output, expressed in sat/vbyte. The fee rate is only determined once a sweeping transaction for the output is created, so it's possible for this to be 0 before this.
uint64 requested_sat_per_vbyte = 11
The requested starting fee rate, expressed in sat/vbyte, for this output. When not requested, this field will be 0.
bool immediate = 12
Whether this input will be swept immediately.
uint64 budget = 13
The budget for this sweep, expressed in satoshis. This is the maximum amount that can be spent as fees to sweep this output.
uint32 deadline_height = 14
The deadline height used for this output when perform fee bumping.
uint32 maturity_height = 15
The block height which the input's locktime will expire at. Zero if the input has no locktime.
message
walletkit.proto:1731Used in:
bytes psbt = 1
The template to use for the funded PSBT. The template must contain at least one non-dust output. The amount to be funded is calculated by summing up the amounts of all outputs in the template, subtracting all the input values of the already specified inputs. The change value is added to the output that is marked as such (or a new change output is added if none is marked). For the input amount calculation to be correct, the template must have the WitnessUtxo field set for all inputs. Any inputs already specified in the PSBT must already be locked (if they belong to this node), only newly added inputs will be locked by this RPC.
oneof change_output
int32 existing_output_index = 2
Use the existing output within the template PSBT with the specified index as the change output. Any leftover change will be added to the already specified amount of that output. To add a new change output to the PSBT, set the "add" field below instead. The type of change output added is defined by change_type in the parent message.
bool add = 3
Add a new change output to the PSBT using the change_type specified in the parent message.
message
walletkit.proto:1801Used as request type in: WalletKit.SignPsbt
Used as field type in:
bytes funded_psbt = 1
The PSBT that should be signed. The PSBT must contain all required inputs, outputs, UTXO data and custom fields required to identify the signing key.
message
walletkit.proto:1809Used as response type in: WalletKit.SignPsbt
Used as field type in:
bytes signed_psbt = 1
The signed transaction in PSBT format.
repeated uint32 signed_inputs = 2
The indices of signed inputs.
message
walletkit.proto:956Used in:
string txid = 1
The transaction id (txid) in hex.
string error = 2
If non-empty, the reason this transaction was rejected.
string other_wtxid = 3
If non-empty, the wtxid (in hex) of a transaction with the same txid but a different witness that was already in the mempool; the submitted transaction was ignored as a duplicate (witness replacement).
message
walletkit.proto:888Used in: ,
uint32 leaf_version = 1
The leaf version. Should be 0xc0 (192) in case of a SegWit v1 script.
bytes script = 2
The script of the tap leaf.
message
walletkit.proto:881Used in:
repeated all_leaves = 1
The complete, ordered list of all tap leaves of the tree.
message
walletkit.proto:896Used in:
optional revealed_leaf = 1
The tap leaf that is known and will be revealed.
bytes full_inclusion_proof = 2
The BIP-0341 serialized inclusion proof that is required to prove that the revealed leaf is part of the tree. This contains 0..n blocks of 32 bytes. If the tree only contained a single leaf (which is the revealed leaf), this can be empty.
message
walletkit.proto:1713Used in:
repeated inputs = 1
An optional list of inputs to use. Every input must be an UTXO known to the wallet that has not been locked before. The sum of all inputs must be sufficiently greater than the sum of all outputs to pay a miner fee with the fee rate specified in the parent message. If no inputs are specified, coin selection will be performed instead and inputs of sufficient value will be added to the resulting PSBT.
map<string, uint64> outputs = 2
A map of all addresses and the amounts to send to in the funded PSBT.
message
walletkit.proto:1763Used in: ,
bytes id = 1
A 32 byte random ID that identifies the lease.
optional outpoint = 2
The identifying outpoint of the output being leased.
uint64 expiration = 3
The absolute expiration of a time-controlled output lease represented as a unix timestamp. Confirmation-controlled leases retain this value for compatibility but do not apply it.
bytes pk_script = 4
The public key script of the leased output.
uint64 value = 5
The value of the leased output in satoshis.
uint32 release_after_spend_confs = 6
The spend maturity depth recorded for this lease. FundPsbt returns it only after the wallet successfully applies the requested option.
int32 confirmed_spend_height = 7
The block height where the spending transaction first confirmed. Zero means no confirmed spend was observed. A negative value means a previously observed spend was disconnected and is awaiting reconfirmation. The only negative value emitted is -1; its magnitude carries no additional information.
Used in:
UNKNOWN_WITNESS = 0
COMMITMENT_TIME_LOCK = 1
A witness that allows us to spend the output of a commitment transaction after a relative lock-time lockout.
COMMITMENT_NO_DELAY = 2
A witness that allows us to spend a settled no-delay output immediately on a counterparty's commitment transaction.
COMMITMENT_REVOKE = 3
A witness that allows us to sweep the settled output of a malicious counterparty's who broadcasts a revoked commitment transaction.
HTLC_OFFERED_REVOKE = 4
A witness that allows us to sweep an HTLC which we offered to the remote party in the case that they broadcast a revoked commitment state.
HTLC_ACCEPTED_REVOKE = 5
A witness that allows us to sweep an HTLC output sent to us in the case that the remote party broadcasts a revoked commitment state.
HTLC_OFFERED_TIMEOUT_SECOND_LEVEL = 6
A witness that allows us to sweep an HTLC output that we extended to a party, but was never fulfilled. This HTLC output isn't directly on the commitment transaction, but is the result of a confirmed second-level HTLC transaction. As a result, we can only spend this after a CSV delay.
HTLC_ACCEPTED_SUCCESS_SECOND_LEVEL = 7
A witness that allows us to sweep an HTLC output that was offered to us, and for which we have a payment preimage. This HTLC output isn't directly on our commitment transaction, but is the result of confirmed second-level HTLC transaction. As a result, we can only spend this after a CSV delay.
HTLC_OFFERED_REMOTE_TIMEOUT = 8
A witness that allows us to sweep an HTLC that we offered to the remote party which lies in the commitment transaction of the remote party. We can spend this output after the absolute CLTV timeout of the HTLC as passed.
HTLC_ACCEPTED_REMOTE_SUCCESS = 9
A witness that allows us to sweep an HTLC that was offered to us by the remote party. We use this witness in the case that the remote party goes to chain, and we know the pre-image to the HTLC. We can sweep this without any additional timeout.
HTLC_SECOND_LEVEL_REVOKE = 10
A witness that allows us to sweep an HTLC from the remote party's commitment transaction in the case that the broadcast a revoked commitment, but then also immediately attempt to go to the second level to claim the HTLC.
WITNESS_KEY_HASH = 11
A witness type that allows us to spend a regular p2wkh output that's sent to an output which is under complete control of the backing wallet.
NESTED_WITNESS_KEY_HASH = 12
A witness type that allows us to sweep an output that sends to a nested P2SH script that pays to a key solely under our control.
COMMITMENT_ANCHOR = 13
A witness type that allows us to spend our anchor on the commitment transaction.
COMMITMENT_NO_DELAY_TWEAKLESS = 14
A witness type that is similar to the COMMITMENT_NO_DELAY type, but it omits the tweak that randomizes the key we need to spend with a channel peer supplied set of randomness.
COMMITMENT_TO_REMOTE_CONFIRMED = 15
A witness type that allows us to spend our output on the counterparty's commitment transaction after a confirmation.
HTLC_OFFERED_TIMEOUT_SECOND_LEVEL_INPUT_CONFIRMED = 16
A witness type that allows us to sweep an HTLC output that we extended to a party, but was never fulfilled. This _is_ the HTLC output directly on our commitment transaction, and the input to the second-level HTLC timeout transaction. It can only be spent after CLTV expiry, and commitment confirmation.
HTLC_ACCEPTED_SUCCESS_SECOND_LEVEL_INPUT_CONFIRMED = 17
A witness type that allows us to sweep an HTLC output that was offered to us, and for which we have a payment preimage. This _is_ the HTLC output directly on our commitment transaction, and the input to the second-level HTLC success transaction. It can only be spent after the commitment has confirmed.
LEASE_COMMITMENT_TIME_LOCK = 18
A witness type that allows us to spend our output on our local commitment transaction after a relative and absolute lock-time lockout as part of the script enforced lease commitment type.
LEASE_COMMITMENT_TO_REMOTE_CONFIRMED = 19
A witness type that allows us to spend our output on the counterparty's commitment transaction after a confirmation and absolute locktime as part of the script enforced lease commitment type.
LEASE_HTLC_OFFERED_TIMEOUT_SECOND_LEVEL = 20
A witness type that allows us to sweep an HTLC output that we extended to a party, but was never fulfilled. This HTLC output isn't directly on the commitment transaction, but is the result of a confirmed second-level HTLC transaction. As a result, we can only spend this after a CSV delay and CLTV locktime as part of the script enforced lease commitment type.
LEASE_HTLC_ACCEPTED_SUCCESS_SECOND_LEVEL = 21
A witness type that allows us to sweep an HTLC output that was offered to us, and for which we have a payment preimage. This HTLC output isn't directly on our commitment transaction, but is the result of confirmed second-level HTLC transaction. As a result, we can only spend this after a CSV delay and CLTV locktime as part of the script enforced lease commitment type.
TAPROOT_PUB_KEY_SPEND = 22
A witness type that allows us to spend a regular p2tr output that's sent to an output which is under complete control of the backing wallet.
TAPROOT_LOCAL_COMMIT_SPEND = 23
A witness type that allows us to spend our settled local commitment after a CSV delay when we force close the channel.
TAPROOT_REMOTE_COMMIT_SPEND = 24
A witness type that allows us to spend our settled local commitment after a CSV delay when the remote party has force closed the channel.
TAPROOT_ANCHOR_SWEEP_SPEND = 25
A witness type that we'll use for spending our own anchor output.
TAPROOT_HTLC_OFFERED_TIMEOUT_SECOND_LEVEL = 26
A witness that allows us to timeout an HTLC we offered to the remote party on our commitment transaction. We use this when we need to go on chain to time out an HTLC.
TAPROOT_HTLC_ACCEPTED_SUCCESS_SECOND_LEVEL = 27
A witness type that allows us to sweep an HTLC we accepted on our commitment transaction after we go to the second level on chain.
TAPROOT_HTLC_SECOND_LEVEL_REVOKE = 28
A witness that allows us to sweep an HTLC on the revoked transaction of the remote party that goes to the second level.
TAPROOT_HTLC_ACCEPTED_REVOKE = 29
A witness that allows us to sweep an HTLC sent to us by the remote party in the event that they broadcast a revoked state.
TAPROOT_HTLC_OFFERED_REVOKE = 30
A witness that allows us to sweep an HTLC we offered to the remote party if they broadcast a revoked commitment.
TAPROOT_HTLC_OFFERED_REMOTE_TIMEOUT = 31
A witness that allows us to sweep an HTLC we offered to the remote party that lies on the commitment transaction for the remote party. We can spend this output after the absolute CLTV timeout of the HTLC as passed.
TAPROOT_HTLC_LOCAL_OFFERED_TIMEOUT = 32
A witness type that allows us to sign the second level HTLC timeout transaction when spending from an HTLC residing on our local commitment transaction. This is used by the sweeper to re-sign inputs if it needs to aggregate several second level HTLCs.
TAPROOT_HTLC_ACCEPTED_REMOTE_SUCCESS = 33
A witness that allows us to sweep an HTLC that was offered to us by the remote party for a taproot channels. We use this witness in the case that the remote party goes to chain, and we know the pre-image to the HTLC. We can sweep this without any additional timeout.
TAPROOT_HTLC_ACCEPTED_LOCAL_SUCCESS = 34
A witness type that allows us to sweep the HTLC offered to us on our local commitment transaction. We'll use this when we need to go on chain to sweep the HTLC. In this case, this is the second level HTLC success transaction.
TAPROOT_COMMITMENT_REVOKE = 35
A witness that allows us to sweep the settled output of a malicious counterparty's who broadcasts a revoked taproot commitment transaction.
TAPROOT_LOCAL_COMMIT_SPEND_FINAL = 36
A witness type that allows us to spend our settled local commitment after a CSV delay when we force close a production taproot channel.
TAPROOT_REMOTE_COMMIT_SPEND_FINAL = 37
A witness type that allows us to spend our settled local commitment after a CSV delay when the remote party has force closed a production taproot channel.
TAPROOT_HTLC_OFFERED_TIMEOUT_SECOND_LEVEL_FINAL = 38
A witness that allows us to timeout an HTLC we offered to the remote party on our production taproot commitment transaction. We use this when we need to go on chain to time out an HTLC.
TAPROOT_HTLC_ACCEPTED_SUCCESS_SECOND_LEVEL_FINAL = 39
A witness type that allows us to sweep an HTLC we accepted on our production taproot commitment transaction after we go to the second level on chain.
TAPROOT_HTLC_OFFERED_REMOTE_TIMEOUT_FINAL = 40
A witness that allows us to sweep an HTLC we offered to the remote party that lies on the production taproot commitment transaction for the remote party. We can spend this output after the absolute CLTV timeout of the HTLC as passed.
TAPROOT_HTLC_ACCEPTED_REMOTE_SUCCESS_FINAL = 41
A witness that allows us to sweep an HTLC that was offered to us by the remote party for a production taproot channel. We use this witness in the case that the remote party goes to chain, and we know the pre-image to the HTLC. We can sweep this without any additional timeout.
TAPROOT_COMMITMENT_REVOKE_FINAL = 42
A witness type that allows us to sweep the settled output of a malicious counterparty's who broadcasts a revoked production taproot commitment transaction.