cryptogera/beachcoin
cryptogera/beachcoin
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 1 Wiki Activity

Stop always storing blocks from whitelisted peers

Browse Source 
There is no reason to wish to store blocks on disk always just
because a peer is whitelisted. This appears to be a historical
quirk to avoid breaking things when the accept limits were added.

Github-Pull: #11531
Rebased-From: 3d9c70ca0fd5d42f31114b689714af1825f0ed30
This commit is contained in:
Matt Corallo 2017-10-11 16:01:51 -04:00 committed by MarcoFalke
parent e976c36ddf
commit c6e4d0ce82
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/net_processing.cpp
View File

@ -2509,11 +2509,7 @@ bool static ProcessMessage(CNode* pfrom, const std::string& strCommand, CDataStr
LogPrint(BCLog::NET, "received block %s peer=%d\n", pblock->GetHash().ToString(), pfrom->GetId());
// Process all blocks from whitelisted peers, even if not requested,
// unless we're still syncing with the network.
// Such an unrequested block may still be processed, subject to the
// conditions in AcceptBlock().
bool forceProcessing = pfrom->fWhitelisted && !IsInitialBlockDownload();
bool forceProcessing = false;
const uint256 hash(pblock->GetHash());
{
LOCK(cs_main);