Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: 3074 support #168

Merged
merged 2 commits into from
Apr 15, 2024
Merged

fix: 3074 support #168

merged 2 commits into from
Apr 15, 2024

Conversation

gzeoneth
Copy link
Member

@gzeoneth gzeoneth commented Apr 15, 2024

This PR

  • Add deprecation notice to function affected by EIP-3074
  • Deprecate sendL2MessageFromOrigin
    • This is a breaking change but should be fine because as of now only an EOA can call this method, so we are not going to run into issue like breaking an immutable contract. Alternatively, we can have this entrypoint call into the non-origin entrypoint but may require changes in the nitro node to locate the data properly.

SequencerInbox fromOrigin entrypoints are not removed yet, it will be fixed before EIP-3074 ship and when we have more clarity on its implementation. Since those entrypoints are only callable by the sequencer it pose less risk than the permissionless sendL2MessageFromOrigin and hence not removed in this PR for now.

@cla-bot cla-bot bot added the s label Apr 15, 2024
emit InboxMessageDeliveredFromOrigin(msgNum);
return msgNum;
function sendL2MessageFromOrigin(bytes calldata) external pure returns (uint256) {
revert Deprecated();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't we just call the non-from-origin variant here? Afaik the only difference is gas usage, I don't think there's an aliasing difference or anything

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can, but as described in the PR I don't think we need to and would prefer the simplicity of deprecating the function entirely

Copy link
Contributor

@shotaronowhere shotaronowhere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gzeoneth gzeoneth merged commit db0ba96 into delay-buffer Apr 15, 2024
9 of 11 checks passed
@gzeoneth gzeoneth deleted the todo-3074 branch April 15, 2024 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants