Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3709f1dba6
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| bytes memory _bundle, | ||
| CallStatus[] calldata _providedCallStatus | ||
| ) public { | ||
| function unbundleBundle(bytes memory _bundle, CallStatus[] calldata _providedCallStatus) public { |
There was a problem hiding this comment.
Keep legacy unbundle selector routable
Changing unbundleBundle to unbundleBundle(bytes,uint8[]) changes the function selector (from 0x98483918 to 0x37dd8238 in l1-contracts/selectors), but receiveMessage still dispatches strictly by selector and reverts unknown selectors, so any in-flight message encoded before this upgrade with the old unbundleBundle(uint256,bytes,uint8[]) selector will no longer be executable after deployment. This is a backward-compatibility break for queued cross-chain bundles, so the old selector path should remain supported (with legacy decoding) alongside the new one.
Useful? React with 👍 / 👎.
|
Coverage after merging sma/refactor-interop-handler into draft-v31 will be
Coverage Report
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
## What ❔ Sister PR to: matter-labs/era-contracts#2056 <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- The `Why` has to be clear to non-Matter Labs entities running their own ZK Chain --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Is this a breaking change? - [ ] Yes - [ ] No ## Operational changes <!-- Any config changes? Any new flags? Any changes to any scripts? --> <!-- Please add anything that non-Matter Labs entities running their own ZK Chain may need to know --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zkstack dev fmt` and `zkstack dev lint`.
What ❔
Sister PR to: matter-labs/zksync-era#4683
Why ❔
Checklist