TGViewer
QNET QNET @aiqnetlab · 397 subscribers
Post #167 400
Currently, the test network has stopped releasing blocks. I’ll tell you what happened.

When a new light node registers on the network, all nodes must calculate the checksum of the node registry in the same way. It turned out that the node that had itself issued a block with such a registration calculated it differently from the others. It stopped matching the network in terms of the same number and could no longer confirm blocks.

Two light nodes registered. The first one disabled one node, the second one disabled the second one. After that, four out of the five required nodes remained, the confirmation stopped, and the network automatically suspended production. This is a standard safety feature: it’s better to stop than to diverge.

The data is intact. The entire history is in place, and the records are the same for all six nodes. Only one calculated value diverges, and it can be restored by recalculating it.

What I do: I restore agreement on the two affected nodes, fix the cause in the code so that this doesn’t happen again during registration, and update all the nodes.
  • 🔥 11
  • ❤ 3
  • ⚡ 1
More from @aiqnetlab
  1. Oct 8, 2026In a few days, I will restore activation via the website and mobile app.
  2. Oct 8, 2026QNet Wallet 1.3.0 for Android is now live on Google Play: https://play.google.com/store/ap…
  3. Oct 7, 2026Two weeks of work in one release: 1,165 files, +277,456 / −68,696 lines, 82k of them tests…
  4. Oct 5, 2026Congratulations, everyone: after a year, QNet Wallet is finally on Google Play. This is a…
  5. Oct 2, 2026Dashboard, Mobile Apps & Extension I am almost done with a major update for the dashboard…
  6. Sep 25, 2026👀
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →