Repository navigation
Kerrigan Core v1.3.2
This release stabilises masternode quorum formation and hardens per-algorithm
difficulty behaviour. It contains a consensus hard fork at block 148000.
Why upgrade
Since InstantSend and ChainLocks came online, some masternodes have been
receiving PoSe penalties and bans through no fault of their own. The cause is on
our side: irregular block timing (a long gap followed by a burst of blocks) could
drop healthy members from a quorum-formation round, and the inherited penalty was
too aggressive for a network of our size. This release fixes both, and the
scheduling fix takes effect the moment you install, before the activation height.
Highlights
-
Quorum-formation stability. A block burst no longer drops honest members
from a DKG round, and the failed-round penalty is recalibrated. Fewer, and
eventually no, unwarranted PoSe bans. The scheduling portion is node-local and
active on install. -
Per-algorithm difficulty recovery. When one algorithm is abandoned at high
difficulty, it now recovers quickly instead of stranding the chain. Pairs with
the per-algorithm retarget already scheduled for block 151000. -
Hivemind Protocol re-arm. The seal-weight fork-choice layer is re-armed
with corrected economics and on-chain verifiable committee proofs, restoring
the chain's finality weighting against reorganisation. -
Startup robustness. A node that was stopped uncleanly no longer refuses to
start in a benign state; it reconciles automatically.
Upgrade: required before block 148000
This release contains a consensus hard fork at block 148000. Every node,
masternode, pool and exchange must be running v1.3.2 before that block, or it will
follow a different chain after it.
Stop the daemon, replace the binaries, restart. No reindex is required.
If your masternode is currently PoSe-banned, revive it from your controller wallet
with protx update_service (BroodNode operators: protx update_service_evo).
A ban does not clear on its own, and upgrading alone does not clear it. Your
collateral is never at risk; payouts resume once the node is back in the active
set. Masternodes must run unpruned.
Verify your downloads against SHA256SUMS before running.