7917fd2ab0
In this commit, we re-work the existing invoiceRegistry struct to support delivering backlog notifications to subscription clients if needed. Rather than using 1 goroutine per-client per-event, each client now gains a concurrent notification queue. This queue will then be used to ensure in-order delivery of all notifications from the invoiceEventNotifier. The SubscribeNotifications method now takes two params: addIndex, and settleIndex. These should be the values of the last add index and settle index the caller knows of. If specified (not zero), then we'll look up all the notifications that the caller has missed, and then deliver those before sending out any new notifications. In order to do this without losing ordering of events, we've added a new central goroutine which will ensure that all events are properly serialized. |
||
---|---|---|
.github | ||
aezeed | ||
autopilot | ||
brontide | ||
chainntnfs | ||
channeldb | ||
cmd/lncli | ||
contractcourt | ||
contrib | ||
discovery | ||
docker | ||
docs | ||
htlcswitch | ||
keychain | ||
lncfg | ||
lnpeer | ||
lnrpc | ||
lntest | ||
lnwallet | ||
lnwire | ||
macaroons | ||
make | ||
multimutex | ||
nat | ||
routing | ||
shachain | ||
signal | ||
tor | ||
walletunlocker | ||
zpay32 | ||
.gitignore | ||
.travis.yml | ||
breacharbiter_test.go | ||
breacharbiter.go | ||
chainparams.go | ||
chainregistry.go | ||
chan_series.go | ||
chancloser.go | ||
config.go | ||
doc.go | ||
Dockerfile | ||
fundingmanager_test.go | ||
fundingmanager.go | ||
Gopkg.lock | ||
Gopkg.toml | ||
invoiceregistry.go | ||
LICENSE | ||
lnd_test.go | ||
lnd.go | ||
log.go | ||
logo.png | ||
Makefile | ||
mock.go | ||
nodesigner.go | ||
nursery_store_test.go | ||
nursery_store.go | ||
peer_test.go | ||
peer.go | ||
pilot.go | ||
README.md | ||
release.sh | ||
rpcserver.go | ||
sample-lnd.conf | ||
server_test.go | ||
server.go | ||
test_utils.go | ||
utxonursery_test.go | ||
utxonursery.go | ||
version.go | ||
witness_beacon.go |
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
lnd
fully conforms to the Lightning Network specification
(BOLTs). BOLT stands for:
Basic of Lightning Technologies. 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 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