Lightning Network Daemon
Go to file
2024-11-20 09:18:25 +01:00
.github
.vscode
aezeed
aliasmgr
amp
autopilot multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
batch
blockcache
brontide
buffer
build multi: update log file max num and size defaults 2024-10-30 13:30:04 +02:00
cert
chainntnfs chainntnfs: skip duplicate numConfsLeft notifications 2024-11-19 16:27:26 +08:00
chainreg multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
chanacceptor multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
chanbackup chanbackup+rpcserver+server: return number of recovered channels 2024-11-06 15:30:23 +01:00
chanfitness multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
channeldb chanfitness: exit early when there are no updates 2024-11-14 01:22:32 +08:00
channelnotifier multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
clock
cluster multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
cmd cmd/commands: fix custom message commands 2024-11-06 15:30:30 +01:00
contractcourt multi: introduce an option for resolutions 2024-11-20 09:18:24 +01:00
contrib
discovery multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
docker
docs docs: fix release notes 2024-11-19 21:09:15 +01:00
feature
fn fn: GoroutineManager.Go returns bool, not error 2024-11-14 15:03:25 -03:00
funding multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
graph multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
healthcheck healthcheck: bump btclog dep 2024-10-26 14:16:25 +02:00
htlcswitch Merge pull request #9240 from carlaKC/9166-mergeonly 2024-11-08 08:38:00 +02:00
input input: add new Preimage method to input.Input 2024-11-14 16:09:58 -08:00
internal/musig2v040
invoices invoices: cancel htlc on HtlcModify signal 2024-10-24 12:59:29 +02:00
itest itest: test "lnd --debuglevel=show" command 2024-11-19 12:44:57 -03:00
keychain
kvdb Revert "kvdb/postgres: remove global application level lock" 2024-10-28 09:35:18 +02:00
labels
lncfg multi: update more loggers to the v2 type 2024-10-22 17:03:56 +02:00
lnencrypt
lnmock
lnpeer
lnrpc routerrpc: fix sendpayment_v2 negative fee limit 2024-11-14 14:31:46 +01:00
lntest Merge pull request #9279 from ellemouton/misc 2024-11-19 10:37:01 +02:00
lntypes
lnutils
lnwallet multi: introduce an option for resolutions 2024-11-20 09:18:24 +01:00
lnwire lnwire: use assertEqualFunc in onion failure harness 2024-11-13 10:25:16 -06:00
macaroons lnwallet: populate resolution blob for incoming+outgoing HTLC resolutions 2024-11-14 16:09:57 -08:00
make
mobile
monitoring multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
msgmux multi: update more loggers to the v2 type 2024-10-22 17:03:56 +02:00
multimutex
nat
netann multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
peer peer+lnd: fix peer blocking on node shutdown 2024-11-18 18:49:34 +08:00
peernotifier multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
pool
protofsm protofsm: use new fn.GoroutineManager to manage goroutines 2024-11-18 20:49:01 -08:00
queue
record
routing multi: wait for rpcclients shutdown to complete 2024-11-14 01:22:31 +08:00
rpcperms multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
scripts scripts: dont check new config value. 2024-11-06 18:52:07 +01:00
shachain
signal multi: start updating various loggers to use the new v2 type 2024-10-22 17:03:55 +02:00
sqldb sqldb: update btclog dep 2024-10-26 14:18:00 +02:00
subscribe
sweep sweep: update storeRecord to include utxo index 2024-11-18 18:12:41 -08:00
ticker
tlv
tools
tor tor: update btclog dep 2024-10-26 14:18:32 +02:00
walletunlocker
watchtower Merge pull request #9281 from ziggie1984/export-towerclientdb-version 2024-11-19 17:53:14 +01:00
zpay32
.editorconfig
.gitignore gitignore: ignore vscode workspace files 2024-10-17 17:35:29 +02:00
.golangci.yml
.protolint.yaml
channel_notifier.go
chanrestore.go
config_builder.go multi: update more loggers to the v2 type 2024-10-22 17:03:56 +02:00
config_test.go
config.go config: improve error message 2024-11-19 12:44:57 -03:00
dev.Dockerfile
doc.go
Dockerfile
go.mod contractcourt: add HtlcBlobs to taprootBriefcase 2024-11-14 16:09:58 -08:00
go.sum contractcourt: add HtlcBlobs to taprootBriefcase 2024-11-14 16:09:58 -08:00
intercepted_forward.go
LICENSE
lnd.go build: separate sublogger and rotator pipe management 2024-10-22 15:19:58 +02:00
log.go go.mod: update LND sub-module deps 2024-10-29 15:01:00 +02:00
logo.png
Makefile makefile+scripts: add Go version check to release command 2024-10-23 13:34:35 +02:00
pilot.go
README.md
rpcserver_test.go
rpcserver.go rpcserver: add robustness check 2024-11-20 09:18:25 +01:00
sample-lnd.conf multi: deprecate dust-treshold config value 2024-11-06 18:16:06 +01:00
SECURITY.md
server_test.go
server.go peer+lnd: fix peer blocking on node shutdown 2024-11-18 18:49:34 +08:00
sqlc.yaml
subrpcserver_config.go multi: update more loggers to the v2 type 2024-10-22 17:03:56 +02:00
sweeper_wallet.go
tls_manager_test.go
tls_manager.go
witness_beacon_test.go
witness_beacon.go

Lightning Network Daemon

Release build MIT licensed Irc Godoc Go Report Card

The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node. 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

lnd fully 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:

  • BOLT 1: Base Protocol
  • BOLT 2: Peer Protocol for Channel Management
  • BOLT 3: Bitcoin Transaction and Script Formats
  • BOLT 4: Onion Routing Protocol
  • BOLT 5: Recommendations for On-chain Transaction Handling
  • BOLT 7: P2P Node and Channel Discovery
  • BOLT 8: Encrypted and Authenticated Transport
  • BOLT 9: Assigned Feature Flags
  • BOLT 10: DNS Bootstrap and Assisted Node Location
  • BOLT 11: Invoice Protocol for Lightning Payments

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 APIs 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 guides, articles, example applications and community resources can be found at: docs.lightning.engineering.

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.libera.chat
  • channel #lnd
  • webchat

Safety

When operating a mainnet lnd node, please refer to our operational safety guidelines. It is important to note that lnd is still beta software and that ignoring these operational guidelines can lead to loss of funds.

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.

Further reading