48c0e42c26
This commit converts the database structure of a payment so that it can not just store the last htlc attempt, but all attempts that have been made. This is a preparation for mpp sending. In addition to that, we now also persist the fail time of an htlc. In a later commit, the full failure reason will be added as well. A key change is made to the control tower interface. Previously the control tower wasn't aware of individual htlc outcomes. The payment remained in-flight with the latest attempt recorded, but an outcome was only set when the payment finished. With this commit, the outcome of every htlc is expected by the control tower and recorded in the database. Co-authored-by: Johan T. Halseth <johanth@gmail.com> |
||
|---|---|---|
| .. | ||
| migration_01_to_11 | ||
| migration12 | ||
| migtest | ||
| addr_test.go | ||
| addr.go | ||
| channel_cache_test.go | ||
| channel_cache.go | ||
| channel_test.go | ||
| channel.go | ||
| codec.go | ||
| db_test.go | ||
| db.go | ||
| doc.go | ||
| duplicate_payments.go | ||
| error.go | ||
| fees.go | ||
| forwarding_log_test.go | ||
| forwarding_log.go | ||
| forwarding_package_test.go | ||
| forwarding_package.go | ||
| graph_test.go | ||
| graph.go | ||
| invoice_test.go | ||
| invoices.go | ||
| legacy_serialization.go | ||
| log.go | ||
| meta_test.go | ||
| meta.go | ||
| mp_payment.go | ||
| nodes_test.go | ||
| nodes.go | ||
| options.go | ||
| payment_control_test.go | ||
| payment_control.go | ||
| payments_test.go | ||
| payments.go | ||
| README.md | ||
| reject_cache_test.go | ||
| reject_cache.go | ||
| waitingproof_test.go | ||
| waitingproof.go | ||
| witness_cache_test.go | ||
| witness_cache.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