Better testnet support

[kornpow]

When setting up loop to run on testnet, loop should adjust file paths appropriately. When I start loop in testnet mode, I should be able to run the command loop out using testnet.

Actual behavior
Either the software knows testnet or mainnet is running, or there should be a flag similar to lncli --network=testnet

To reproduce

Start Loop like so:

nohup loopd --lnd.host=$LND_NODE_IP --lnd.macaroonpath=$CRED_PATH/admin.macaroon --lnd.tlspath=$CRED_PATH/tls.cert --network=testnet > ~/loopd.log &

Try running a loop out:

loop out --amt=250000
[loop] unable to read macaroon path : open /home/lnuser/.loop/mainnet/loop.macaroon: no such file or directory

I have been able to work around this problem however by linking:

ln -s ~/.loop/testnet/ ~/.loop/mainnet

However once I do this, everything seems good!

System information

standalone

no

cli

Loop master

x64

ubuntu

[kornpow]

Also, something along similar lines, from the lightning Slack:

https://lightningcommunity.slack.com/team/U02J1F80F8A

bash-5.1# ./loopd --network=testnet
2021-10-19 18:50:16.244 [INF] LOOPD: Version: 0.15.0-beta commit=
2021-10-19 18:50:16.244 [INF] LNDC: Creating lnd connection to localhost:10009
2021-10-19 18:50:16.245 [INF] LNDC: Connected to lnd
loopd exited with an error: open /root/.lnd/data/chain/bitcoin/mainnet/admin.macaroon: no such file or directory

[carlaKC]

Looks like we need to update our defaults to use the networkStr in cmd/loop/main.

[arshbot]

there should be a flag similar to lncli --network=testnet

@sako0938 there is, it's on the loop command and not the out subcommand, which is why you may not have seen it.

The following will work and is consistent with with lncli

 loop --network=testnet out --amt=250000

[arshbot]

Also, something along similar lines, from the lightning Slack:

https://lightningcommunity.slack.com/team/U02J1F80F8A

bash-5.1# ./loopd --network=testnet
2021-10-19 18:50:16.244 [INF] LOOPD: Version: 0.15.0-beta commit=
2021-10-19 18:50:16.244 [INF] LNDC: Creating lnd connection to localhost:10009
2021-10-19 18:50:16.245 [INF] LNDC: Connected to lnd
loopd exited with an error: open /root/.lnd/data/chain/bitcoin/mainnet/admin.macaroon: no such file or directory

I wasn't able to reproduce this myself

Here are the commands I ran

# Start LND
$ docker pull lightninglabs/lnd
$ docker run -v lightninglabs:/lnd --name=lnd -d \
    -p 9735:9735 \
    -p 10009:10009 \
    lnzap/lnd:latest \
    --bitcoin.active \
    --bitcoin.testnet \
    --debuglevel=debug \
    --bitcoin.node=neutrino \
    --neutrino.connect=faucet.lightning.community \
    --autopilot.active \
    --rpclisten=0.0.0.0:10009
$ docker start lnd

# Copy's the dockers files over to local -- use bind mounts if you're not comfortable running this
$ docker cp $(docker ps | grep lnd |awk '{ print $1 }'):/lnd/.lnd/data/chain/bitcoin/testnet/ ~/.lnd/data/chain/bitcoin/

# Start loop
$ loopd --network=testnet \
  --debuglevel=debug \
  --lnd.macaroonpath=$HOME/.lnd/data/chain/bitcoin/testnet/admin.macaroon \
  --lnd.tlspath=$HOME/.lnd/tls.cert

[arshbot]

Although revisiting, it would be nice if ./loopd --network=testnet looked at the default testnet folder instead of the default mainnet folder. That way you wouldn't have to specify so much.

[arshbot]

Fixed lingering issues by #434