proxyd: cap latest at cross-unsafe block - #618
Draft
karlfloersch wants to merge 1 commit into
Draft
karlfloersch wants to merge 1 commit into
karlfloersch wants to merge 1 commit into
Conversation
karlfloersch
force-pushed
the
codex/proxyd-cross-unsafe-latest-cap
branch
2 times, most recently
from
May 6, 2026 03:50
700f74b to
296360a
Compare
karlfloersch
force-pushed
the
codex/proxyd-cross-unsafe-latest-cap
branch
from
May 11, 2026 18:46
296360a to
3273e8e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an opt-in proxyd interop validation setting that polls
supervisor_getLatestCrossUnsafeBlock(chain_id)and caps consensuslatestrewrites to the returned block number. When enabled but no cap has been fetched yet, proxyd fails closed by using block 0 rather than falling back to EL latest.Also adds an authenticated bypass list so trusted internal callers, like op-interop-filter ingestion, can use a dedicated proxyd auth alias and avoid the circular dependency where the filter needs uncapped blocks to advance the cap.
Motivation
This lets proxyd avoid serving unsafe-chain blocks beyond the latest block that op-interop-filter has cross-unsafe validated, while still allowing the filter itself to ingest from proxyd.
Validation
go test ./...fromproxyd/Dependency
Depends on the op-interop-filter RPC endpoint from the companion monorepo PR.