docs: update loop.md

Author: hieblmi

docs/loop.1

@@ -470,6 +470,8 @@ withdrawing
 withdrawn
 looping_in
 looped_in
+opening_channel
+channel_published
 publish_expired_deposit
 sweep_htlc_timeout
 htlc_timeout_swept
@@ -564,3 +566,71 @@ Loop in funds from static address deposits.
 .PP
 \fB--verbose, -v\fP: show expanded details
 
+.SS openchannel
+.PP
+Open a channel to a an existing peer.
+
+.PP
+\fB--base_fee_msat\fP="": the base fee in milli-satoshis that will be charged for each forwarded HTLC, regardless of payment size (default: 0)
+
+.PP
+\fB--channel_type\fP="": (optional) the type of channel to propose to the remote peer ("tweakless", "anchors", "taproot")
+
+.PP
+\fB--close_address\fP="": (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 \fInot\fP be able to cooperatively close to a different address.
+
+.PP
+\fB--fee_rate_ppm\fP="": 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) (default: 0)
+
+.PP
+\fB--fundmax\fP: if 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_amt
+
+.PP
+\fB--help, -h\fP: show help
+
+.PP
+\fB--local_amt\fP="": the number of satoshis the wallet should commit to the channel (default: 0)
+
+.PP
+\fB--max_local_csv\fP="": (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 close. (default: 0)
+
+.PP
+\fB--memo\fP="": (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 characters
+
+.PP
+\fB--min_htlc_msat\fP="": (optional) the minimum value we will require for incoming HTLCs on the channel (default: 0)
+
+.PP
+\fB--node_key\fP="": the identity public key of the target node/peer serialized in compressed format
+
+.PP
+\fB--private\fP: make 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 it
+
+.PP
+\fB--push_amt\fP="": 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 step (default: 0)
+
+.PP
+\fB--remote_csv_delay\fP="": (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 size (default: 0)
+
+.PP
+\fB--remote_max_value_in_flight_msat\fP="": (optional) the maximum value in msat that can be pending within the channel at any given time (default: 0)
+
+.PP
+\fB--remote_reserve_sats\fP="": (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 used. (default: 0)
+
+.PP
+\fB--sat_per_vbyte\fP="": (optional) a manual fee expressed in sat/vbyte that should be used when crafting the transaction (default: 0)
+
+.PP
+\fB--scid_alias\fP: (optional) whether a scid-alias channel type should be negotiated.
+
+.PP
+\fB--utxo\fP="": 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_amt (default: [])
+
+.PP
+\fB--zero_conf\fP: (optional) whether a zero-conf channel open should be attempted.
+