Difference between revisions of "Orphan Block"
| Line 3: | Line 3: | ||
An orphan block often originates when two [[Mining|miners]] produce a block around the same point in time. The time delay in propagating and accepting a block leads to Bitcoin SV nodes encountering scenarios where they need to select which of multiple blocks to accept as the most legitimate to include next in the chain. After a block is selected by the network, then the other block is considered an orphaned block. Transactions in the orphaned block that were not included in the successful block are re-included into the mempool as membership candidates for future blocks. In most cases the vast majority of transactions will be included in both as propagation of transactions across the network is very efficient and both miners are likely to have seen the same set. | An orphan block often originates when two [[Mining|miners]] produce a block around the same point in time. The time delay in propagating and accepting a block leads to Bitcoin SV nodes encountering scenarios where they need to select which of multiple blocks to accept as the most legitimate to include next in the chain. After a block is selected by the network, then the other block is considered an orphaned block. Transactions in the orphaned block that were not included in the successful block are re-included into the mempool as membership candidates for future blocks. In most cases the vast majority of transactions will be included in both as propagation of transactions across the network is very efficient and both miners are likely to have seen the same set. | ||
| − | In other instances, orphan blocks may be generated when malicious nodes seek to reverse transactions by generating alternative desired blocks. This they hope to accomplish through the utilization of large amounts of hash power (see [[Attacks on Bitcoin| 51% attack]]). However, attacks intended to cause the deliberate orphaning of blocks are extremely resource-intensive and are largely infeasible. The blocks they generate generally end up being orphaned. | + | In other instances, orphan blocks may be generated when malicious nodes seek to reverse transactions by generating alternative desired blocks. This they hope to accomplish through the utilization of large amounts of hash power (see [[Attacks on Bitcoin| 51% attack]]). However, attacks intended to cause the deliberate orphaning of blocks are extremely resource-intensive and are largely infeasible. The blocks they generate generally end up being orphaned themselves. |
==See Also== | ==See Also== | ||
* [[Miner subsidy]] | * [[Miner subsidy]] | ||
Revision as of 12:00, 18 February 2020
An "orphan block" is a well-formed block with valid proof of work which has been rejected by miners and does not form part of the longest Block chain. As the block in question has not been accepted, the block reward and the transaction fees are no longer spendable on the difficulty wise-longest and well-formed blockchain. This phenomenon must be taken into account by mining pools that use any payout strategy other than "proportional".
An orphan block often originates when two miners produce a block around the same point in time. The time delay in propagating and accepting a block leads to Bitcoin SV nodes encountering scenarios where they need to select which of multiple blocks to accept as the most legitimate to include next in the chain. After a block is selected by the network, then the other block is considered an orphaned block. Transactions in the orphaned block that were not included in the successful block are re-included into the mempool as membership candidates for future blocks. In most cases the vast majority of transactions will be included in both as propagation of transactions across the network is very efficient and both miners are likely to have seen the same set.
In other instances, orphan blocks may be generated when malicious nodes seek to reverse transactions by generating alternative desired blocks. This they hope to accomplish through the utilization of large amounts of hash power (see 51% attack). However, attacks intended to cause the deliberate orphaning of blocks are extremely resource-intensive and are largely infeasible. The blocks they generate generally end up being orphaned themselves.