Skip to content

Conversation

@geoknee
Copy link
Contributor

@geoknee geoknee commented Oct 3, 2025

Description

Tests

Additional context

Metadata

@geoknee geoknee added the H-l1-fusaka-defense Soft fork for being compatible with an L1 which has activated Fusaka label Oct 3, 2025
@geoknee geoknee marked this pull request as ready for review October 3, 2025 14:08
@geoknee geoknee requested review from a team as code owners October 3, 2025 14:08
@geoknee geoknee added the M-do-not-merge Meta: Do not merge label Oct 3, 2025
@sebastianst sebastianst enabled auto-merge October 3, 2025 20:30
@sebastianst sebastianst added this pull request to the merge queue Oct 3, 2025
Merged via the queue into develop with commit 05ba528 Oct 3, 2025
67 checks passed
@sebastianst sebastianst deleted the gk/skip-blob-verification branch October 3, 2025 20:56
geoknee added a commit that referenced this pull request Oct 6, 2025
…e skipped via `l1.beacon.skip-blob-verification` flag (#17713)"

This reverts commit 05ba528.
github-merge-queue bot pushed a commit that referenced this pull request Oct 6, 2025
…17725)

* recompute blob proof if skipBlobVerification

* use even simpler verification

* replace verification logic

* refactor to make verification more direct

This approach does not use any additional data from the beacon endpoint, aside from the blob itself, so anticipates future API changes where this will be the only data provided.

* tweak comments

* rename to verifyBlob

* tweak test comments

* Revert "op-service/L1BeaconClient: allow blob proof verification to be skipped via `l1.beacon.skip-blob-verification` flag (#17713)"

This reverts commit 05ba528.

* Revert "Add `skip-blob-verification` flag to op-program and op-challenger  (#17718)"

This reverts commit 3ee883b.

* add an extra unit test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

H-l1-fusaka-defense Soft fork for being compatible with an L1 which has activated Fusaka

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants