[codex] Build Base canary launch readiness#82
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
This PR turns the live Base canary work into a coherent launch-readiness package:
/canarymode that keeps live-read canary state separate from local fixture mode;afterSwapcallback path with tests while preserving the boundary that this is not a production PoolManager hook deployment;Closes #76.
Closes #77.
Closes #79.
Advances #78.
Validation
forge testnpm testnpm test --prefix apps/dashboardnpm run build --prefix apps/dashboardnpm run launch:candidatenpm run verify:base-canary:sources -- --check-bytecode --rpc-url https://mainnet.base.org --jsonBoundary
This is canary/launch-readiness work. It does not claim production L1 readiness, production Uniswap v4 hook deployment, production verifier trustlessness, token custody, dynamic fees, or AI running on-chain.