GitHub - LightningPeach/lnd: Lightning Network Daemon ⚡️

Lightning Network Daemon

The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node and currently deployed on testnet3 - the Bitcoin Test Network. lnd has several pluggable back-end chain services including btcd (a full-node), bitcoind, and neutrino (a new experimental light client). The project's codebase uses the btcsuite set of Bitcoin libraries, and also exports a large set of isolated re-usable Lightning Network related libraries within it. In the current state lnd is capable of:

Creating channels.
Closing channels.
Completely managing all channel states (including the exceptional ones!).
Maintaining a fully authenticated+validated channel graph.
Performing path finding within the network, passively forwarding incoming payments.
Sending outgoing onion-encrypted payments through the network.
Updating advertised fee schedules.
Automatic channel management (autopilot).

Lightning Network Specification Compliance

lndfully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. The specifications are currently being drafted by several groups of implementers based around the world including the developers of lnd. The set of specification documents as well as our implementation of the specification are still a work-in-progress. With that said, the current status of lnd's BOLT compliance is:

Developer Resources

The daemon has been designed to be as developer friendly as possible in order to facilitate application development on top of lnd. Two primary RPC interfaces are exported: an HTTP REST API, and a gRPC service. The exported API's are not yet stable, so be warned: they may change drastically in the near future.

An automatically generated set of documentation for the RPC APIs can be found at api.lightning.community. A set of developer resources including talks, articles, and example applications can be found at: dev.lightning.community.

Finally, we also have an active Slack where protocol developers, application developers, testers and users gather to discuss various aspects of lnd and also Lightning in general.

Installation

In order to build from source, please see the installation instructions.

Docker

To run lnd from Docker, please see the main Docker instructions

IRC

irc.freenode.net
channel #lnd
webchat

Security

The developers of lnd take security very seriously. The disclosure of security vulnerabilities helps us secure the health of lnd, privacy of our users, and also the health of the Lightning Network as a whole. If you find any issues regarding security or privacy, please disclose the information responsibly by sending an email to security at lightning dot engineering, preferably encrypted using our designated PGP key (91FE464CD75101DA6B6BAB60555C6465E5BCB3AF) which can be found here.

Lightning Network Daemon

The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node and currently deployed on testnet3 - the Bitcoin Test Network. lnd has several pluggable back-end chain services including btcd (a full-node), bitcoind, and neutrino (a new experimental light client). The project's codebase uses the btcsuite set of Bitcoin libraries, and also exports a large set of isolated re-usable Lightning Network related libraries within it. In the current state lnd is capable of:

Creating channels.
Closing channels.
Completely managing all channel states (including the exceptional ones!).
Maintaining a fully authenticated+validated channel graph.
Performing path finding within the network, passively forwarding incoming payments.
Sending outgoing onion-encrypted payments through the network.
Updating advertised fee schedules.
Automatic channel management (autopilot).

Lightning Network Specification Compliance

lndfully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. The specifications are currently being drafted by several groups of implementers based around the world including the developers of lnd. The set of specification documents as well as our implementation of the specification are still a work-in-progress. With that said, the current status of lnd's BOLT compliance is:

Developer Resources

The daemon has been designed to be as developer friendly as possible in order to facilitate application development on top of lnd. Two primary RPC interfaces are exported: an HTTP REST API, and a gRPC service. The exported API's are not yet stable, so be warned: they may change drastically in the near future.

An automatically generated set of documentation for the RPC APIs can be found at api.lightning.community. A set of developer resources including talks, articles, and example applications can be found at: dev.lightning.community.

Finally, we also have an active Slack where protocol developers, application developers, testers and users gather to discuss various aspects of lnd and also Lightning in general.

Installation

In order to build from source, please see the installation instructions.

Docker

To run lnd from Docker, please see the main Docker instructions

IRC

irc.freenode.net
channel #lnd
webchat

Security

The developers of lnd take security very seriously. The disclosure of security vulnerabilities helps us secure the health of lnd, privacy of our users, and also the health of the Lightning Network as a whole. If you find any issues regarding security or privacy, please disclose the information responsibly by sending an email to security at lightning dot engineering, preferably encrypted using our designated PGP key (91FE464CD75101DA6B6BAB60555C6465E5BCB3AF) which can be found here.

Lightning Network Daemon

The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node and currently deployed on testnet3 - the Bitcoin Test Network. lnd has several pluggable back-end chain services including btcd (a full-node), bitcoind, and neutrino (a new experimental light client). The project's codebase uses the btcsuite set of Bitcoin libraries, and also exports a large set of isolated re-usable Lightning Network related libraries within it. In the current state lnd is capable of:

Creating channels.
Closing channels.
Completely managing all channel states (including the exceptional ones!).
Maintaining a fully authenticated+validated channel graph.
Performing path finding within the network, passively forwarding incoming payments.
Sending outgoing onion-encrypted payments through the network.
Updating advertised fee schedules.
Automatic channel management (autopilot).

Lightning Network Specification Compliance

lndfully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. The specifications are currently being drafted by several groups of implementers based around the world including the developers of lnd. The set of specification documents as well as our implementation of the specification are still a work-in-progress. With that said, the current status of lnd's BOLT compliance is:

Developer Resources

The daemon has been designed to be as developer friendly as possible in order to facilitate application development on top of lnd. Two primary RPC interfaces are exported: an HTTP REST API, and a gRPC service. The exported API's are not yet stable, so be warned: they may change drastically in the near future.

An automatically generated set of documentation for the RPC APIs can be found at api.lightning.community. A set of developer resources including talks, articles, and example applications can be found at: dev.lightning.community.

Finally, we also have an active Slack where protocol developers, application developers, testers and users gather to discuss various aspects of lnd and also Lightning in general.

Installation

In order to build from source, please see the installation instructions.

Docker

To run lnd from Docker, please see the main Docker instructions

IRC

irc.freenode.net
channel #lnd
webchat

Security

The developers of lnd take security very seriously. The disclosure of security vulnerabilities helps us secure the health of lnd, privacy of our users, and also the health of the Lightning Network as a whole. If you find any issues regarding security or privacy, please disclose the information responsibly by sending an email to security at lightning dot engineering, preferably encrypted using our designated PGP key (91FE464CD75101DA6B6BAB60555C6465E5BCB3AF) which can be found here.

Lightning Network Daemon

The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node and currently deployed on testnet3 - the Bitcoin Test Network. lnd has several pluggable back-end chain services including btcd (a full-node), bitcoind, and neutrino (a new experimental light client). The project's codebase uses the btcsuite set of Bitcoin libraries, and also exports a large set of isolated re-usable Lightning Network related libraries within it. In the current state lnd is capable of:

Creating channels.
Closing channels.
Completely managing all channel states (including the exceptional ones!).
Maintaining a fully authenticated+validated channel graph.
Performing path finding within the network, passively forwarding incoming payments.
Sending outgoing onion-encrypted payments through the network.
Updating advertised fee schedules.
Automatic channel management (autopilot).

Lightning Network Specification Compliance

lndfully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. The specifications are currently being drafted by several groups of implementers based around the world including the developers of lnd. The set of specification documents as well as our implementation of the specification are still a work-in-progress. With that said, the current status of lnd's BOLT compliance is:

Developer Resources

The daemon has been designed to be as developer friendly as possible in order to facilitate application development on top of lnd. Two primary RPC interfaces are exported: an HTTP REST API, and a gRPC service. The exported API's are not yet stable, so be warned: they may change drastically in the near future.

An automatically generated set of documentation for the RPC APIs can be found at api.lightning.community. A set of developer resources including talks, articles, and example applications can be found at: dev.lightning.community.

Finally, we also have an active Slack where protocol developers, application developers, testers and users gather to discuss various aspects of lnd and also Lightning in general.

Installation

In order to build from source, please see the installation instructions.

Docker

To run lnd from Docker, please see the main Docker instructions

IRC

irc.freenode.net
channel #lnd
webchat

Security

