Node upgrades
Release verdicts for GenLayer nodes, published on-chain by the Changelog Guard intelligent contract: validators read the release notes and must agree on what an operator has to do.
Current verdict
[01]None in this release.
None in this release.
Source: docs.genlayer.com/validators/changelog · first seen by WatchLayer 2h 7m ago
Release history
[02]| Version | Mandatory | Breaking | First seen |
|---|---|---|---|
| v0.5.14 | No | No | 2h 7m ago |
How a verdict is produced
[03]1 · Submit
Anyone calls submit(network, version, url) with a release page from docs.genlayer.com or a genlayerlabs release tag.
2 · Read and extract
The leader fetches the page, keeps only that version's section and asks an LLM for a strict JSON verdict.
3 · Validators agree
Every validator repeats the extraction and compares: exact on version, mandatory, breaking and deadline; at least 80% overlap on config and env keys.
4 · Alert
WatchLayer reads the stored verdict and the Telegram bot alerts subscribers when a mandatory release is newer than the tracked version.
Contract source and tutorial: github.com/blockhunters-dev/genlayer-changelog-guard