lnd/channeldb/error.go

package channeldb

import "fmt"

var (
	ErrNoChanDBExists = fmt.Errorf("channel db has not yet been created")

	ErrNoActiveChannels = fmt.Errorf("no active channels exist")
	ErrChannelNoExist   = fmt.Errorf("this channel does not exist")
	ErrNoPastDeltas     = fmt.Errorf("channel has no recorded deltas")

	ErrInvoiceNotFound   = fmt.Errorf("unable to locate invoice")
	ErrNoInvoicesCreated = fmt.Errorf("there are no existing invoices")
	ErrDuplicateInvoice  = fmt.Errorf("invoice with payment hash already exists")
)
channeldb: create new channeldb package, update lnwallet to use new API * Initial draft of brain dump of chandler. Nothing yet set in stone. * Will most likely move the storage of all structs to a more “column” oriented approach. Such that, small updates like incrementing the total satoshi sent don’t result in the entire struct being serialized and written. * Some skeleton structs for other possible data we might want to store are also included. * Seem valuable to record as much data as possible for record keeping, visualization, debugging, etc. Will need to set up a time+space+dirty cache to ensure performance isn’t impacted too much. 2015-12-26 12:35:15 -06:00			`package channeldb`
channeldb: switch to Open/Create methods rather than New Commit includes basic tests for Open/Create. Additionally, rather than relying on btcwallet’s addmgr for encryption/decryption, this package now exposes a simple crypto system interface. 2016-03-23 22:11:57 -07:00
			`import "fmt"`

			`var (`
channeldb: add doc strings to finalize funcs/structs 2016-06-22 16:17:19 -07:00			`ErrNoChanDBExists = fmt.Errorf("channel db has not yet been created")`

channeldb: modify schema to multiple-channels-per-peer This commit overhauls the current schema for storing active channels in order to support tracking+updating multiple open channels for a particular peer. Channels are now uniquely identified by an output (txid:index) rather than an arbitrary hash value. As a result, the funding transaction is no longer stored, as only the txin is required to lookup the original transaction, and to sign for new commitment states. A new bucket, nested within the bucket for a node’s Lightning ID has been created. This new bucket acts as an index to the active channels for a particular peer by storing all the active channel points as keys within the bucket. This bucket can then be scanned in a linear fashion, or queried randomly in order to retrieve channel information. The split between top-level, and channel-level keys remains the same. The primary modification comes in using the channel ID (the funding outpoint) as the key suffix for all top-level and channel-level keys. 2016-06-20 21:39:50 -07:00			`ErrNoActiveChannels = fmt.Errorf("no active channels exist")`
channeldb: add doc strings to finalize funcs/structs 2016-06-22 16:17:19 -07:00			`ErrChannelNoExist = fmt.Errorf("this channel does not exist")`
channeldb: implement commitment state update log This commit implements a state update log which is intended the record the relevant information for each state transition on disk. For each state transition a delta should be written recording the new state. A new method is also provided which is able to retrieve a previous channel state based on a state update #. At the moment no measures has been taken to optimize the space utilization of each update on disk. There are several low-hanging fruits which can be addressed at a later point. Ultimately the update log itself should be implemented with an append-only flat file at the storage level. In any case, the high level abstraction should be able to maintained independent of differences in the on-disk format itself. 2016-09-02 18:51:34 -07:00			`ErrNoPastDeltas = fmt.Errorf("channel has no recorded deltas")`
channeldb: add persistent invoice workflow This commit adds the necessary database functionality required for a high-level payment invoice workflow. Invoices can be added dealing the requirements for fulfillment, looked by payment hash, and the finally also settled by payment hash. For record keeping and the possibility of reconciling future disputes, invoices are currently never deleted from disk. Instead when an invoice is settled a bit is toggled indicating as much. The current invoiceManger within the daemon will be modified to use this persistent invoice store, only storing certain “debug” invoices in memory as dictated by a command line flag. 2016-09-16 17:23:37 -07:00
channeldb: store the invoice counter within the invoice index bucket This commit moves the location of the invoice counter key which is an auto-incrementing primary key for all invoices. Rather than storing the counter in the same top-level invoice bucket, the counter is now stored within the invoiceIndex bucket. With this change, the top-level bucket can now cleanly be scanned in a sequential manner to retrieve all invoices. 2016-09-19 11:46:48 -07:00			`ErrInvoiceNotFound = fmt.Errorf("unable to locate invoice")`
			`ErrNoInvoicesCreated = fmt.Errorf("there are no existing invoices")`
			`ErrDuplicateInvoice = fmt.Errorf("invoice with payment hash already exists")`
channeldb: switch to Open/Create methods rather than New Commit includes basic tests for Open/Create. Additionally, rather than relying on btcwallet’s addmgr for encryption/decryption, this package now exposes a simple crypto system interface. 2016-03-23 22:11:57 -07:00			`)`