The developers of lnd take security very seriously. The disclosure of security vulnerabilities helps us secure the health of lnd, privacy of our users, and also the health of the Lightning Network as a whole. If you find any issues regarding security or privacy, please disclose the information responsibly by sending an email to security at lightning dot engineering, preferably encrypted using our designated PGP key (91FE464CD75101DA6B6BAB60555C6465E5BCB3AF) which can be found here.

Lightning Network Daemon

The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node and currently deployed on testnet3 - the Bitcoin Test Network. lnd has several pluggable back-end chain services including btcd (a full-node), bitcoind, and neutrino (a new experimental light client). The project's codebase uses the btcsuite set of Bitcoin libraries, and also exports a large set of isolated re-usable Lightning Network related libraries within it. In the current state lnd is capable of:

Creating channels.
Closing channels.
Completely managing all channel states (including the exceptional ones!).
Maintaining a fully authenticated+validated channel graph.
Performing path finding within the network, passively forwarding incoming payments.
Sending outgoing onion-encrypted payments through the network.
Updating advertised fee schedules.
Automatic channel management (autopilot).

Lightning Network Specification Compliance

lndfully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. The specifications are currently being drafted by several groups of implementers based around the world including the developers of lnd. The set of specification documents as well as our implementation of the specification are still a work-in-progress. With that said, the current status of lnd's BOLT compliance is:

Developer Resources

The daemon has been designed to be as developer friendly as possible in order to facilitate application development on top of lnd. Two primary RPC interfaces are exported: an HTTP REST API, and a gRPC service. The exported API's are not yet stable, so be warned: they may change drastically in the near future.

An automatically generated set of documentation for the RPC APIs can be found at api.lightning.community. A set of developer resources including talks, articles, and example applications can be found at: dev.lightning.community.

Finally, we also have an active Slack where protocol developers, application developers, testers and users gather to discuss various aspects of lnd and also Lightning in general.

Installation

In order to build from source, please see the installation instructions.

Docker

To run lnd from Docker, please see the main Docker instructions

IRC

irc.freenode.net
channel #lnd
webchat

Security

The developers of lnd take security very seriously. The disclosure of security vulnerabilities helps us secure the health of lnd, privacy of our users, and also the health of the Lightning Network as a whole. If you find any issues regarding security or privacy, please disclose the information responsibly by sending an email to security at lightning dot engineering, preferably encrypted using our designated PGP key (91FE464CD75101DA6B6BAB60555C6465E5BCB3AF) which can be found here.

Lightning Network Daemon

The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node and currently deployed on testnet3 - the Bitcoin Test Network. lnd has several pluggable back-end chain services including btcd (a full-node), bitcoind, and neutrino (a new experimental light client). The project's codebase uses the btcsuite set of Bitcoin libraries, and also exports a large set of isolated re-usable Lightning Network related libraries within it. In the current state lnd is capable of:

Creating channels.
Closing channels.
Completely managing all channel states (including the exceptional ones!).
Maintaining a fully authenticated+validated channel graph.
Performing path finding within the network, passively forwarding incoming payments.
Sending outgoing onion-encrypted payments through the network.
Updating advertised fee schedules.
Automatic channel management (autopilot).

Lightning Network Specification Compliance

lndfully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. The specifications are currently being drafted by several groups of implementers based around the world including the developers of lnd. The set of specification documents as well as our implementation of the specification are still a work-in-progress. With that said, the current status of lnd's BOLT compliance is:

Developer Resources

The daemon has been designed to be as developer friendly as possible in order to facilitate application development on top of lnd. Two primary RPC interfaces are exported: an HTTP REST API, and a gRPC service. The exported API's are not yet stable, so be warned: they may change drastically in the near future.

An automatically generated set of documentation for the RPC APIs can be found at api.lightning.community. A set of developer resources including talks, articles, and example applications can be found at: dev.lightning.community.

Finally, we also have an active Slack where protocol developers, application developers, testers and users gather to discuss various aspects of lnd and also Lightning in general.

Installation

In order to build from source, please see the installation instructions.

Docker

To run lnd from Docker, please see the main Docker instructions

IRC

irc.freenode.net
channel #lnd
webchat

Security

The developers of lnd take security very seriously. The disclosure of security vulnerabilities helps us secure the health of lnd, privacy of our users, and also the health of the Lightning Network as a whole. If you find any issues regarding security or privacy, please disclose the information responsibly by sending an email to security at lightning dot engineering, preferably encrypted using our designated PGP key (91FE464CD75101DA6B6BAB60555C6465E5BCB3AF) which can be found here.

Lightning Network Daemon

The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node and currently deployed on testnet3 - the Bitcoin Test Network. lnd has several pluggable back-end chain services including btcd (a full-node), bitcoind, and neutrino (a new experimental light client). The project's codebase uses the btcsuite set of Bitcoin libraries, and also exports a large set of isolated re-usable Lightning Network related libraries within it. In the current state lnd is capable of:

Creating channels.
Closing channels.
Completely managing all channel states (including the exceptional ones!).
Maintaining a fully authenticated+validated channel graph.
Performing path finding within the network, passively forwarding incoming payments.
Sending outgoing onion-encrypted payments through the network.
Updating advertised fee schedules.
Automatic channel management (autopilot).

Lightning Network Specification Compliance

lndfully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. The specifications are currently being drafted by several groups of implementers based around the world including the developers of lnd. The set of specification documents as well as our implementation of the specification are still a work-in-progress. With that said, the current status of lnd's BOLT compliance is:

Developer Resources

The daemon has been designed to be as developer friendly as possible in order to facilitate application development on top of lnd. Two primary RPC interfaces are exported: an HTTP REST API, and a gRPC service. The exported API's are not yet stable, so be warned: they may change drastically in the near future.

An automatically generated set of documentation for the RPC APIs can be found at api.lightning.community. A set of developer resources including talks, articles, and example applications can be found at: dev.lightning.community.

Finally, we also have an active Slack where protocol developers, application developers, testers and users gather to discuss various aspects of lnd and also Lightning in general.

Installation

In order to build from source, please see the installation instructions.

Docker

To run lnd from Docker, please see the main Docker instructions

IRC

irc.freenode.net
channel #lnd
webchat

Security

The developers of lnd take security very seriously. The disclosure of security vulnerabilities helps us secure the health of lnd, privacy of our users, and also the health of the Lightning Network as a whole. If you find any issues regarding security or privacy, please disclose the information responsibly by sending an email to security at lightning dot engineering, preferably encrypted using our designated PGP key (91FE464CD75101DA6B6BAB60555C6465E5BCB3AF) which can be found here.

Lightning Network Daemon

The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node and currently deployed on testnet3 - the Bitcoin Test Network. lnd has several pluggable back-end chain services including btcd (a full-node), bitcoind, and neutrino (a new experimental light client). The project's codebase uses the btcsuite set of Bitcoin libraries, and also exports a large set of isolated re-usable Lightning Network related libraries within it. In the current state lnd is capable of:

Creating channels.
Closing channels.
Completely managing all channel states (including the exceptional ones!).
Maintaining a fully authenticated+validated channel graph.
Performing path finding within the network, passively forwarding incoming payments.
Sending outgoing onion-encrypted payments through the network.
Updating advertised fee schedules.
Automatic channel management (autopilot).

Lightning Network Specification Compliance

lndfully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. The specifications are currently being drafted by several groups of implementers based around the world including the developers of lnd. The set of specification documents as well as our implementation of the specification are still a work-in-progress. With that said, the current status of lnd's BOLT compliance is:

Developer Resources

The daemon has been designed to be as developer friendly as possible in order to facilitate application development on top of lnd. Two primary RPC interfaces are exported: an HTTP REST API, and a gRPC service. The exported API's are not yet stable, so be warned: they may change drastically in the near future.

An automatically generated set of documentation for the RPC APIs can be found at api.lightning.community. A set of developer resources including talks, articles, and example applications can be found at: dev.lightning.community.

Finally, we also have an active Slack where protocol developers, application developers, testers and users gather to discuss various aspects of lnd and also Lightning in general.

Installation

In order to build from source, please see the installation instructions.

Docker

To run lnd from Docker, please see the main Docker instructions

IRC

irc.freenode.net
channel #lnd
webchat

Security

The developers of lnd take security very seriously. The disclosure of security vulnerabilities helps us secure the health of lnd, privacy of our users, and also the health of the Lightning Network as a whole. If you find any issues regarding security or privacy, please disclose the information responsibly by sending an email to security at lightning dot engineering, preferably encrypted using our designated PGP key (91FE464CD75101DA6B6BAB60555C6465E5BCB3AF) which can be found here.

Name		Name	Last commit message	Last commit date
.github		.github
aezeed		aezeed
autopilot		autopilot
brontide		brontide
build		build
chainntnfs		chainntnfs
channeldb		channeldb
cmd/lncli		cmd/lncli
contractcourt		contractcourt
contrib		contrib
discovery		discovery
docker		docker
docs		docs
htlcswitch		htlcswitch
keychain		keychain
lncfg		lncfg
lnpeer		lnpeer
lnrpc		lnrpc
lntest		lntest
lnwallet		lnwallet
lnwire		lnwire
macaroons		macaroons
make		make
multimutex		multimutex
nat		nat
queue		queue
routing		routing
shachain		shachain
signal		signal
sweep		sweep
ticker		ticker
tor		tor
walletunlocker		walletunlocker
watchtower		watchtower
zpay32		zpay32
.gitignore		.gitignore
.travis.yml		.travis.yml
Dockerfile		Dockerfile
Gopkg.lock		Gopkg.lock
Gopkg.toml		Gopkg.toml
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
breacharbiter.go		breacharbiter.go
breacharbiter_test.go		breacharbiter_test.go
chainparams.go		chainparams.go
chainregistry.go		chainregistry.go
chan_series.go		chan_series.go
chancloser.go		chancloser.go
config.go		config.go
doc.go		doc.go
fundingmanager.go		fundingmanager.go
fundingmanager_test.go		fundingmanager_test.go
invoiceregistry.go		invoiceregistry.go
lnd.go		lnd.go
lnd_test.go		lnd_test.go
log.go		log.go
logo.png		logo.png
mock.go		mock.go
nodesigner.go		nodesigner.go
nursery_store.go		nursery_store.go
nursery_store_test.go		nursery_store_test.go
peer.go		peer.go
peer_test.go		peer_test.go
pilot.go		pilot.go
release.sh		release.sh
rpcserver.go		rpcserver.go
sample-lnd.conf		sample-lnd.conf
server.go		server.go
server_test.go		server_test.go
test_utils.go		test_utils.go
utxonursery.go		utxonursery.go
utxonursery_test.go		utxonursery_test.go
witness_beacon.go		witness_beacon.go

Name		Name	Last commit message	Last commit date
.github		.github
aezeed		aezeed
autopilot		autopilot
brontide		brontide
build		build
chainntnfs		chainntnfs
channeldb		channeldb
cmd/lncli		cmd/lncli
contractcourt		contractcourt
contrib		contrib
discovery		discovery
docker		docker
docs		docs
htlcswitch		htlcswitch
keychain		keychain
lncfg		lncfg
lnpeer		lnpeer
lnrpc		lnrpc
lntest		lntest
lnwallet		lnwallet
lnwire		lnwire
macaroons		macaroons
make		make
multimutex		multimutex
nat		nat
queue		queue
routing		routing
shachain		shachain
signal		signal
sweep		sweep
ticker		ticker
tor		tor
walletunlocker		walletunlocker
watchtower		watchtower
zpay32		zpay32
.gitignore		.gitignore
.travis.yml		.travis.yml
Dockerfile		Dockerfile
Gopkg.lock		Gopkg.lock
Gopkg.toml		Gopkg.toml
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
breacharbiter.go		breacharbiter.go
breacharbiter_test.go		breacharbiter_test.go
chainparams.go		chainparams.go
chainregistry.go		chainregistry.go
chan_series.go		chan_series.go
chancloser.go		chancloser.go
config.go		config.go
doc.go		doc.go
fundingmanager.go		fundingmanager.go
fundingmanager_test.go		fundingmanager_test.go
invoiceregistry.go		invoiceregistry.go
lnd.go		lnd.go
lnd_test.go		lnd_test.go
log.go		log.go
logo.png		logo.png
mock.go		mock.go
nodesigner.go		nodesigner.go
nursery_store.go		nursery_store.go
nursery_store_test.go		nursery_store_test.go
peer.go		peer.go
peer_test.go		peer_test.go
pilot.go		pilot.go
release.sh		release.sh
rpcserver.go		rpcserver.go
sample-lnd.conf		sample-lnd.conf
server.go		server.go
server_test.go		server_test.go
test_utils.go		test_utils.go
utxonursery.go		utxonursery.go
utxonursery_test.go		utxonursery_test.go
witness_beacon.go		witness_beacon.go

Name		Name	Last commit message	Last commit date
.github		.github
aezeed		aezeed
autopilot		autopilot
brontide		brontide
build		build
chainntnfs		chainntnfs
channeldb		channeldb
cmd/lncli		cmd/lncli
contractcourt		contractcourt
contrib		contrib
discovery		discovery
docker		docker
docs		docs
htlcswitch		htlcswitch
keychain		keychain
lncfg		lncfg
lnpeer		lnpeer
lnrpc		lnrpc
lntest		lntest
lnwallet		lnwallet
lnwire		lnwire
macaroons		macaroons
make		make
multimutex		multimutex
nat		nat
queue		queue
routing		routing
shachain		shachain
signal		signal
sweep		sweep
ticker		ticker
tor		tor
walletunlocker		walletunlocker
watchtower		watchtower
zpay32		zpay32
.gitignore		.gitignore
.travis.yml		.travis.yml
Dockerfile		Dockerfile
Gopkg.lock		Gopkg.lock
Gopkg.toml		Gopkg.toml
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
breacharbiter.go		breacharbiter.go
breacharbiter_test.go		breacharbiter_test.go
chainparams.go		chainparams.go
chainregistry.go		chainregistry.go
chan_series.go		chan_series.go
chancloser.go		chancloser.go
config.go		config.go
doc.go		doc.go
fundingmanager.go		fundingmanager.go
fundingmanager_test.go		fundingmanager_test.go
invoiceregistry.go		invoiceregistry.go
lnd.go		lnd.go
lnd_test.go		lnd_test.go
log.go		log.go
logo.png		logo.png
mock.go		mock.go
nodesigner.go		nodesigner.go
nursery_store.go		nursery_store.go
nursery_store_test.go		nursery_store_test.go
peer.go		peer.go
peer_test.go		peer_test.go
pilot.go		pilot.go
release.sh		release.sh
rpcserver.go		rpcserver.go
sample-lnd.conf		sample-lnd.conf
server.go		server.go
server_test.go		server_test.go
test_utils.go		test_utils.go
utxonursery.go		utxonursery.go
utxonursery_test.go		utxonursery_test.go
witness_beacon.go		witness_beacon.go

