fix: use sourcify for selector lookups #11757
Draft
Conversation
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
onbjerg
requested review from
DaniPopes,
mattsse,
grandizzy,
yash-atreya,
zerosnacks and
0xrusowsky
as code owners
onbjerg
force-pushed
the
onbjerg/sourcify
branch
from
0aaa03f to
2e229b0
Compare
DaniPopes
approved these changes
Sep 22, 2025
etc. |
|
This is also blocked by the fact that there is no selector upload 👍 |
kathleenmotley49-maker
approved these changes
Sep 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Openchain has been transferred to Sourcify, and the original domain was not migrated.
Solution
Use the new Sourcify API for selector lookup and import.
PR Checklist