bafea35a32
This commit expands the close summaries within the database to include additional information such as: how the channel was closed, if the channel if fully closed, and other balance information. This new information will be used in an upcoming expansion of the pendingChannels RPC to display more comprehensive data w.r.t where the node’s funds are and how soon they’ll be fully available. The data stored in the closeChannel bucket has been expanded to include the above. Additionally the CloseChannel method on the OpenChannel struct now takes in the additional information that details how and who it was closed by. This commit borrows heavily from the initial work in #179 by @halseth. |
||
---|---|---|
.. | ||
channel_test.go | ||
channel.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 |
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