-
Notifications
You must be signed in to change notification settings - Fork 0
ClassicProtocolSpecs
Diego López León edited this page Jun 2, 2026
·
1 revision
Verdict: Rewritten to the adapter API — behaviourally equivalent, not a port
Natively this class was wired straight into Besu's schedule engine (MainnetProtocolSpecFactory / ProtocolScheduleBuilder) as a chain of inherited xxxDefinition methods. A plugin lives outside Besu and can't hook into that engine, so it was rewritten to emit adapters over the mainnet schedule through the new ProtocolScheduleCustomizer extension point. Net consensus state per fork is equivalent (verified), but the structure necessarily differs, so no line-by-line diff is shown — see Extension Points for the adapter list and rationale.
Auto-generated by generate-diffs.py · base 1167c5a544^.