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

[txmgr] Ensure that fee is increased by at least 10% #8747

Merged

Conversation

mdehoog
Copy link
Contributor

@mdehoog mdehoog commented Dec 22, 2023

Description

#8713 fixed a txmgr bug where if the fees were < 10, the fee would not be bumped at all.

This PR ensures we conform to the spec a little more, guaranteeing that we bump the fee by at least 10%.

For example, the current implementation will bump 11 to 12, which is not technically 10% more (because we do floor(fee * 1.1). This PR switches to use ceil(fee * 1.1).

Tests

Updated tests.

Additional context

go-ethereum currently rounds down internally, so this would not affect L1s running geth.

@mdehoog mdehoog requested a review from a team as a code owner December 22, 2023 17:57
Copy link
Contributor

coderabbitai bot commented Dec 22, 2023

Walkthrough

Walkthrough

The update pertains to the transaction manager component, involving a refinement in the gas price calculation logic. A new constant has been introduced to fine-tune the threshold value used in the calculation. Additionally, the test suite has been adjusted to align with the updated logic, changing the expected outcomes for gas price limit scenarios.

Changes

File(s) Change Summary
op-service/.../txmgr.go Modified calcThresholdValue function to incorporate a new constant ninetyNine and updated the logic for adding 1 wei.
op-service/.../txmgr_test.go Updated TestIncreaseGasPriceLimits to reflect new expected tip and fee caps following the changes in gas price limit calculations.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ?


Tips

Chat with CodeRabbit Bot (@coderabbitai)

  • You can directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
  • You can tag CodeRabbit on specific lines of code or entire files in the PR by tagging @coderabbitai in a comment. Examples:
  • You can tag @coderabbitai in a PR comment and ask questions about the PR and the codebase. Use quoted replies to pass the context for follow-up questions. Examples:
    • @coderabbitai render interesting statistics about this repository as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai generate unit tests for the src/utils.ts file.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@mdehoog mdehoog changed the title Ensure that fee is increased by at least 10% [txmgr] Ensure that fee is increased by at least 10% Dec 22, 2023
Copy link
Member

@sebastianst sebastianst left a comment

Choose a reason for hiding this comment

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

Thanks, that's indeed the proper way to do it!

@sebastianst sebastianst added this pull request to the merge queue Dec 22, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 22, 2023
@sebastianst sebastianst added this pull request to the merge queue Dec 22, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Dec 22, 2023
@sebastianst sebastianst added this pull request to the merge queue Dec 22, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 22, 2023
@sebastianst sebastianst added this pull request to the merge queue Dec 22, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 22, 2023
@sebastianst sebastianst added this pull request to the merge queue Dec 22, 2023
Merged via the queue into ethereum-optimism:develop with commit edec19f Dec 22, 2023
64 checks passed
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.

None yet

2 participants