From 92c1766f49871b2433d8ce93e18cfe86f722fd8a Mon Sep 17 00:00:00 2001 From: JoelKatz Date: Fri, 1 Mar 2013 13:20:08 -0800 Subject: [PATCH] Ack! A delayed consensus causes the close time threshold to ratchet the wrong way. --- src/cpp/ripple/LedgerConsensus.cpp | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/cpp/ripple/LedgerConsensus.cpp b/src/cpp/ripple/LedgerConsensus.cpp index fb4345f390..53c6148150 100644 --- a/src/cpp/ripple/LedgerConsensus.cpp +++ b/src/cpp/ripple/LedgerConsensus.cpp @@ -766,10 +766,8 @@ void LedgerConsensus::updateOurPositions() neededWeight = AV_INIT_CONSENSUS_PCT; else if (mClosePercent < AV_LATE_CONSENSUS_TIME) neededWeight = AV_MID_CONSENSUS_PCT; - else if (mClosePercent < AV_STUCK_CONSENSUS_TIME) - neededWeight = AV_LATE_CONSENSUS_PCT; else - neededWeight = AV_STUCK_CONSENSUS_TIME; + neededWeight = AV_LATE_CONSENSUS_PCT; uint32 closeTime = 0; mHaveCloseTimeConsensus = false;