Author

Topic: fork detection behavior (Read 857 times)

jr. member
Activity: 50
Merit: 54
January 03, 2015, 09:26:47 AM
#3
The quote is out of context, so it isn't clear that we're talking about a non-upgraded node after a hard fork.  In that case, the non-upgraded node does not think the stronger chain is valid (because it breaks some consensus rule), so it will not accept it as the local best block chain.  The error/alertnotify is to tell you something is wrong.  For reference, that section of the docs was written based on the code is this function.

I'll push a minor revision to the quoted sentence so it's more clear and harder to take out of context.  Thanks!
staff
Activity: 4284
Merit: 8808
January 01, 2015, 01:55:50 AM
#2
Of course, otherwise it would risk triggerable (or even spontaneous) convergence failures which could be exploited to cause loss of funds.
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
January 01, 2015, 01:50:37 AM
#1
regarding this:

Quote
Bitcoin Core includes code that detects a hard fork by looking at block chain proof of work. If a node receives block chain headers demonstrating six blocks more proof of work than the best chain this node considers valid, the node reports an error in the getinfo RPC results and runs the -alertnotify command if set.

even though the node reports an error, will it still accept the longer chain as the new best chain?
Jump to: