29f2f88abc
In this commit we’ve extended the TestChannelStateTransition method to exercise the new state transition related messages. This includes ensuring that when we add a new dangling commitment, and then the remote party revokes it, then the on-disk state is update accordingly. |
||
|---|---|---|
| .. | ||
| channel_test.go | ||
| channel.go | ||
| codec.go | ||
| db_test.go | ||
| db.go | ||
| doc.go | ||
| error.go | ||
| fees.go | ||
| graph_test.go | ||
| graph.go | ||
| invoice_test.go | ||
| invoices.go | ||
| log.go | ||
| meta_test.go | ||
| meta.go | ||
| migrations.go | ||
| nodes_test.go | ||
| nodes.go | ||
| payments_test.go | ||
| payments.go | ||
| README.md | ||
| waitingproof_test.go | ||
| waitingproof.go | ||
channeldb
The channeldb implements the persistent storage engine for lnd and
generically a data storage layer for the required state within the Lightning
Network. The backing storage engine is
boltdb, an embedded pure-go key-value store
based off of LMDB.
The package implements an object-oriented storage model with queries and mutations flowing through a particular object instance rather than the database itself. The storage implemented by the objects includes: open channels, past commitment revocation states, the channel graph which includes authenticated node and channel announcements, outgoing payments, and invoices
Installation and Updating
$ go get -u github.com/lightningnetwork/lnd/channeldb