Don't be too harsh for invalid CLSIGs (#2742)

The local node might be the bad one actually as it might not have catched
up with the chain. In that case, LLMQs might be different for the sending
and receiving node.
This commit is contained in:
Alexander Block 2019-03-06 08:00:21 +01:00 committed by GitHub
parent a34fb6d6f7
commit 8dd9349224
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -104,7 +104,7 @@ void CChainLocksHandler::ProcessNewChainLock(NodeId from, const llmq::CChainLock
LogPrintf("CChainLocksHandler::%s -- invalid CLSIG (%s), peer=%d\n", __func__, clsig.ToString(), from); LogPrintf("CChainLocksHandler::%s -- invalid CLSIG (%s), peer=%d\n", __func__, clsig.ToString(), from);
if (from != -1) { if (from != -1) {
LOCK(cs_main); LOCK(cs_main);
Misbehaving(from, 100); Misbehaving(from, 10);
} }
return; return;
} }