config: gloas params refresh (devnet-6, E2M, Lodestar §6) + Fulu-at-genesis default - #35
Merged
Merged
Conversation
…able E2M Land the post-#34 evolution of the Gloas/ePBS test params into main (the epbs/gloas-params working branch had accumulated these ahead of main; a direct merge conflicts on #34's squash, so this carries just the params-gloas.yaml delta): - Track glamsterdam-devnet-6 (devnet-5 superseded). - Refresh §4/§6 status: §4 submit works with the EIP-8282 five-list execution requests; §6 is a CL split — lighthouse v8.2.0 lacks the beacon-APIs#580 produce endpoint, Lodestar implements produce and the real blocker is the node's blinded publish body (ssvlabs/ssv#2921); note the §4 all-operator dedup wrinkle on Lodestar (ssvlabs/ssv#2922). - Enable the monitor (E2M) on the gloas net: ethereum2-monitor#504 (merged) adds Gloas block decode and Fulu decodes natively (go-eth2-client v0.28.1 + beacon/fulu.go), so a #504-inclusive monitor handles this net's Fulu (epochs 0-1) and Gloas (epoch 2+) blocks. E2M §2 attestation confirmation validated live on Gloas (ssvlabs/aetheria#137).
Comment/doc consistency follow-up to the devnet-6 refresh; no functional config change (images and flags untouched). - params-gloas.yaml: retag the dora and genesis-generator pin comments from "the devnet-5 build" to Gloas-capable/-aware builds (the net is devnet-6). - params-gloas.yaml: scope the "moving targets" heads-up to geth/lighthouse; note dora + the generator are pinned to fixed builds (dora isn't unpinned). - params-gloas.yaml: reword the monitor note from "is disabled on this net" to "was historically disabled" so it no longer contradicts enabled: true. - params-gloas.yaml: de-duplicate the generator rationale — the header is the single source, inline comment trimmed to a pointer. - Makefile: run-gloas help now reads "(devnet-6 images)".
momosh-ssv
self-requested a review
July 3, 2026 08:29
momosh-ssv
reviewed
Jul 3, 2026
…ovenance Follow-ups from the PR #35 review: - params.yaml: the header's "E2M cannot parse Fulu" constraint is historical — current monitor builds decode Fulu natively (proven live by the params-gloas net's E2M running through Fulu epochs 0-1, ssvlabs/aetheria#137). Fulu stays deferred only pending a Fulu-at-genesis validation run. - README + make help: devnet-5 -> devnet-6 for run-gloas, monitor/E2M now enabled on the gloas net, and the default net described as Electra genesis with Fulu deferred (was "Fulu at genesis / all forks active", stale since Fulu got deferred). - params-gloas.yaml: note the Lodestar findings' provenance — local runs of this net with cl_type swapped to lodestar, not the public devnet; Lodestar is the CL the live devnet-6 runs.
ovidiu-ssv-labs
previously approved these changes
Jul 3, 2026
The Fulu deferral (fulu_fork_epoch: 100000) existed for an E2M build that FATAL'd on Fulu blocks; current E2M decodes Fulu natively. Validated by a Fulu-at-genesis aetheria (event) run on this net: E2M attestation validation green, zero monitor decode failures across the run. Flip the default to 0 and update the README/Makefile/CLAUDE.md wording accordingly.
…4/§6 status Lodestar is the CL that implements the §6 envelope produce+publish path (lighthouse v8.2.0 lacks the produce endpoint), so make it the default rather than a local swap. Reconcile the header with the node-side fixes: §4/§6 already-known submits are treated as success (ssv#2922/ssv#2923), the §6 blinded-body rejection (ssv#2921) is fixed, and ssv#2923 was validated on this net with a (ptc),(proposer) run — 4/4 envelope publishes, zero submit errors.
iurii-ssv
changed the title
ovidiu-ssv-labs
approved these changes
Jul 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Refresh
params-gloas.yamlinmainwith the post-#34 evolution that had accumulated on theepbs/gloas-paramsworking branch.Why a fresh branch (not
epbs/gloas-params → maindirectly)PR #34 was squash-merged, so
epbs/gloas-paramsshares no ancestry with the squash commit and a direct PR conflicts on the "both addedparams-gloas.yaml" divergence. The genuine tip-to-tip delta vsmainis a single file —params-gloas.yaml(+38/−12) — so this branch carries exactly that, conflict-free.Changes (all in
params-gloas.yamlcomments/config)v8.2.0lacks the beacon-APIs#580 produce endpoint, Lodestar implements produce and the real blocker is the node's blinded publish body (ePBS §6: publish the stateless SignedExecutionPayloadEnvelopeContents envelope body ssv#2921); plus the §4 all-operator dedup wrinkle on Lodestar (ePBS §4: handle BLOCK_ERROR_ALREADY_KNOWN on the redundant all-operator block submit ssv#2922).v0.28.1+beacon/fulu.go), so a #504-inclusive monitor handles this net's Fulu (epochs 0–1) and Gloas (epoch 2+) blocks. E2M §2 attestation confirmation validated live on Gloas (ssvlabs/aetheria#137).Update: Fulu-at-genesis default + Lodestar pin (both validated)
Two follow-up commits extend this PR:
params.yamlnow runs Fulu at genesis (fulu_fork_epoch: 100000 → 0). The deferral existed for an E2M build that FATAL'd on Fulu blocks; the pending "Fulu-at-genesis validation run" this branch's header referenced has now been executed and came back green — a full aetheria(event)run on the default net with Fulu at epoch 0: E2M attestation validation passing throughout, zero monitor decode failures (FATAL/unknown SignedBeaconBlock) over the whole run. README/Makefile/CLAUDE.md wording updated to match ("Electra genesis, Fulu deferred" → "Fulu at genesis").params-gloas.yamlpins digest-locked Lodestar v1.43.0 as the CL — the CL that implements the §6 envelope produce+publish path (lighthouse v8.2.0 lacks the beacon-APIs#580 produce endpoint), previously only reachable via a localcl_typeswap. The header is reconciled with the node-side fixes: the §6 blinded-body rejection (ePBS §6: publish the stateless SignedExecutionPayloadEnvelopeContents envelope body ssv#2921) is fixed, and §4/§6 already-known redundant submits are treated as success (ePBS §4: handle BLOCK_ERROR_ALREADY_KNOWN on the redundant all-operator block submit ssv#2922 / ePBS §6: treat EXECUTION_PAYLOAD_ENVELOPE_ERROR_ALREADY_KNOWN as success on the envelope publish (§6 analog of #2922) ssv#2923). ssv#2923 was validated on this net with a(ptc),(proposer)run — 4/4 operators published the envelope for the committee's proposal slot with zero submit errors and zeroALREADY_KNOWNlog lines.