GITBOOK-338: change request with no subject merged in GitBook

Author: Leo Weese

Diff for: lightning-network-tools/loop/the-loop-cli.md

@@ -4,7 +4,7 @@ description: Understand fees in Lightning Loop and get the most out of it
 
 # The Loop CLI
 
-## Using Loop <a href="docs-internal-guid-0588c9ab-7fff-a9c6-0c68-1ad299980217" id="docs-internal-guid-0588c9ab-7fff-a9c6-0c68-1ad299980217"></a>
+## Using Loop <a href="#docs-internal-guid-0588c9ab-7fff-a9c6-0c68-1ad299980217" id="docs-internal-guid-0588c9ab-7fff-a9c6-0c68-1ad299980217"></a>
 
 As soon as Loop is running, you will be able to make use of the CLI. Depending on your installation, you will be able to run it simply by typing loop into your console, or navigate to where the binaries are stored and execute with `./loop`
 
@@ -14,6 +14,8 @@ We can start by requesting the latest Loop terms. The command `loop terms` shoul
 
 You can also use the command `loop getparams` to see current fees, prepaid amounts and [autoloop](autoloop.md) settings.
 
+
+
 ### Loop In fees
 
 We can also use the command `loop quote in 500000` to get a more precise quote for how much a swap would cost. For Loop In, we are making an on-chain transaction, for which we will have to pay the on-chain transaction fees. If we have enough satoshis in our on-chain LND wallet, Loop can give us a good estimate of these transaction fees as well. Either way, we can Loop In from our internal or external Bitcoin wallet.
@@ -30,19 +32,23 @@ The cost of sweeping the smart contract is quoted in satoshi as `htlc_sweep_fee_
 
 You can customize the command `loop in <amount in satoshis>`. For example, you could specify the channel that the Lightning payment should arrive in using the `--last_hop` parameter. The last hop is identified by the public key of a node. Make sure that you have an active channel with this node and plenty of incoming capacity. You can also specify a label with `--label`.
 
-If you are making the on-chain transaction from an external wallet, make sure to use the `--external` flag. You may set the transaction fees separately there too, or use the `--conf_target` value to a higher number for lower fees and longer processing times.
+You may set the transaction fees separately using this command, or use the `--conf_target` value to a higher number for lower fees and longer processing times.
 
 `loop in --last_hop 02e7a7d3c1e6055b7b7457d95e04d9bbd24f200fd4a58daca7beee7bc776e17440 --amt 295916`\
-Once you run the command, you are quoted the upper bound of the fees for this transaction. Loop will now obtain a LSAT for 1 satoshi and initiate the swap. You are then presented with an ID for the swap and two HTLC smart contract addresses. You may make your on-chain transaction to either of these two addresses, though P2WSH (starting with bc1) is recommended for maximum efficiency. The payment needs to be the exact amount and carry an appropriate transaction fee. There is no time limit with regard to when the on-chain payment has to confirm, but keep in mind that if you specify a channel into which the off-chain funds are to be deposited, the state of that channel might change over the next day or two.
+Once you run the command, you are quoted the upper bound of the fees for this transaction. Loop will now obtain a LSAT for 1 satoshi and initiate the swap.
 
 You can monitor the status of your Loop In with the command loop monitor. It will give you updates about your transaction. As soon as your on-chain transaction has one confirmation on the Blockchain, you should receive your off-chain transaction into the channel you specified.
 
+### External Loop In
+
+You can fund your Loop In with funds from any external wallet using the command line interface using the `--external` flag.
+
+Once you execute the `loop in` command, you are presented with two HTLC smart contract addresses in addition to the swap ID. You may make your on-chain transaction to either of these two addresses, though P2WSH (starting with bc1) is recommended for maximum efficiency. **The payment needs to be the exact amount and carry an appropriate transaction fee**. There is no time limit with regard to when the on-chain payment has to confirm, but keep in mind that if you specify a channel into which the off-chain funds are to be deposited, the state of that channel might change over the next day or two.
+
 ### Loop Out
 
 The Loop Out command requires a minimum amount of satoshis, typically around 250,000 satoshis. This value may increase in times of high on-chain fees and can be obtained using the `loop terms` command. You can optionally also specify which channel you want to loop out of using the `--channel` flag together with the short channel ID.
 
-By default, the on-chain transaction will arrive in your LND’s wallet. Alternatively, you can specify a Bitcoin address with the `--addr` flag.
-
 The speed of your swap is highly influenced by your willingness to pay with regard to fees. You can influence these fees in various ways. If you specify the `--fast` flag, the Loop server will publish its on-chain transaction quickly, but at a higher fee.
 
 Once this transaction is confirmed, you will need to sweep its address to your own wallet. This is usually done within 9 blocks, but can be done faster or slower by specifying the desired number of blocks with the `--conf_target` setting.
@@ -82,6 +88,10 @@ We will see two payments, first our 30,000 satoshi prepayment as specified in th
 
 We received 993,198 satoshi in our on-chain address.
 
+### External Loop Out
+
+By default, the on-chain transaction will arrive in your LND’s wallet. Alternatively, you can specify the Bitcoin address of any external wallet with the `--addr` flag.
+
 ## Use parameters as a frequent user
 
 We can set various parameters for our swaps with the command loop `setparams <options>`