Hey hey, human nodes!
We recently encountered two incidents related to finality stalls (an occurrence when the consensus process fails to decide on the final state of the block within a specified period). As a quick response, we have implemented a workaround that is now deployed. Rest assured, devs are actively working on a more comprehensive fix, which we will ship after thorough testing.
🔑 Key Details about the issue:
The cause of the issue seems to be that with our network growing to over 1,000 validators (yes we have crossed the 1K nodes landmark), we are pushing the limits of our core consensus and gossip algorithms. This has caused us to encounter rarely visited code paths that are typically dormant. While Kusama and Polkadot, with whom we share our codebase have not seen these issues, we are committed to resolving this for the Humanode.
👉What you need to do:
Update your node. If you are running the node using Humanode Launcher, go to
Settings and Click on Check for Peer Updates.We’ll be closely monitoring the rollout via https://telemetry.humanode.io/ and you are welcome to follow along as well. The target version is f5bccf0d13193e070aeef1472a2a4726e836cd93
Note that this update will delay the finality target for 5 blocks behind the best block which is expected so no need to worry. Please adjust monitoring and your dApp settings accordingly.
We appreciate your cooperation and attention.
Humanode Core