github serenita-org/vero v1.5.0-rc.0

pre-release4 hours ago

Vero v1.5.0-rc.0 adds support for the Gloas fork on the Hoodi testnet, including new validator duties and post-Gloas builder configuration.

Hoodi operators should upgrade before Gloas activates at epoch 132352 (Oct-26-2026 17:42:48 UTC).

This is a Hoodi-only release. It is incompatible with Ethereum mainnet, Gnosis Chain, and the Chiado testnet. Operators on those networks should continue using v1.4.1.

Vero v1.5.0-rc.0 is compatible with the Glamsterdam-ready client releases listed below. Ensure you are running compatible client versions before updating Vero.

Version
Grandine 3.0.0-rc.1
Lighthouse v8.3.0
Lodestar v1.50.0
Nimbus v26.10.1
Prysm v7.3.0
Teku 26.10.1

🧱 Gloas support

Vero now supports payload timeliness committee (PTC) duties, signed proposer preferences, and execution payload envelope signing and publication for locally built blocks. Attestation and sync committee duties follow earlier deadlines introduced with Gloas. After Gloas, connected beacon nodes can contact builders directly using the configuration supplied by Vero:

Flag Description Default
--builder-urls Comma-separated list of builder URLs Empty
--builder-min-bid Minimum accepted builder bid, in Gwei 0
--builder-max-execution-payment Maximum trusted execution payment, in Gwei 0

The existing --builder-boost-factor continues to control the preference for externally built blocks.

Builder bid selection is handled by the connected beacon nodes. Pre-Gloas validator registrations remain controlled by --use-external-builder.

⛽️ Scheduled Gas Limits

Vero now supports EIP-8261 gas limit schedules after Gloas. Hoodi’s configured default increases to 200 million gas at epoch 132352.

Gas limit preferences use the following precedence:

  1. Per-validator override configured through the Keymanager API.
  2. Explicit --gas-limit setting.
  3. Active network gas limit schedule, falling back to the network default pre-Gloas.

Explicit settings above the scheduled recommendation produce a warning and remain honored.

💻 Beacon node URLs no longer require unique hostnames

Previously, Vero required all beacon node URLs provided via --beacon-node-urls to have unique hostnames. As of this release, you can add multiple beacon nodes running on the same host on different ports without having to alias them.

📊 Monitoring Changes

Action required for custom dashboards and alerts: the host metric label has been renamed to netloc. Its value now identifies the host and port, allowing multiple services on the same host to be distinguished.

Both bundled Grafana dashboards have been updated. The dashboards uids have been updated to io-serenita-vero-detailed and io-serenita-vero-simple.

Additional monitoring changes:

  • New vc_published_ptc_attestations_total and vc_published_payload_envelopes_total metrics
  • Add Grafana panel for published PTC attestations.

Changes included in this release

Features

Bug Fixes

  • Fix race condition in duties update logic by @eth2353 in #339
  • Fix voluntary exit signature domain in Keymanager API by @eth2353 in #336

Maintenance

Full Changelog: v1.4.1...v1.5.0-rc.0

Don't miss a new vero release

NewReleases is sending notifications on new releases.