|
|
| (5 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | The Bitcoin '''block chain''' is the transaction database that is built by nodes participating in the [[mining]] process on the Bitcoin network. The block chain contains every [[Bitcoin Transactions|transaction]] ever executed on the network. With this information, one can calculate and trace the ownership record of all Bitcoins managed on the ledger at any point in history.
| + | #REDIRECT [[Blockchain]] |
| − | | |
| − | Every [[Block|block]] contains a reference to the block it builds upon. This has the effect of creating a chain of blocks from the [[genesis block]] to the current block. Blocks become computationally impractical to modify they have been built upon for a period of time due to the amount of [[Proof of Work|work]] that would need to be regenerated.
| |
| − | | |
| − | Miners extend the blockchain by building on what they consider to be the most recent valid block in the longest chain of proof of work. Miners can dispute blocks by choosing ''not'' to build upon them. A block that is not built upon is called an [[Orphan Block]].
| |
| − | | |
| − | For any block on the chain, there is only one path to the genesis block. Coming from the genesis block, however, there can be forks. Forks can be created from time to time when two valid blocks are created just a few seconds apart. When this happens, nodes will attempt to build a new block whichever one of the blocks they received first. When a new block is found, the block it built upon becomes part of the longest chain, orphaning its competitor.
| |
| − | | |
| − | Forks can also occur when nodes disagree on network rules. Two notable forks have occurred on Bitcoin, the first in 2017 when Bitcoin was forked onto the BCH network when BTC nodes elected to adopt Segregated Witness into the BTC network rules, and again in November 2018 when BCH nodes elected to implement new opcodes and consensus rules that were unaligned with the original protocol.
| |
| − | | |
| − | Blocks in shorter chains (or invalid chains) are not used for anything. If a node detects the creation of a longer chain than the one it is working on, all valid transactions of the block template inside the shorter chain are re-added to the pool of queued transactions and will be included in another block. The reward for the blocks on the shorter chain will not be present in the longest chain, so they will be practically lost, which is why a network-enforced 100-block maturation time for generations exists.
| |
| − | | |
| − | Because a block can only reference one previous block, it is impossible for two forked chains to merge.
| |
| − | | |
| − | Blocks are broadcast to all nodes on the networking using the Bitcoin Network protocol.
| |
| − | | |
| − | ==Attribution==
| |
| − | This content is based on content sourced from https://en.bitcoin.it/wiki/Block_chain under [https://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution 3.0]. Although it may have been extensively revised and updated we acknowledge the original authors.
| |