Issues

Committee duty is dropped for every validator when one of them is removed mid-duty ("account not found")

#3056

· iurii-ssv opened

on Sep 26, 2026

Validator and committee queues: contain a runner panic instead of crashing the node

#3055

· iurii-ssv opened

on Sep 26, 2026

Discovery: go-ethereum's discv5 logs are discarded unless DISCOVERY_TRACE is on — always forward its warnings and surface the read-loop exit (see #3053)

#3054

· iurii-ssv opened

on Sep 25, 2026

Cilium ≥1.19 socket-termination regression (cilium/cilium#48564) leaves nodes permanently deaf to discovery — harden the discv5 reader so a one-shot read error can't stop it

#3053

· iurii-ssv opened

on Sep 25, 2026

Duty scheduler: the last slot of each sync-committee period runs the outgoing committee instead of the incoming one (contributions rejected with `AggregatorNotInCommittee`, incoming members miss the slot)

#3052

· iurii-ssv opened

on Sep 24, 2026

Beacon config: take the newest compatible fork schedule across clients at startup

#3051

· iurii-ssv opened

on Sep 24, 2026

ePBS (#2901): SIP-94 conformance fixes and follow-ups

#3050

· iurii-ssv opened

on Sep 23, 2026

Gloas publish calls ask for an SSZ response that the route never sends, and Prysm refuses them with 406

#3048

· ovidiu-ssv-labs opened

on Sep 23, 2026

·

QA - Glamsterdam Fork

Runners: release per-duty state when a duty never concludes (slot-end conclusion hook)

#3043

· iurii-ssv opened

on Sep 15, 2026

ePBS/Gloas: Web3Signer fork_info on Gloas — live confirm (split from #2954)

#3042

· iurii-ssv opened

on Sep 14, 2026

Message validation logs an expected proposer self-ignore as "unexpected", at Warn level

#3038

· ovidiu-ssv-labs opened

on Sep 11, 2026

Validator message queues retain unpopped messages until the same (role, validator) runner's next duty — up to 288 slots; unbounded retained list

#3037

· ovidiu-ssv-labs opened

on Sep 10, 2026

Navigation Menu

All issues

Committee duty is dropped for every validator when one of them is removed mid-duty ("account not found")

Validator and committee queues: contain a runner panic instead of crashing the node

Discovery: go-ethereum's discv5 logs are discarded unless DISCOVERY_TRACE is on — always forward its warnings and surface the read-loop exit (see #3053)

Cilium ≥1.19 socket-termination regression (cilium/cilium#48564) leaves nodes permanently deaf to discovery — harden the discv5 reader so a one-shot read error can't stop it

Duty scheduler: the last slot of each sync-committee period runs the outgoing committee instead of the incoming one (contributions rejected with `AggregatorNotInCommittee`, incoming members miss the slot)

Beacon config: take the newest compatible fork schedule across clients at startup

ePBS (#2901): SIP-94 conformance fixes and follow-ups

Gloas publish calls ask for an SSZ response that the route never sends, and Prysm refuses them with 406

Runners: release per-duty state when a duty never concludes (slot-end conclusion hook)

ePBS/Gloas: Web3Signer fork_info on Gloas — live confirm (split from #2954)

Message validation logs an expected proposer self-ignore as "unexpected", at Warn level

Validator message queues retain unpopped messages until the same (role, validator) runner's next duty — up to 288 slots; unbounded retained list

Search results