Gloas hardfork

[KaloyanTanev]

🎯 Problem to be solved

Prepare Charon for gloas hardfork

🛠️ Proposed solution

• Gloas groundwork
  • Spec-driven per-fork slot timing (*: configurable time offset for different duties in a slot #4617)
  • Migrate SSZ from fastssz to dynssz (*: migrate from fastssz to dynssz #4652)
  • Bump go-eth2-client to gloas types + transport (v0.29.0-obol.2-gloas)
  • Gloas in the fork schedule (core/scheduler: resolve payload timeliness committee duties #4659)
• PTC (payload attestation) duty
  • DutyPayloadAttestation duty type + PTC signing domain (*: add PayloadAttestation duty #4618)
  • Core types: PayloadAttestationData, SignedPayloadAttestationMessage (core: add payload attestation types for gloas #4653)
  • DutyDB support (core/dutydb: support payload attestation duty #4656)
  • VC endpoints: payload_attestation_data + pool submission (core/validatorapi: add payload attestation endpoints #4657)
  • Adopt go-eth2-client payload attestation interfaces (core/validatorapi: adopt payload attestation interfaces #4658)
  • Scheduler duty resolution (core/scheduler: resolve payload timeliness committee duties #4659)
  • Fetcher: fetch data, handle 204 no-block-seen (core/fetcher: fetch payload attestation data #4667)
  • Versioned payload attestation data + message types (core: version payload attestation data #4663, core: version and broadcast payload attestation message #4668)
  • Bcast: submit aggregated messages (core: version and broadcast payload attestation message #4668)
  • Serve duties/ptc from charon with pubshare mapping (core/validatorapi: serve ptc duties #4669)
  • validatormock support + e2e simnet test (testutil: vmock payload attestation and simnet e2e #4670)
• Fork readiness observability
  • Readiness metrics for charon/BN/VC/EL (app/eth2wrap: add fork readiness metrics #4660)
  • Populate per-fork minimum client versions once fork-ready releases exist
  • Fork-aware proposer deadline, SSE thresholds, quarter-slot buckets (core/app: fork-aware slot fraction timings #4676)
  • Retitle Grafana Charon Overview v3 "%% of Blocks Processed after 4s" panel to 3s after gloas activation
• Attestations
  • Accept gloas-versioned attestations (core: accept gloas versioned attestations #4671)
  • Optional deprecated committee_index query param (core/validatorapi: optional committee index param #4672)
  • data.index payload-status bit: no handling needed, BN sets it and charon agrees on data opaquely; regression test (core: accept gloas versioned attestations #4671)
• Block production (ePBS)
  • Produce block v4 with include_payload (self-build) — POST /eth/v4/validator/blocks/{slot} with a BuilderConfig body (beacon-APIs#630). Stack in review: *: adopt go-eth2-client v0.29.0-obol.4-gloas #4715 client bump, core: gloas epbs proposal data types #4717 core types, core/fetcher: fetch gloas epbs proposals #4718 fetcher, core/validatorapi: serve and accept gloas epbs proposals #4719 validatorapi, testutil: vmock gloas epbs proposals and simnet e2e #4720 validatormock + simnet e2e
    • Core EPBS proposal types — payload-included/excluded discriminator, no blinded semantics (core: gloas epbs proposal data types #4717)
    • Fetcher: fetch gloas EPBS proposals, fork-schedule aware, single attestation fetch, verify self-built fee recipient (core/fetcher: fetch gloas epbs proposals #4718)
    • ValidatorAPI: always serve stateless (payload-included) proposals + accept signed EPBS proposals, gated on gloas onwards (core/validatorapi: serve and accept gloas epbs proposals #4719)
    • validatormock + gloas EPBS simnet e2e (testutil: vmock gloas epbs proposals and simnet e2e #4720)
    • Proxy the BuilderConfig body: substitute threshold-aggregated SignedBuilderRequestAuths for the VC's partial ones before forwarding to the BN — deferred to the builder preferences duty (core: gloas builder preferences duty (SignedBuilderRequestAuth aggregation) #4724); charon currently emits min_bid/builder_boost_factor with no builder entries (self-build only)
    • Watch beacon-APIs#627 produceBlockV4WithBid — explicitly motivated by multi-BN/DV setups, may become the preferred DV flow
  • Execution payload envelope publishing — remaining arc for external / P2P builder bids
    • (up for discussion / review — do we need it?) Forward the broadcast_validation query param (gossip default / consensus / consensus_and_equivocation) to the beacon node. Currently dropped for every duty, block proposals included: charon always broadcasts at the BN default (gossip). Cross-cutting — the requested level would have to be carried as duty metadata through parsig → sigagg → bcast, so scope it across block proposals and envelopes together (they share the consensus_and_equivocation anti-unbundling motivation)
  • Proposer preferences signed duty — supersedes prepare_beacon_proposer + register_validator (core: proposer preferences signed duty (gloas ePBS) #4691); implementation in review (core: add gloas proposer preferences duty #4693 + *: adopt go-eth2-client v0.29.0-obol.4-gloas #4715/testutil: vmock proposer preferences and simnet e2e #4716)
    • Adopt go-eth2-client proposer-preferences interfaces (*: adopt go-eth2-client v0.29.0-obol.4-gloas #4715)
    • DutyProposerPreferences type + DOMAIN_PROPOSER_PREFERENCES (core: add gloas proposer preferences duty #4693)
    • Core (Versioned)ProposerPreferences + partial-signed type (core: add gloas proposer preferences duty #4693)
    • Serve v2 proposer duties with the E-2 shuffling dependent_root — client-native v2 duties + cache (*: adopt go-eth2-client v0.29.0-obol.4-gloas #4715); cache invalidation on dependent_root change tracked separately (app/eth2wrap: invalidate duties cache on dependent_root change #4710)
    • SubmitProposerPreferences intake (sync-message model, non-blocking 2XX) (core: add gloas proposer preferences duty #4693)
    • ParSigDB/ParSigEx/SigAgg; key by (validator, proposal_slot, dependent_root) (core: add gloas proposer preferences duty #4693)
    • Bcast: submit the aggregate to the BN ahead of the slot, delay anchored to earliest submission (*: adopt go-eth2-client v0.29.0-obol.4-gloas #4715)
    • Warn + metric on fee_recipient / gas_limit mismatch vs lock (core: add gloas proposer preferences duty #4693)
    • validatormock + simnet e2e (testutil: vmock proposer preferences and simnet e2e #4716)
  • Builder preferences signed duty — see core: gloas builder preferences duty (SignedBuilderRequestAuth aggregation) #4724 for full scoping (spec provenance, per-client support table, aggregation design). PARKED: waiting for upstream go-eth2-client to re-land the builder types (interim port parked as draft Add gloas builder config and builder preferences types go-eth2-client#32) — SignedBuilderRequestAuth aggregation (builder-specs gloas/validator.md)
    • Mechanics: the proposer key signs BuilderRequestAuth{data, slot} under DOMAIN_BUILDER_REQUEST_AUTH — data is out-of-band bytes per builder (default: UTF-8 of the builder's advertised URL, byte-exact), slot is the proposal slot. One signature per (builder, proposal_slot) authenticates both submitBuilderPreferences and getExecutionPayloadBid. max_execution_payment is NOT signed (rides beside the auth). No timestamp / dependent_root → partials aggregate iff all VCs carry byte-identical builder url/auth_data (config alignment via app: distribute cluster proposer config (fee recipient / gas limit) to validator clients #4692). Submitted the epoch before the proposal (state.proposer_lookahead).
    • DutyBuilderPreferences type + DOMAIN_BUILDER_REQUEST_AUTH
    • Core signed data type for SignedBuilderRequestAuth; aggregation key (validator, proposal_slot, auth data)
    • VAPI intake: POST /eth/v1/validator/builder_preferences (batched BuilderPreferencesEntry; sync-message model, non-blocking 2XX; pubshare→pubkey swap; deterministic cluster max_execution_payment alongside the aggregated auth)
    • ParSigDB/ParSigEx/SigAgg + Bcast: forward aggregated entries to the BN ahead of the proposal (gated on go-eth2-client builder-preferences support)
    • Reuse the aggregated auths in the produce-block-v4 BuilderConfig proxy (see above)
    • validatormock + simnet e2e
  • Distribute cluster fee recipient / gas limit to VCs — charon-generated canonical sparse file, VC restart to apply; no keymanager API (app: distribute cluster proposer config (fee recipient / gas limit) to validator clients #4692; charon app: generate proposer config file for validator clients #4700 + CDVN app/log: remove caller from console logs #486/cmd: refactor to use create command #487 in review, all five VCs live-verified)
    • Extend to builder config: byte-identical builder url/auth_data (signed into the auth) + min_bid/builder_boost_factor/max_execution_payment across nodes (Prysm proposer-settings v2 extends the same file charon generates) (app: generate builder config for validator clients #4704)
  • Fork-gate legacy --builder-api behaviors at the gloas epoch — the flag's jobs all belong to the mev-boost architecture and dissolve post-gloas (participation becomes the granular --builder-* values; "enabled" ≈ non-empty builder URLs)
    • Scheduler: stop submitting validator registrations from the fork epoch (registrations are deprecated, superseded by the proposer preferences duty; nothing consumes them post-fork)
    • Fetcher/router: builder_boost_factor=MaxUint64 override only applies to produceBlockV3 (v4 takes it from the BuilderConfig body)
    • Infosync: builder vs full proposal-type negotiation is meaningless for v4 proposals (no blinded/full split)
    • Proposer config file: resolved by the canonical schema (app: generate proposer config file for validator clients #4700) — charon's file no longer carries builder.enabled; CDVN wrappers source it from the BUILDER_API_ENABLED env var
    • Deprecate the flag once pre-gloas support is dropped
• Testing
  • e2e duty timing migration test, thirds to quarters (testutil: vmock payload attestation and simnet e2e #4670)
  • Devnet testing

🔗 References

• Consensus spec (gloas)
• Beacon API