|Joost Jager 3e960b8b54||2 years ago|
|cmd||2 years ago|
|docs||2 years ago|
|lndclient||2 years ago|
|loopdb||2 years ago|
|looprpc||2 years ago|
|swap||2 years ago|
|sweep||2 years ago|
|test||2 years ago|
|.gitignore||2 years ago|
|.travis.yml||2 years ago|
|LICENSE||2 years ago|
|Makefile||2 years ago|
|README.md||2 years ago|
|client.go||2 years ago|
|client_test.go||2 years ago|
|config.go||2 years ago|
|executor.go||2 years ago|
|go.mod||2 years ago|
|go.sum||2 years ago|
|interface.go||2 years ago|
|log.go||2 years ago|
|loopin.go||2 years ago|
|loopin_test.go||2 years ago|
|loopin_testcontext_test.go||2 years ago|
|loopout.go||2 years ago|
|loopout_test.go||2 years ago|
|release.sh||2 years ago|
|server_mock_test.go||2 years ago|
|store_mock_test.go||2 years ago|
|swap.go||2 years ago|
|swap_server_client.go||2 years ago|
|testcontext_test.go||2 years ago|
|uncharge_state.go||2 years ago|
|version.go||2 years ago|
Lightning Loop is a non-custodial service offered by Lightning Labs to bridge on-chain and off-chain Bitcoin using submarine swaps. This repository is home to the Loop client and depends on the Lightning Network daemon lnd. All of lnd’s supported chain backends are fully supported when using the Loop client: Neutrino, Bitcoin Core, and btcd.
In the current iteration of the Loop software, only off-chain to on-chain swaps are supported, where the Loop client sends funds off-chain in exchange for the funds back on-chain. This is called a Loop Out.
The service can be used in various situations:
Future iterations of the Loop software will also allow on-chain to off-chain swaps. These swaps can be useful for additional use-cases:
The Loop client is current in an early beta state, and offers a simple command line application. Future APIs will be added to support implementation or use of the Loop service.
LND and the loop client are using Go modules. Make sure that the
env variable is set to
In order to execute a swap, LND will need to be rebuilt on master with sub servers enabled.
Make sure that you are using the
master branch of lnd. You can get this by
git cloning the repository
git clone https://github.com/lightningnetwork/lnd.git
Once the lnd repository is cloned, it will need to be built with special build tags that enable the swap. This enables the required lnd rpc services.
cd lnd make install tags="signrpc walletrpc chainrpc"
Check to see if you have already installed lnd. If you have, you will need to
.macaroon files from your lnd directory.
Do not delete any other files other than the
// Example on Linux to see macaroons in the default directory: ls ~/.lnd/data/chain/bitcoin/mainnet
This should show no
.macaroon files. If it does? Stop lnd, delete macaroons,
Now delete the .macaroon files and restart lnd. (don't delete any other files)
After lnd is installed, you will need to clone the Lightning Loop repo and install the command line interface and swap client service.
git clone https://github.com/lightninglabs/loop.git cd loop/cmd go install ./...
After you have lnd and the Loop client installed, you can execute a Loop swap.
The Loop client needs its own short-lived daemon which will deal with the swaps in progress.
Command to start
loopd // Or if you want to do everything in the same terminal and background loopd loopd & // For testnet mode, you'll need to specify the network as mainnet is the default: loopd --network=testnet
loopd attempts to connect to the lnd instance running on
localhost:10009 and reads the macaroon and tls certificate from
This can be altered using command line flags. See
loopd only listens on localhost and uses an unencrypted and unauthenticated
Now that loopd is running, you can initiate a simple Loop Out. This will pay out Lightning off-chain funds and you will receive Bitcoin on-chain funds in return. There will be some chain and routing fees associated with this swap.
loop out <amt_in_satoshis>
This will take some time, as it requires an on-chain confirmation. When the
swap is initiated successfully,
loopd will see the process through.
To query in-flight swap statuses, run
loopd is terminated (or killed) for whatever reason, it will pickup
pending swaps after a restart.
Information about pending swaps is stored persistently in the swap database.
Its location is
It is possible to execute multiple swaps simultaneously. Just keep loopd running.