You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(evm): don't create single sequencer for non-aggregator nodes (#3389)
* fix(evm): don't create single sequencer for non-aggregator nodes
P2P-only followers (no DA address) crashed on startup with a nil
pointer dereference: the EVM app's createSequencer unconditionally
built a single sequencer, whose forced-inclusion retriever calls
GetForcedInclusionNamespace on the nil DA client.
Mirror the testapp guard from #3386 by skipping sequencer creation
for non-aggregators, and fail fast in single.NewSequencer when the
DA client is nil so future regressions surface as a clean error
instead of a SIGSEGV.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix: keep sequencer for promotable followers and require DA for promotable mode
Promotable nodes start as followers but can be promoted to proposer at
runtime, which hands the sequencer to the aggregator components. The
non-aggregator guard (added to testapp in #3386 and mirrored here for
the EVM app) would leave promotable nodes with a nil sequencer and
break promotion. Create the sequencer for promotable nodes too, and
require a DA address for promotable mode at config validation, same as
aggregator mode.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
0 commit comments