Name		Name	Last commit message	Last commit date
.github		.github
aezeed		aezeed
autopilot		autopilot
brontide		brontide
build		build
chainntnfs		chainntnfs
channeldb		channeldb
cmd/lncli		cmd/lncli
contractcourt		contractcourt
contrib		contrib
discovery		discovery
docker		docker
docs		docs
htlcswitch		htlcswitch
keychain		keychain
lncfg		lncfg
lnpeer		lnpeer
lnrpc		lnrpc
lntest		lntest
lnwallet		lnwallet
lnwire		lnwire
macaroons		macaroons
make		make
multimutex		multimutex
nat		nat
queue		queue
routing		routing
shachain		shachain
signal		signal
sweep		sweep
ticker		ticker
tor		tor
walletunlocker		walletunlocker
watchtower		watchtower
zpay32		zpay32
.gitignore		.gitignore
.travis.yml		.travis.yml
Dockerfile		Dockerfile
Gopkg.lock		Gopkg.lock
Gopkg.toml		Gopkg.toml
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
breacharbiter.go		breacharbiter.go
breacharbiter_test.go		breacharbiter_test.go
chainparams.go		chainparams.go
chainregistry.go		chainregistry.go
chan_series.go		chan_series.go
chancloser.go		chancloser.go
config.go		config.go
doc.go		doc.go
fundingmanager.go		fundingmanager.go
fundingmanager_test.go		fundingmanager_test.go
invoiceregistry.go		invoiceregistry.go
lnd.go		lnd.go
lnd_test.go		lnd_test.go
log.go		log.go
logo.png		logo.png
mock.go		mock.go
nodesigner.go		nodesigner.go
nursery_store.go		nursery_store.go
nursery_store_test.go		nursery_store_test.go
peer.go		peer.go
peer_test.go		peer_test.go
pilot.go		pilot.go
release.sh		release.sh
rpcserver.go		rpcserver.go
sample-lnd.conf		sample-lnd.conf
server.go		server.go
server_test.go		server_test.go
test_utils.go		test_utils.go
utxonursery.go		utxonursery.go
utxonursery_test.go		utxonursery_test.go
witness_beacon.go		witness_beacon.go

Name		Name	Last commit message	Last commit date
.github		.github
aezeed		aezeed
autopilot		autopilot
brontide		brontide
build		build
chainntnfs		chainntnfs
channeldb		channeldb
cmd/lncli		cmd/lncli
contractcourt		contractcourt
contrib		contrib
discovery		discovery
docker		docker
docs		docs
htlcswitch		htlcswitch
keychain		keychain
lncfg		lncfg
lnpeer		lnpeer
lnrpc		lnrpc
lntest		lntest
lnwallet		lnwallet
lnwire		lnwire
macaroons		macaroons
make		make
multimutex		multimutex
nat		nat
queue		queue
routing		routing
shachain		shachain
signal		signal
sweep		sweep
ticker		ticker
tor		tor
walletunlocker		walletunlocker
watchtower		watchtower
zpay32		zpay32
.gitignore		.gitignore
.travis.yml		.travis.yml
Dockerfile		Dockerfile
Gopkg.lock		Gopkg.lock
Gopkg.toml		Gopkg.toml
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
breacharbiter.go		breacharbiter.go
breacharbiter_test.go		breacharbiter_test.go
chainparams.go		chainparams.go
chainregistry.go		chainregistry.go
chan_series.go		chan_series.go
chancloser.go		chancloser.go
config.go		config.go
doc.go		doc.go
fundingmanager.go		fundingmanager.go
fundingmanager_test.go		fundingmanager_test.go
invoiceregistry.go		invoiceregistry.go
lnd.go		lnd.go
lnd_test.go		lnd_test.go
log.go		log.go
logo.png		logo.png
mock.go		mock.go
nodesigner.go		nodesigner.go
nursery_store.go		nursery_store.go
nursery_store_test.go		nursery_store_test.go
peer.go		peer.go
peer_test.go		peer_test.go
pilot.go		pilot.go
release.sh		release.sh
rpcserver.go		rpcserver.go
sample-lnd.conf		sample-lnd.conf
server.go		server.go
server_test.go		server_test.go
test_utils.go		test_utils.go
utxonursery.go		utxonursery.go
utxonursery_test.go		utxonursery_test.go
witness_beacon.go		witness_beacon.go

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Lightning Network Daemon

Lightning Network Specification Compliance

Developer Resources

Installation

Docker

IRC

Security

Further reading

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Lightning Network Daemon

Lightning Network Specification Compliance

Developer Resources

Installation

Docker

IRC

Security

Further reading

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Lightning Network Daemon

Lightning Network Specification Compliance

Developer Resources

Installation

Docker

IRC

Security

Further reading

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Lightning Network Daemon

Lightning Network Specification Compliance

Developer Resources

Installation

Docker

IRC