mirror of
https://github.com/FlipsideCrypto/dcrd.git
synced 2026-02-06 10:56:47 +00:00
This commit is the first stage of several that are planned to convert
the blockchain package into a concurrent safe package that will
ultimately allow support for multi-peer download and concurrent chain
processing. The goal is to update btcd proper after each step so it can
take advantage of the enhancements as they are developed.
In addition to the aforementioned benefit, this staged approach has been
chosen since it is absolutely critical to maintain consensus.
Separating the changes into several stages makes it easier for reviewers
to logically follow what is happening and therefore helps prevent
consensus bugs. Naturally there are significant automated tests to help
prevent consensus issues as well.
The main focus of this stage is to convert the blockchain package to use
the new database interface and implement the chain-related functionality
which it no longer handles. It also aims to improve efficiency in
various areas by making use of the new database and chain capabilities.
The following is an overview of the chain changes:
- Update to use the new database interface
- Add chain-related functionality that the old database used to handle
- Main chain structure and state
- Transaction spend tracking
- Implement a new pruned unspent transaction output (utxo) set
- Provides efficient direct access to the unspent transaction outputs
- Uses a domain specific compression algorithm that understands the
standard transaction scripts in order to significantly compress them
- Removes reliance on the transaction index and paves the way toward
eventually enabling block pruning
- Modify the New function to accept a Config struct instead of
inidividual parameters
- Replace the old TxStore type with a new UtxoViewpoint type that makes
use of the new pruned utxo set
- Convert code to treat the new UtxoViewpoint as a rolling view that is
used between connects and disconnects to improve efficiency
- Make best chain state always set when the chain instance is created
- Remove now unnecessary logic for dealing with unset best state
- Make all exported functions concurrent safe
- Currently using a single chain state lock as it provides a straight
forward and easy to review path forward however this can be improved
with more fine grained locking
- Optimize various cases where full blocks were being loaded when only
the header is needed to help reduce the I/O load
- Add the ability for callers to get a snapshot of the current best
chain stats in a concurrent safe fashion
- Does not block callers while new blocks are being processed
- Make error messages that reference transaction outputs consistently
use <transaction hash>:<output index>
- Introduce a new AssertError type an convert internal consistency
checks to use it
- Update tests and examples to reflect the changes
- Add a full suite of tests to ensure correct functionality of the new
code
The following is an overview of the btcd changes:
- Update to use the new database and chain interfaces
- Temporarily remove all code related to the transaction index
- Temporarily remove all code related to the address index
- Convert all code that uses transaction stores to use the new utxo
view
- Rework several calls that required the block manager for safe
concurrency to use the chain package directly now that it is
concurrent safe
- Change all calls to obtain the best hash to use the new best state
snapshot capability from the chain package
- Remove workaround for limits on fetching height ranges since the new
database interface no longer imposes them
- Correct the gettxout RPC handler to return the best chain hash as
opposed the hash the txout was found in
- Optimize various RPC handlers:
- Change several of the RPC handlers to use the new chain snapshot
capability to avoid needlessly loading data
- Update several handlers to use new functionality to avoid accessing
the block manager so they are able to return the data without
blocking when the server is busy processing blocks
- Update non-verbose getblock to avoid deserialization and
serialization overhead
- Update getblockheader to request the block height directly from
chain and only load the header
- Update getdifficulty to use the new cached data from chain
- Update getmininginfo to use the new cached data from chain
- Update non-verbose getrawtransaction to avoid deserialization and
serialization overhead
- Update gettxout to use the new utxo store versus loading
full transactions using the transaction index
The following is an overview of the utility changes:
- Update addblock to use the new database and chain interfaces
- Update findcheckpoint to use the new database and chain interfaces
- Remove the dropafter utility which is no longer supported
NOTE: The transaction index and address index will be reimplemented in
another commit.
177 lines
3.9 KiB
Go
177 lines
3.9 KiB
Go
// Copyright (c) 2013-2014 Conformal Systems LLC.
|
|
// Copyright (c) 2015-2016 The Decred developers
|
|
// Use of this source code is governed by an ISC
|
|
// license that can be found in the LICENSE file.
|
|
|
|
package dcrjson
|
|
|
|
// Standard JSON-RPC 2.0 errors
|
|
var (
|
|
ErrInvalidRequest = Error{
|
|
Code: -32600,
|
|
Message: "Invalid request",
|
|
}
|
|
ErrMethodNotFound = Error{
|
|
Code: -32601,
|
|
Message: "Method not found",
|
|
}
|
|
ErrInvalidParams = Error{
|
|
Code: -32602,
|
|
Message: "Invalid paramaters",
|
|
}
|
|
ErrInternal = Error{
|
|
Code: -32603,
|
|
Message: "Internal error",
|
|
}
|
|
ErrParse = Error{
|
|
Code: -32700,
|
|
Message: "Parse error",
|
|
}
|
|
)
|
|
|
|
// General application defined JSON errors
|
|
var (
|
|
ErrMisc = Error{
|
|
Code: -1,
|
|
Message: "Miscellaneous error",
|
|
}
|
|
ErrForbiddenBySafeMode = Error{
|
|
Code: -2,
|
|
Message: "Server is in safe mode, and command is not allowed in safe mode",
|
|
}
|
|
ErrType = Error{
|
|
Code: -3,
|
|
Message: "Unexpected type was passed as parameter",
|
|
}
|
|
ErrInvalidAddressOrKey = Error{
|
|
Code: -5,
|
|
Message: "Invalid address or key",
|
|
}
|
|
ErrOutOfMemory = Error{
|
|
Code: -7,
|
|
Message: "Ran out of memory during operation",
|
|
}
|
|
ErrInvalidParameter = Error{
|
|
Code: -8,
|
|
Message: "Invalid, missing or duplicate parameter",
|
|
}
|
|
ErrDatabase = Error{
|
|
Code: -20,
|
|
Message: "Database error",
|
|
}
|
|
ErrDeserialization = Error{
|
|
Code: -22,
|
|
Message: "Error parsing or validating structure in raw format",
|
|
}
|
|
)
|
|
|
|
// Peer-to-peer client errors
|
|
var (
|
|
ErrClientNotConnected = Error{
|
|
Code: -9,
|
|
Message: "dcrd is not connected",
|
|
}
|
|
ErrClientInInitialDownload = Error{
|
|
Code: -10,
|
|
Message: "dcrd is downloading blocks...",
|
|
}
|
|
)
|
|
|
|
// Wallet JSON errors
|
|
var (
|
|
ErrWallet = Error{
|
|
Code: -4,
|
|
Message: "Unspecified problem with wallet",
|
|
}
|
|
ErrWalletInsufficientFunds = Error{
|
|
Code: -6,
|
|
Message: "Not enough funds in wallet or account",
|
|
}
|
|
ErrWalletInvalidAccountName = Error{
|
|
Code: -11,
|
|
Message: "Invalid account name",
|
|
}
|
|
ErrWalletKeypoolRanOut = Error{
|
|
Code: -12,
|
|
Message: "Keypool ran out, call keypoolrefill first",
|
|
}
|
|
ErrWalletUnlockNeeded = Error{
|
|
Code: -13,
|
|
Message: "Enter the wallet passphrase with walletpassphrase first",
|
|
}
|
|
ErrWalletPassphraseIncorrect = Error{
|
|
Code: -14,
|
|
Message: "The wallet passphrase entered was incorrect",
|
|
}
|
|
ErrWalletWrongEncState = Error{
|
|
Code: -15,
|
|
Message: "Command given in wrong wallet encryption state",
|
|
}
|
|
ErrWalletEncryptionFailed = Error{
|
|
Code: -16,
|
|
Message: "Failed to encrypt the wallet",
|
|
}
|
|
ErrWalletAlreadyUnlocked = Error{
|
|
Code: -17,
|
|
Message: "Wallet is already unlocked",
|
|
}
|
|
)
|
|
|
|
// Specific Errors related to commands. These are the ones a user of the rpc
|
|
// server are most likely to see. Generally, the codes should match one of the
|
|
// more general errors above.
|
|
var (
|
|
ErrBlockNotFound = Error{
|
|
Code: -5,
|
|
Message: "Block not found",
|
|
}
|
|
ErrBlockCount = Error{
|
|
Code: -5,
|
|
Message: "Error getting block count",
|
|
}
|
|
ErrBestBlockHash = Error{
|
|
Code: -5,
|
|
Message: "Error getting best block hash",
|
|
}
|
|
ErrDifficulty = Error{
|
|
Code: -5,
|
|
Message: "Error getting difficulty",
|
|
}
|
|
ErrOutOfRange = Error{
|
|
Code: -1,
|
|
Message: "Block number out of range",
|
|
}
|
|
ErrNoTxInfo = Error{
|
|
Code: -5,
|
|
Message: "No information available about transaction",
|
|
}
|
|
ErrNoNewestBlockInfo = Error{
|
|
Code: -5,
|
|
Message: "No information about newest block",
|
|
}
|
|
ErrInvalidTxVout = Error{
|
|
Code: -5,
|
|
Message: "Ouput index number (vout) does not exist for transaction.",
|
|
}
|
|
ErrRawTxString = Error{
|
|
Code: -32602,
|
|
Message: "Raw tx is not a string",
|
|
}
|
|
ErrDecodeHexString = Error{
|
|
Code: -22,
|
|
Message: "Unable to decode hex string",
|
|
}
|
|
)
|
|
|
|
// Errors that are specific to dcrd.
|
|
var (
|
|
ErrNoWallet = Error{
|
|
Code: -1,
|
|
Message: "This implementation does not implement wallet commands",
|
|
}
|
|
ErrUnimplemented = Error{
|
|
Code: -1,
|
|
Message: "Command unimplemented",
|
|
}
|
|
)
|