You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🔴 I experienced an error, well can this be called an error?, or a BUG? hmm, I think it's both. My node was validated 20 hours ago but the "Rotation Index" showed the number 111/1270 during the time I spent validating the Rotation Index number did not change and was stuck at 111/1270. 🔴
What impact does the issue have?
🔴 The impact of the problem I experienced was that my node in the Rotation Index seemed to not be running and was stuck at 111/1270 for more than 20 hours, and I experienced this after updating to the latest version, namely 1.16.3.
I hope this problem will be fixed soon so that it doesn't have a significant impact on the Shardeum network itself. 🔴
How to reproduce the issue?
🔴
Explain in as much detail as possible to help reproduce the bug:
1. Stuck On "Rotation Index" 111/1270 when validating from 20 hours ago
🔴
What other resources can you share regarding this issue?
🔴
🔴
The text was updated successfully, but these errors were encountered:
What is the issue?
🔴 I experienced an error, well can this be called an error?, or a BUG? hmm, I think it's both. My node was validated 20 hours ago but the "Rotation Index" showed the number 111/1270 during the time I spent validating the Rotation Index number did not change and was stuck at 111/1270. 🔴
What impact does the issue have?
🔴 The impact of the problem I experienced was that my node in the Rotation Index seemed to not be running and was stuck at 111/1270 for more than 20 hours, and I experienced this after updating to the latest version, namely 1.16.3.
I hope this problem will be fixed soon so that it doesn't have a significant impact on the Shardeum network itself. 🔴
How to reproduce the issue?
🔴
Explain in as much detail as possible to help reproduce the bug:
🔴
What other resources can you share regarding this issue?
🔴
🔴
The text was updated successfully, but these errors were encountered: