loop.md

June 3, 2026 · View on GitHub

CLI interface - loop

control plane for your loopd.

Usage:

$ loop [GLOBAL FLAGS] [COMMAND] [COMMAND FLAGS] [ARGUMENTS...]

Global flags:

NameDescriptionTypeDefault valueEnvironment variables
--rpcserver="…"loopd daemon address host:portstringlocalhost:11010LOOPCLI_RPCSERVER
--network="…" (-n)the network loop is running on e.g. mainnet, testnet, etcstringmainnetLOOPCLI_NETWORK
--loopdir="…"path to loop's base directorystring~/.loopLOOPCLI_LOOPDIR
--tlscertpath="…"path to loop's TLS certificatestring~/.loop/mainnet/tls.certLOOPCLI_TLSCERTPATH
--macaroonpath="…"path to macaroon filestring~/.loop/mainnet/loop.macaroonLOOPCLI_MACAROONPATH
--help (-h)show helpboolfalsenone
--version (-v)print the versionboolfalsenone

out command

perform an off-chain to on-chain swap (looping out).

Attempts to loop out the target amount into either the backing lnd's wallet, or a targeted address. The amount is to be specified in satoshis. Optionally a BASE58/bech32 encoded bitcoin destination address may be specified. If not specified, a new wallet address will be generated.

Usage:

$ loop [GLOBAL FLAGS] out [COMMAND FLAGS] amt [addr]

The following flags are supported:

NameDescriptionTypeDefault value
--addr="…"the optional address that the looped out funds should be sent to, if let blank the funds will go to lnd's walletstring
--account="…"the name of the account to generate a new address from. You can list the names of valid accounts in your backing lnd instance with "lncli wallet accounts list"string
--account_addr_type="…"the address type of the extended public key specified in account. Currently only pay-to-taproot-pubkey(p2tr) is supportedstringp2tr
--amt="…"the amount in satoshis to loop out. To check for the minimum and maximum amounts to loop out please consult "loop terms"uint0
--htlc_confs="…"the number of confirmations (in blocks) that we require for the htlc extended by the server before we reveal the preimageuint1
--conf_target="…"the number of blocks from the swap initiation height that the on-chain HTLC should be swept withinuint9
--max_swap_routing_fee="…"the max off-chain swap routing fee in satoshis, if not specified, a default max fee will be usedint0
--fastindicate you want to swap immediately, paying potentially a higher fee. If not set the swap server might choose to wait up to 30 minutes before publishing the swap HTLC on-chain, to save on its chain fees. Not setting this flag therefore might result in a lower swap feeboolfalse
--payment_timeout="…"the timeout for each individual off-chain payment attempt. If not set, the default timeout of 1 hour will be used. As the payment might be retried, the actual total time may be longerduration0s
--asset_id="…"the asset ID of the asset to loop out, if this is set, the loop daemon will require a connection to a taproot assets daemonstring
--asset_edge_node="…"the pubkey of the edge node of the asset to loop out, this is required if the taproot assets daemon has multiple channels of the given asset id with different edge nodesstring
--forceAssumes yes during confirmation. Using this option will result in an immediate swapboolfalse
--label="…"an optional label for this swap,limited to 500 characters. The label may not start with our reserved prefix: [reserved]string
--verbose (-v)show expanded detailsboolfalse
--channel="…"the comma-separated list of short channel IDs of the channels to loop outstring
--help (-h)show helpboolfalse

out sweephtlc subcommand

sweep an HTLC output using the preimage success path.

Usage:

