Bitcoin Forum
November 25, 2020, 04:55:57 PM *
News: Bitcointalk Community Awards
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Propagating orphan block headers  (Read 1009 times)
TierNolan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1006


View Profile
May 29, 2013, 12:31:58 PM
 #1

According to the official protocol rules, when a node receives a block that extends an orphan branch (but doesn't make it the main chain), the client simply stores the block.  It doesn't relay it.

This makes it impossible for nodes on the network to know if there is an orphan chain receiving significant hashing power.

If the rule was changed so that the block headers are forwarded, then the network would be informed about alt chains that are being hashed against.  

This would allow a warning to be given that a potential network split is occurring.  The client could then mark a transaction as unconfirmed if it occurs after the split.

The change would be to amend rule 17 from

Code:
For case 2, adding to a side branch, we don't do anything.

to

Code:
For case 2, adding to a side branch, if the fork point is within <some number of> blocks of the end of the main chain, relay the block header of the block to our peers.

Transmitting a block header shouldn't be taken to mean that the block has been verified.  It only means that block header forms part of the PoW tree.

This could cause problems with SPV clients, but they already assume that PoW alone is secure.

There would also need to be rules added for receiving a header.  It should be forwarded if it extends any branch in the tree (near the end of the main chain)

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!