Skip to content

OPB-02: Raise error on oversized chain id#3620

Merged
mergify[bot] merged 2 commits intodevelopfrom
op-node/fillbytes-size-checks
Oct 4, 2022
Merged

OPB-02: Raise error on oversized chain id#3620
mergify[bot] merged 2 commits intodevelopfrom
op-node/fillbytes-size-checks

Conversation

@maurelian
Copy link
Contributor

@maurelian maurelian commented Sep 29, 2022

Description

Fixes OPB-02.

This is a draft, POC for how I'd do this in signer.go. Two other locations still need fixing which I'll do in a subsequent PR once this is approved.

Tests

No new tests are added as it's unclear how this would actually be reachable, however it was decided to include it as "future proofing".

@changeset-bot
Copy link

changeset-bot bot commented Sep 29, 2022

⚠️ No Changeset found

Latest commit: b115db2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@mergify
Copy link
Contributor

mergify bot commented Sep 29, 2022

This PR changes implementation code, but doesn't include a changeset. Did you forget to add one?

@maurelian maurelian force-pushed the op-node/fillbytes-size-checks branch from e69f994 to caa4690 Compare September 29, 2022 20:19
@maurelian maurelian force-pushed the op-node/fillbytes-size-checks branch from caa4690 to bd3d1b7 Compare October 3, 2022 17:11
@maurelian maurelian force-pushed the op-node/fillbytes-size-checks branch from bd3d1b7 to 80b79bb Compare October 3, 2022 17:59
@maurelian maurelian marked this pull request as ready for review October 3, 2022 17:59
Copy link
Contributor

@protolambda protolambda left a comment

Choose a reason for hiding this comment

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

LGTM. Technically the FillBytes usages are all safe; chain ID is loaded exclusively from local configuration. And the other usages from OPB-2 are all through other safe code paths (deposit fields are from test only code-paths, and basefee size is checked by the json decoder). Still nice to catch any potential issues when the code is used wrong or called in unexpected ways however. Nice fix. The other OPB-02 fixes can also go in a separate PR.

@trianglesphere
Copy link
Contributor

The PR description needs to be updated. I also am re-running the e2e tests b/c they timed out. It seems like a flake given these changes, but we'll have to see.

@maurelian
Copy link
Contributor Author

@trianglesphere seems to all be working now

@mergify
Copy link
Contributor

mergify bot commented Oct 3, 2022

This PR has been added to the merge queue, and will be merged soon.

@mergify
Copy link
Contributor

mergify bot commented Oct 3, 2022

This PR is next in line to be merged, and will be merged as soon as checks pass.

1 similar comment
@mergify
Copy link
Contributor

mergify bot commented Oct 3, 2022

This PR is next in line to be merged, and will be merged as soon as checks pass.

@mslipper
Copy link
Contributor

mslipper commented Oct 4, 2022

CircleCI errored out and didn't mark completed jobs as done, so they hung. Restarted the jobs to get this through.

@mergify mergify bot merged commit 1bcd11e into develop Oct 4, 2022
@mergify mergify bot deleted the op-node/fillbytes-size-checks branch October 4, 2022 00:57
@mergify mergify bot removed the on-merge-train label Oct 4, 2022
This was referenced Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants