lnd/channeldb
Andras Banki-Horvath b3dc3ed5c8 channeldb: filter AMP state to relevant set IDs
When fetching an AMP invoice we sometimes filter HTLCs to selected set
IDs, however we always kept the full AMP state which is irrelevant as it
contains state for all AMP payments. This was a side effect of
UpdateInvoice needing to serialize the whole invoice when storing after
an update but it is an unwanted "feature" as users will need to filter
to relevant set when listing an AMP payment or subsribing to an update.
2024-09-06 12:59:32 -07:00
..
2024-04-25 11:21:18 +02:00
2024-04-11 15:04:03 +02:00
2024-04-11 15:04:03 +02:00
2024-04-11 15:04:03 +02:00
2024-04-11 15:04:03 +02:00
2022-01-24 12:19:02 +02:00
2023-08-15 10:00:30 +02:00
2022-08-23 22:10:24 +08:00
2022-02-10 11:02:01 +01:00
2022-08-23 22:10:24 +08:00

channeldb

Build Status MIT licensed GoDoc

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