c986e52da7
In this commit, we fix an existing issue that could at times cause an inconsistent view between the set of total coins, and the set of segwit coins in the wallet of the node. This could be caused by initiating a funding flow, but then the funding negotiation breaking down somewhere along the lines. In this case, us or the other peer will disconnect. When we initiate funding flows, we lock coins exclusively, to ensure that concurrent funding flows don’t end up double spending the same coin. Before this commit, we wouldn’t ever unlock those coins. As a result, our view of available coins would be skewed. The walletbalance call would show all the coins, but when adding the —witness_only flag, some coins would be missing, or gone all together. This is because the former call actually scans the txstore and manually tallies the amount of available coins, while the latter looks at the sent of available outputs, which is filtered based on which coins are locked. To remedy this, we now ensure that when a peer disconnects, we wipe all existing reservations which will return any locked outputs to the set of available outputs for funding flows. |
||
|---|---|---|
| autopilot | ||
| brontide | ||
| chainntnfs | ||
| channeldb | ||
| cmd/lncli | ||
| contrib | ||
| discovery | ||
| docker | ||
| docs | ||
| htlcswitch | ||
| lnrpc | ||
| lnwallet | ||
| lnwire | ||
| macaroons | ||
| routing | ||
| shachain | ||
| walletunlocker | ||
| zpay32 | ||
| .gitignore | ||
| .travis.yml | ||
| breacharbiter_test.go | ||
| breacharbiter.go | ||
| chainparams.go | ||
| chainregistry.go | ||
| chancloser.go | ||
| config.go | ||
| doc.go | ||
| fundingmanager_test.go | ||
| fundingmanager.go | ||
| glide.lock | ||
| glide.yaml | ||
| gotest.sh | ||
| invoiceregistry.go | ||
| LICENSE | ||
| lnd_test.go | ||
| lnd.go | ||
| log.go | ||
| logo.png | ||
| mock.go | ||
| networktest_test.go | ||
| networktest.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.go | ||
| signal.go | ||
| test_utils.go | ||
| utxonursery_test.go | ||
| utxonursery.go | ||
| version.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) 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 doesn't yet fully conform 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, lnd 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.
IRC
- irc.freenode.net
- channel #lnd
- webchat