lbcd/blockchain
2021-09-13 16:57:14 -07:00
..
fullblocktests use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
indexers use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
testdata multi: Rework utxoset/view to use outpoints. 2018-05-27 03:07:41 -05:00
accept.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
blockindex.go step 1 of updating module paths to not use replace 2021-09-10 16:23:04 -04:00
chain.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
chainio.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
chainio_test.go step 1 of updating module paths to not use replace 2021-09-10 16:23:04 -04:00
chainview.go blockchain: Refactor to use new chain view. 2017-08-23 23:43:37 -05:00
chainview_test.go step 1 of updating module paths to not use replace 2021-09-10 16:23:04 -04:00
checkpoints.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
claimtrie.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
common_test.go [lbry] ci: fix linting (nakedret) 2021-09-13 16:57:14 -07:00
compress.go step 1 of updating module paths to not use replace 2021-09-10 16:23:04 -04:00
compress_test.go multi: Rework utxoset/view to use outpoints. 2018-05-27 03:07:41 -05:00
difficulty.go fix regtest difficulty 2021-09-11 17:50:32 -04:00
difficulty_test.go build: clean linter warnings 2020-05-13 08:58:39 -04:00
doc.go Relicense to the btcsuite developers. 2015-05-01 12:00:56 -05:00
error.go [lbry] add ClaimTrie to Block Header 2021-08-19 14:19:20 -04:00
error_test.go blockchain: Track block validation status in block index. 2017-10-23 04:33:15 -05:00
log.go all: Remove seelog logger. 2017-06-19 16:46:50 -04:00
mediantime.go [lbry] misc: rename btcd to lbcd 2021-08-19 14:17:22 -04:00
mediantime_test.go btcd/multi: fix a number of typos in comments. 2018-01-25 23:23:59 -06:00
merkle.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
notifications.go blockchain: Consistency pass on subscribe code. 2017-08-15 11:12:56 -05:00
process.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
README.md sanitizing readmes for lbcd 2021-08-31 15:53:55 -04:00
scriptval.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
thresholdstate.go step 1 of updating module paths to not use replace 2021-09-10 16:23:04 -04:00
thresholdstate_test.go step 1 of updating module paths to not use replace 2021-09-10 16:23:04 -04:00
timesorter.go blockchain: Use int64 timestamps in block nodes. 2017-01-31 17:51:29 -06:00
timesorter_test.go blockchain: Consolidate tests into package. 2017-08-19 23:05:17 -05:00
upgrade.go step 1 of updating module paths to not use replace 2021-09-10 16:23:04 -04:00
upgrade_test.go multi: Rework utxoset/view to use outpoints. 2018-05-27 03:07:41 -05:00
utxoviewpoint.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
validate.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00
versionbits.go step 1 of updating module paths to not use replace 2021-09-10 16:23:04 -04:00
weight.go use newer lbcutil, rename refs for it 2021-09-10 16:51:53 -04:00

blockchain

ISC License

Bitcoin Chain Processing Overview

Before a block is allowed into the block chain, it must go through an intensive series of validation rules. The following list serves as a general outline of those rules to provide some intuition into what is going on under the hood, but is by no means exhaustive:

  • Reject duplicate blocks
  • Perform a series of sanity checks on the block and its transactions such as verifying proof of work, timestamps, number and character of transactions, transaction amounts, script complexity, and merkle root calculations
  • Compare the block against predetermined checkpoints for expected timestamps and difficulty based on elapsed time since the checkpoint
  • Save the most recent orphan blocks for a limited time in case their parent blocks become available
  • Stop processing if the block is an orphan as the rest of the processing depends on the block's position within the block chain
  • Perform a series of more thorough checks that depend on the block's position within the block chain such as verifying block difficulties adhere to difficulty retarget rules, timestamps are after the median of the last several blocks, all transactions are finalized, checkpoint blocks match, and block versions are in line with the previous blocks
  • Determine how the block fits into the chain and perform different actions accordingly in order to ensure any side chains which have higher difficulty than the main chain become the new main chain
  • When a block is being connected to the main chain (either through reorganization of a side chain to the main chain or just extending the main chain), perform further checks on the block's transactions such as verifying transaction duplicates, script complexity for the combination of connected scripts, coinbase maturity, double spends, and connected transaction values
  • Run the transaction scripts to verify the spender is allowed to spend the coins
  • Insert the block into the block database