Skip to content

revert(L1): undo AggregateVerifier cadence changes in v8.3.0 - #436

Merged
jackchuma merged 3 commits into
releases/v8.3.0from
backport/v8.3.0-revert-aggregate-verifier
Sep 14, 2026
Merged

jackchuma merged 3 commits into
releases/v8.3.0from
backport/v8.3.0-revert-aggregate-verifier

Conversation

@jackchuma

Copy link
Copy Markdown
Collaborator

What changed? Why?

Notes to reviewers

  • The three commits were reverted newest-first.
  • just snapshots completed with a clean tree.
  • just test: 1,220 passed, 0 failed, 1 skipped.

Made with Cursor

@jackchuma
jackchuma merged commit e009b09 into releases/v8.3.0 Sep 14, 2026
3 checks passed
@jackchuma
jackchuma deleted the backport/v8.3.0-revert-aggregate-verifier branch September 14, 2026 18:38
jackchuma added a commit that referenced this pull request Sep 14, 2026
OptimismPortal2, DisputeGameFactory, and AggregateVerifier all have source
changes relative to the versions currently deployed onchain, but still declare
the same semver. Bump each so the onchain version distinguishes the artifacts.

- OptimismPortal2 5.2.0 -> 6.0.0: ETHLockbox removal drops the `ethLockbox()`
  getter and the `OptimismPortal_InvalidLockboxState` error from the ABI.
- DisputeGameFactory 1.4.0 -> 1.5.0: game proxies are now deployed with
  `cloneDeterministic`; the ABI is unchanged.
- AggregateVerifier 0.1.0 -> 0.2.0: the schedule-pinning work landed after
  0.1.0 shipped, and reverting the cadence changes in #436 also reverted the
  version, leaving it colliding with the released 0.1.0.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant