0e0e207802
This commit updates the internal channel state machine to the one as
described within the spec and currently implemented within the rest of
the other Lightning implementations.
At a high level the following modifications have been made:
* When signing we no loner include the index of the remote party’s
log
that our signature covers. Instead we include ALL of our current
updates, but only the updates of the remote party that we’ve
ACK’d.
* A pending change is considered ACK’d once a revocation message
has been received, locking in the changes in the remote party’s
commitment transaction.
* When sending a new commitment, we remember the index of our
log at that point so we can mark that portion of the log as ACK’d
once we receive a revocation message from the remote party.
* When receiving a new commitment signature, we include ALL of
the remote party’s changes that we’ve received but only our set
of changes that’ve been ACK’d by the remote party.
* Implicitly a revocation message now also implicitly serves to ACK
all the changes that were included in the CommitSig message
received before it.
The resulting change is a rather minor diff. However, with this state
machine it’s important to note that the order to sig/revoke messages
has been swapped. A proper exchange now looks like the following:
* Alice -> Add, Add, Add
* Alice -> Sig
* Revoke <- Bob
* Sig <- Bob
* Alice -> Revoke
One other thing that’s worth noting is that with this state machine,
since what’s included in an update is implicit, both side may need to
at times send a new commitment update in the case of a concurrent state
transition initiated by both sides.
Finally, all counters/indexes have been made 64-bit integers in order
to properly match the spec.
|
||
|---|---|---|
| brontide | ||
| chainntnfs | ||
| channeldb | ||
| cmd/lncli | ||
| contrib | ||
| docker | ||
| docs | ||
| elkrem | ||
| lnrpc | ||
| lnwallet | ||
| lnwire | ||
| routing | ||
| shachain | ||
| zpay32 | ||
| .gitignore | ||
| .travis.yml | ||
| breacharbiter.go | ||
| config.go | ||
| doc.go | ||
| features.go | ||
| fundingmanager.go | ||
| glide.lock | ||
| glide.yaml | ||
| htlcswitch.go | ||
| invoiceregistry.go | ||
| LICENSE | ||
| lnd_test.go | ||
| lnd.go | ||
| log.go | ||
| networktest_test.go | ||
| networktest.go | ||
| params.go | ||
| peer_test.go | ||
| peer.go | ||
| README.md | ||
| release.sh | ||
| rpcserver.go | ||
| server.go | ||
| signal.go | ||
| utxonursery_test.go | ||
| utxonursery.go | ||
| version.go | ||
Lightning Network Daemon
[
]
(https://travis-ci.org/lightningnetwork/lnd)
[
]
(https://github.com/lightningnetwork/lnd/blob/master/LICENSE)
[
]
(https://webchat.freenode.net/?channels=lnd)
[
]
(https://godoc.org/github.com/lightningnetwork/lnd)
The Lightning Network Daemon (lnd) - is a complete implementation of a
Lightning Network node and currently
deployed on testnet4 - the Bitcoin Test Network. It utilizes an
upcoming upgrade to Bitcoin: Segregated Witness (segwit). The
project's codebase uses the btcsuite set
of Bitcoin libraries, and is currently dependant on btcd.
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
Lightning Network Specification Compliance
lnd doesn't yet fully conform to the Lightning Network specification
(BOLT's). 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
lndcurrently utilizes a distinct wire format which was created before the emgergence of the current draft of BOLT specifications. We don't have aninitmessage, but we do have analogues to all the other defined message types.
- BOLT 2: Peer Protocol for Channel Management
lndimplements all the functionality defined within the document, however we currently use a different set of wire messages. Additionally,lnduses a distinct commitment update state-machine and doesn't yet support dynamically updating commitment fees.
- BOLT 3: Bitcoin Transaction and Script Formats
lndcurrently uses a commitment design from a prior iteration of the protocol. Revocation secret generation is handled byelkremand our scripts are slightly different.
- 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
Installation
In order to build from source, the following build dependencies are required:
-
Go: Installation instructions can be found here.
It is recommended to add
$GOPATH/binto yourPATHat this point. Note: If you are building withGo 1.5, then you'll need to enable the vendor experiment by setting theGO15VENDOREXPERIMENTenvironment variable to1. If you're usingGo 1.6or later, then it is safe to skip this step. -
Glide: This project uses
Glideto manage dependencies as well as to provide reproducible builds. To installGlide, execute the following command (assumes you already have Go properly installed):$ go get -u github.com/Masterminds/glide -
btcd: This project currently requires
btcdwith segwit support, which is not yet merged into the master branch. Instead, roasbeef maintains a fork with his segwit implementation applied. To install, please see the installation instructions.
With the preliminary steps completed, to install lnd, lncli, and all
related dependencies run the following commands:
$ git clone https://github.com/lightningnetwork/lnd $GOPATH/src/github.com/lightningnetwork/lnd
$ cd $GOPATH/src/github.com/lightningnetwork/lnd
$ glide install
$ go install . ./cmd/...
Updating
To update your version of lnd to the latest version run the following
commands:
$ cd $GOPATH/src/github.com/lightningnetwork/lnd
$ git pull && glide install
$ go install . ./cmd/...
Tests
To check that lnd was installed properly run the following command:
go install; go test -v -p 1 $(go list ./... | grep -v '/vendor/')
IRC
- irc.freenode.net
- channel #lnd
- webchat