$ loop [GLOBAL FLAGS] out sweephtlc [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--outpoint="…"htlc outpoint to sweep (format: txid:vout)string
--htlcaddr="…"htlc address corresponding to the outpointstring
--feerate="…"fee rate to use in sat/vbyteuint0
--destaddr="…"optional destination address; defaults to a new wallet addressstring
--preimage="…"optional preimage hex to override stored swap preimagestring
--publishpublish the sweep transaction immediatelyboolfalse
--help (-h)show helpboolfalse

in command

perform an on-chain to off-chain swap (loop in).

Send the amount in satoshis specified by the amt argument off-chain. By default the swap client will create and broadcast the on-chain htlc. The fee priority of this transaction can optionally be set using the conf_target flag. The external flag can be set to publish the on chain htlc independently. Note that this flag cannot be set with the conf_target flag.

Usage:

$ loop [GLOBAL FLAGS] in [COMMAND FLAGS] amt

The following flags are supported:

NameDescriptionTypeDefault value
--amt="…"the amount in satoshis to loop in. To check for the minimum and maximum amounts to loop in please consult "loop terms"uint0
--externalexpect htlc to be published externallyboolfalse
--conf_target="…"the target number of blocks the on-chain htlc broadcast by the swap client should confirm withinuint0
--last_hop="…"the pubkey of the last hop to use for this swapstring
--label="…"an optional label for this swap,limited to 500 characters. The label may not start with our reserved prefix: [reserved]string
--forceAssumes yes during confirmation. Using this option will result in an immediate swapboolfalse
--verbose (-v)show expanded detailsboolfalse
--route_hints="…"route hints that can each be individually used to assist in reaching the invoice's destinationstring[]
--privategenerates and passes routehints. Should be used if the connected node is only reachable via private channelsboolfalse
--help (-h)show helpboolfalse

terms command

Display the current swap terms imposed by the server.

Usage:

$ loop [GLOBAL FLAGS] terms [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

monitor command

monitor progress of any active swaps.

Allows the user to monitor progress of any active swaps.

Usage:

$ loop [GLOBAL FLAGS] monitor [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

quote command

get a quote for the cost of a swap.

Usage:

$ loop [GLOBAL FLAGS] quote [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

quote in subcommand

get a quote for the cost of a loop in swap.

Allows to determine the cost of a swap up front.Either specify an amount or deposit outpoints.

Usage:

$ loop [GLOBAL FLAGS] quote in [COMMAND FLAGS] amt

The following flags are supported:

NameDescriptionTypeDefault value
--last_hop="…"the pubkey of the last hop to use for the quotestring
--conf_target="…"the target number of blocks the on-chain htlc broadcast by the swap client should confirm withinuint0
--verbose (-v)show expanded detailsboolfalse
--privategenerates and passes routehints. Should be used if the connected node is only reachable via private channelsboolfalse
--route_hints="…"route hints that can each be individually used to assist in reaching the invoice's destinationstring[]
--deposit_outpoint="…"one or more static address deposit outpoints to quote for. Deposit outpoints are not to be used in combination with an amount. Eachadditional outpoint can be added by specifying --deposit_outpoint tx_id:idxstring[]
--help (-h)show helpboolfalse

quote out subcommand

get a quote for the cost of a loop out swap.

Allows to determine the cost of a swap up front.

Usage:

$ loop [GLOBAL FLAGS] quote out [COMMAND FLAGS] amt

The following flags are supported:

NameDescriptionTypeDefault value
--conf_target="…"the number of blocks from the swap initiation height that the on-chain HTLC should be swept within in a Loop Outuint9
--fastIndicate you want to swap immediately, paying potentially a higher fee. If not set the swap server might choose to wait up to 30 minutes before publishing the swap HTLC on-chain, to save on chain fees. Not setting this flag might result in a lower swap feeboolfalse
--verbose (-v)show expanded detailsboolfalse
--help (-h)show helpboolfalse

listauth command

list all L402 tokens.

Shows a list of all L402 tokens that loopd has paid for.

Usage:

$ loop [GLOBAL FLAGS] listauth [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

fetchl402 command

fetches a new L402 authentication token from the server.

Fetches a new L402 authentication token from the server. This token is required to listen to notifications from the server, such as reservation notifications. If a L402 is already present in the store, this command is a no-op.

Usage:

$ loop [GLOBAL FLAGS] fetchl402 [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

listswaps command

list all swaps in the local database.

Allows the user to get a list of all swaps that are currently stored in the database.

Usage:

$ loop [GLOBAL FLAGS] listswaps [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--loop_out_onlyonly list swaps that are loop out swapsboolfalse
--loop_in_onlyonly list swaps that are loop in swapsboolfalse
--pending_onlyonly list pending swapsboolfalse
--label="…"an optional label for this swap,limited to 500 characters. The label may not start with our reserved prefix: [reserved]string
--channel="…"the comma-separated list of short channel IDs of the channels to loop outstring
--last_hop="…"the pubkey of the last hop to use for this swapstring
--max_swaps="…"Max number of swaps to return after filteringuint0
--start_time_ns="…"Unix timestamp in nanoseconds to select swaps initiated after this timeint0
--help (-h)show helpboolfalse

swapinfo command

show the status of a swap.

Allows the user to get the status of a single swap currently stored in the database.

Usage:

$ loop [GLOBAL FLAGS] swapinfo [COMMAND FLAGS] id

The following flags are supported:

NameDescriptionTypeDefault value
--id="…"the ID of the swapuint0
--help (-h)show helpboolfalse

getparams command

show liquidity manager parameters.

Displays the current set of parameters that are set for the liquidity manager.

Usage:

$ loop [GLOBAL FLAGS] getparams [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

setrule command

set liquidity manager rule for a channel/peer.

Update or remove the liquidity rule for a channel/peer.

Usage:

$ loop [GLOBAL FLAGS] setrule [COMMAND FLAGS] {shortchanid | peerpubkey}

The following flags are supported:

NameDescriptionTypeDefault value
--type="…"the type of swap to perform, set to 'out' for acquiring inbound liquidity or 'in' for acquiring outbound liquiditystringout
--incoming_threshold="…"the minimum percentage of incoming liquidity to total capacity beneath which to recommend loop out to acquire incomingint0
--outgoing_threshold="…"the minimum percentage of outbound liquidity that we do not want to drop belowint0
--clearremove the rule currently set for the channel/peerboolfalse
--help (-h)show helpboolfalse

suggestswaps command

show a list of suggested swaps.

Displays a list of suggested swaps that aim to obtain the liquidity balance as specified by the rules set in the liquidity manager.

Usage:

$ loop [GLOBAL FLAGS] suggestswaps [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

setparams command

update the parameters set for the liquidity manager.

Updates the parameters set for the liquidity manager. Note the parameters are persisted in db to save the trouble of setting them again upon loopd restart. To get the defaultvalues, use getparams before any setparams.

Usage:

$ loop [GLOBAL FLAGS] setparams [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--sweeplimit="…"the limit placed on our estimated sweep fee in sat/vByteint0
--feepercent="…"the maximum percentage of swap amount to be used across all fee categoriesfloat0
--maxswapfee="…"the maximum percentage of swap volume we are willing to pay in server feesfloat0
--maxroutingfee="…"the maximum percentage of off-chain payment volume that we are willing to pay in routingfeesfloat0
--maxprepayfee="…"the maximum percentage of off-chain prepay volume that we are willing to pay in routing feesfloat0
--maxprepay="…"the maximum no-show (prepay) in satoshis that swap suggestions should be limited touint0
--maxminer="…"the maximum miner fee in satoshis that swap suggestions should be limited touint0
--sweepconf="…"the number of blocks from htlc height that swap suggestion sweeps should target, used to estimate max miner feeint0
--failurebackoff="…"the amount of time, in seconds, that should pass before a channel that previously had a failed swap will be included in suggestionsuint0
--autoloopset to true to enable automated dispatch of swaps, limited to the budget set by autobudgetboolfalse
--destaddr="…"custom address to be used as destination for autoloop loop out, set to "default" in order to revert to default behaviorstring
--account="…"the name of the account to generate a new address from. You can list the names of valid accounts in your backing lnd instance with "lncli wallet accounts list"string
--account_addr_type="…"the address type of the extended public key specified in account. Currently only pay-to-taproot-pubkey(p2tr) is supportedstringp2tr
--autobudget="…"the maximum amount of fees in satoshis that automatically dispatched loop out swaps may spenduint0
--autobudgetrefreshperiod="…"the time period over which the automated loop budget is refreshedduration0s
--autoinflight="…"the maximum number of automatically dispatched swaps that we allow to be in flightuint0
--minamt="…"the minimum amount in satoshis that the autoloop client will dispatch per-swapuint0
--maxamt="…"the maximum amount in satoshis that the autoloop client will dispatch per-swapuint0
--htlc_conf="…"the confirmation target for loop in on-chain htlcsint0
--loopinsource="…"the loop-in source to use for autoloop rules: wallet or static-address. Static-address requires loopd --experimentalstring
--easyautoloopset to true to enable easy autoloop, which will automatically dispatch swaps in order to meet the target local balanceboolfalse
--localbalancesat="…"the target size of total local balance in satoshis, used by easy autoloopuint0
--easyautoloop_excludepeer="…"list of peer pubkeys (hex) to exclude from easy autoloop channel selection; repeat --easyautoloop_excludepeer for multiple peersstring[]
--easyatutoloop_includeallpeersinclude all peers back into easy autoloop by clearing the exclusion list. It cannot be combined with --easyautoloop_excludepeerboolfalse
--asset_easyautoloopset to true to enable asset easy autoloop, which will automatically dispatch asset swaps in order to meet the target local balanceboolfalse
--asset_id="…"If set to a valid asset ID, the easyautoloop and localbalancesat flags will be set for the specified assetstring
--asset_localbalance="…"the target size of total local balance in asset units, used by asset easy autoloopuint0
--fastif set new swaps are expected to be published immediately, paying a potentially higher fee. If not set the swap server might choose to wait up to 30 minutes before publishing swap HTLCs on-chain, to save on chain fees. Not setting this flag therefore might result in a lower swap feesboolfalse
--help (-h)show helpboolfalse

getinfo command

show general information about the loop daemon.

Displays general information about the daemon like current version, connection parameters and basic swap information.

Usage:

$ loop [GLOBAL FLAGS] getinfo [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

abandonswap command

abandon a swap with a given swap hash.

This command overrides the database and abandons a swap with a given swap hash. !!! This command might potentially lead to loss of funds if it is applied to swaps that are still waiting for pending user funds. Before executing this command make sure that no funds are locked by the swap.

Usage:

$ loop [GLOBAL FLAGS] abandonswap [COMMAND FLAGS] ID

The following flags are supported:

NameDescriptionTypeDefault value
--i_know_what_i_am_doingSpecify this flag if you made sure that you read and understood the following consequence of applying this commandboolfalse
--help (-h)show helpboolfalse

reservations command (aliases: r)

manage reservations.

With loopd running, you can use this command to manage your reservations. Reservations are 2-of-2 multisig utxos that the loop server can open to clients. The reservations are used to enable instant swaps.

Usage:

$ loop [GLOBAL FLAGS] reservations [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

reservations list subcommand (aliases: l)

list all reservations.

List all reservations.

Usage:

$ loop [GLOBAL FLAGS] reservations list [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

instantout command

perform an instant off-chain to on-chain swap (looping out).

Attempts to instantly loop out into the backing lnd's wallet. The amount will be chosen via the cli.

Usage:

$ loop [GLOBAL FLAGS] instantout [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--channel="…"the comma-separated list of short channel IDs of the channels to loop outstring
--addr="…"the optional address that the looped out funds should be sent to, if let blank the funds will go to lnd's walletstring
--help (-h)show helpboolfalse

listinstantouts command

list all instant out swaps.

List all instant out swaps.

Usage:

$ loop [GLOBAL FLAGS] listinstantouts [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

stop command

stop the loop daemon.

Requests loopd to perform a graceful shutdown.

Usage:

$ loop [GLOBAL FLAGS] stop [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--waitwait until loopd fully shuts downboolfalse
--help (-h)show helpboolfalse

static command (aliases: s)

perform on-chain to off-chain swaps using static addresses.

Usage:

$ loop [GLOBAL FLAGS] static [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

static new subcommand (aliases: n)

Create a new static loop in address.

Requests a new static loop in address from the server. Funds that are sent to this address will be locked by a 2:2 multisig between us and the loop server, or a timeout path that we can sweep once it opens up. The funds can either be cooperatively spent with a signature from the server or looped in.

Usage:

$ loop [GLOBAL FLAGS] static new [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

static listunspent subcommand (aliases: l)

List unspent static address outputs.

List all unspent static address outputs.

Usage:

$ loop [GLOBAL FLAGS] static listunspent [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--min_confs="…"The minimum amount of confirmations an output should have to be listedint0
--max_confs="…"The maximum number of confirmations an output could have to be listedint0
--help (-h)show helpboolfalse

static listdeposits subcommand

Displays static address deposits. A filter can be applied to only show deposits in a specific state.

Usage:

$ loop [GLOBAL FLAGS] static listdeposits [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--filter="…"specify a filter to only display deposits in the specified state. Leaving out the filter returns all deposits. The state can be one of the following: deposited withdrawing withdrawn looping_in looped_in opening_channel channel_published publish_expired_deposit sweep_htlc_timeout htlc_timeout_swept wait_for_expiry_sweep expired failedstring
--help (-h)show helpboolfalse

static listwithdrawals subcommand

Display a summary of past withdrawals.

Usage:

$ loop [GLOBAL FLAGS] static listwithdrawals [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

static listswaps subcommand

Shows a list of static address swaps.

Usage:

$ loop [GLOBAL FLAGS] static listswaps [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

static withdraw subcommand (aliases: w)

Withdraw from static address deposits.

Withdraws from all or selected static address deposits by sweeping them to the internal wallet or an external address.

Usage:

$ loop [GLOBAL FLAGS] static withdraw [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--utxo="…"specify utxos as outpoints(tx:idx) which willbe withdrawnstring[]
--allwithdraws all static address depositsboolfalse
--dest_addr="…"the optional address that the withdrawn funds should be sent to, if let blank the funds will go to lnd's walletstring
--sat_per_vbyte="…"(optional) a manual fee expressed in sat/vbyte that should be used when crafting the transactionuint0
--amt="…" (--amount)the number of satoshis that should be withdrawn from the selected deposits. The change is sent back to the static addressuint0
--help (-h)show helpboolfalse

static summary subcommand (aliases: s)

Display a summary of static address related information.

Displays various static address related information about deposits, withdrawals, swaps and channel openings.

Usage:

$ loop [GLOBAL FLAGS] static summary [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--help (-h)show helpboolfalse

static in subcommand

Loop in funds from static address deposits.

Requests a loop-in swap based on static address deposits. After the creation of a static address funds can be sent to it. Once the funds are confirmed on-chain they can be swapped instantaneously. If deposited funds are not needed they can we withdrawn back to the local lnd wallet.

Usage:

$ loop [GLOBAL FLAGS] static in [COMMAND FLAGS] [amt] [--all | --utxo xxx:xx]

The following flags are supported:

NameDescriptionTypeDefault value
--utxo="…"specify the utxos of deposits as outpoints(tx:idx) that should be looped instring[]
--allloop in all static address depositsboolfalse
--payment_timeout="…"the maximum time in seconds that the server is allowed to take for the swap payment. The client can retry the swap with adjusted parameters after the payment timed outduration0s
--amt="…" (--amount)the number of satoshis that should be swapped from the selected deposits. If thereis change it is sent back to the static addressuint0
--fastUsage: complete the swap faster by paying a higher fee, so the change output is available soonerboolfalse
--max_swap_fee_sat="…"the maximum swap fee in satoshis. If set, the swap is rejected when the quoted fee exceeds this cap. The maximum allowed value is 10000000. On-chain fees for creating static deposits are unaffecteduint0
--max_swap_fee_ppm="…"the maximum swap fee expressed in parts per million of the swap amount. If set together with --max_swap_fee_sat the tighter cap is useduint0
--last_hop="…"the pubkey of the last hop to use for this swapstring
--label="…"an optional label for this swap,limited to 500 characters. The label may not start with our reserved prefix: [reserved]string
--route_hints="…"route hints that can each be individually used to assist in reaching the invoice's destinationstring[]
--privategenerates and passes routehints. Should be used if the connected node is only reachable via private channelsboolfalse
--forceAssumes yes during confirmation. Using this option will result in an immediate swapboolfalse
--verbose (-v)show expanded detailsboolfalse
--help (-h)show helpboolfalse

static openchannel subcommand

Open a channel to an existing peer.

Attempt to open a new channel to an existing peer with the key node-key. The channel will be initialized with local-amt satoshis locally and push-amt satoshis for the remote node. Note that the push-amt is deducted from the specified local-amt which implies that the local-amt must be greater than the push-amt. Also note that specifying push-amt means you give that amount to the remote node as part of the channel opening. Once the channel is open, a channelPoint (txid:vout) of the funding output is returned. If the remote peer supports the option upfront shutdown feature bit (query listpeers to see their supported feature bits), an address to enforce payout of funds on cooperative close can optionally be provided. Note that if you set this value, you will not be able to cooperatively close out to another address. One can also specify a short string memo to record some useful information about the channel using the --memo argument. This is stored locally only, and is purely for reference. It has no bearing on the channel's operation. Max allowed length is 500 characters.

Usage:

$ loop [GLOBAL FLAGS] static openchannel [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionTypeDefault value
--node_key="…"the identity public key of the target node/peer serialized in compressed formatstring
--local_amt="…"the number of satoshis the wallet should commit to the channelint0
--base_fee_msat="…"the base fee in milli-satoshis that will be charged for each forwarded HTLC, regardless of payment sizeuint0
--fee_rate_ppm="…"the fee rate ppm (parts per million) that will be charged proportionally based on the value of each forwarded HTLC, the lowest possible rate is 0 with a granularity of 0.000001 (millionths)uint0
--push_amt="…"the number of satoshis to give the remote side as part of the initial commitment state, this is equivalent to first opening a channel and sending the remote party funds, but done all in one stepint0
--sat_per_vbyte="…"(optional) a manual fee expressed in sat/vbyte that should be used when crafting the transactionuint0
--privatemake the channel private, such that it won't be announced to the greater network, and nodes other than the two channel endpoints must be explicitly told about it to be able to route through itboolfalse
--min_htlc_msat="…"(optional) the minimum value we will require for incoming HTLCs on the channelint0
--remote_csv_delay="…"(optional) the number of blocks we will require our channel counterparty to wait before accessing its funds in case of unilateral close. If this is not set, we will scale the value according to the channel sizeuint0
--max_local_csv="…"(optional) the maximum number of blocks that we will allow the remote peer to require we wait before accessing our funds in the case of a unilateral closeuint0
--close_address="…"(optional) an address to enforce payout of our funds to on cooperative close. Note that if this value is set on channel open, you will not be able to cooperatively close to a different addressstring
--remote_max_value_in_flight_msat="…"(optional) the maximum value in msat that can be pending within the channel at any given timeuint0
--channel_type="…"(optional) the type of channel to propose to the remote peer ("tweakless", "anchors", "taproot")string
--zero_conf(optional) whether a zero-conf channel open should be attemptedboolfalse
--scid_alias(optional) whether a scid-alias channel type should be negotiatedboolfalse
--remote_reserve_sats="…"(optional) the minimum number of satoshis we require the remote node to keep as a direct payment. If not specified, a default of 1% of the channel capacity will be useduint0
--memo="…"(optional) a note-to-self containing some useful information about the channel. This is stored locally only, and is purely for reference. It has no bearing on the channel's operation. Max allowed length is 500 charactersstring
--fundmaxif set, the wallet will attempt to commit the maximum possible local amount to the channel. This must not be set at the same time as local_amtboolfalse
--utxo="…"a utxo specified as outpoint(tx:idx) which will be used to fund a channel. This flag can be repeatedly used to fund a channel with a selection of utxos. The selected funds can either be entirely spent by specifying the fundmax flag or partially by selecting a fraction of the sum of the outpoints in local_amtstring[]
--help (-h)show helpboolfalse