[codex] Record Base canary source verification#91
Merged
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
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.
Summary
Records the completed BaseScan source verification pass for the Base canary deployment and hardens the verification helper after the live submit run:
FlowMemoryHookAdapterwas verified against deployment-source commit11d562c, while currentmaincontains the newer v4-shaped callback source;--continue-on-errorand--delay-mssupport for explorer rate-limit handling.Validation
node --check infra/scripts/verify-base-canary-sources.mjsnpm run verify:base-canary:sources -- --check-bytecode --rpc-url https://mainnet.base.org --jsonnpm run launch:candidateSecurity note
The API key used for verification was not committed. Because it appeared in chat and one pre-fix error path, it should be rotated outside the repo.