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(sender): make sure gas price is above baseFee #1531

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

0xmountaintop
Copy link
Member

@0xmountaintop 0xmountaintop commented Oct 8, 2024

Purpose or design rationale of this PR

During the sdk test, we found that suggested gas price might be insufficent if the txpool have a few txs (cc @jonastheis any clue if you look into gas oracle logic?). and our txpool will reject a legacy tx if its gas price is below basefee.

Feedback from altlayer:
After running for a while, the suggested gas price will drop to 0.01GWei, and gas oracle sender couldn't send any tx successfully.
Then they have to manually send a tx with gas price = baseFee. After that, the gas oracle sender can resume working.

While I think the real solution is to fix the gas oracle, we can quick hack it in this way to make our sdk testnet working.

PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

  • build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
  • ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
  • docs: Documentation-only changes
  • feat: A new feature
  • fix: A bug fix
  • perf: A code change that improves performance
  • refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • test: Adding missing tests or correcting existing tests

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

  • No, this PR doesn't involve a new deployment, git tag, docker image tag
  • Yes

Breaking change label

Does this PR have the breaking-change label?

  • No, this PR is not a breaking change
  • Yes

Summary by CodeRabbit

  • New Features

    • Updated version number to v4.4.73.
    • Enhanced gas price adjustment logic for legacy transaction resubmissions to ensure compliance with base fee requirements.
  • Bug Fixes

    • Improved logging for transaction gas adjustments to provide clearer insights during resubmission.

@0xmountaintop 0xmountaintop added the bump-version Bump the version tag for deployment label Oct 8, 2024
colinlyguo
colinlyguo previously approved these changes Oct 8, 2024
Copy link
Member

@colinlyguo colinlyguo left a comment

Choose a reason for hiding this comment

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

nice catch.

@@ -357,6 +366,10 @@ func (s *Sender) resubmitTransaction(tx *gethTypes.Transaction, baseFee, blobBas
originalGasPrice := tx.GasPrice()
gasPrice := new(big.Int).Mul(originalGasPrice, escalateMultipleNum)
gasPrice = new(big.Int).Div(gasPrice, escalateMultipleDen)
baseFeeInt := new(big.Int).SetUint64(baseFee)
if gasPrice.Cmp(baseFeeInt) < 0 {
gasPrice = baseFeeInt
Copy link
Member

Choose a reason for hiding this comment

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

may as well add a multiplier here? the drawback would be over-charging by the multiplier.

Copy link
Member Author

Choose a reason for hiding this comment

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

gasPrice is already multiplied. if after being multiplied it's still below baseFee we should bump it. I prefer not to multiplying again here.

Copy link
Member

Choose a reason for hiding this comment

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

if the txn is submitted, and before it's included in a block, the block's base fee is updated by gas-oracle price update, the gas price will be < base fee again. same suspicion in another comment discussion.

rollup/internal/controller/sender/sender.go Outdated Show resolved Hide resolved
georgehao
georgehao previously approved these changes Oct 8, 2024
@codecov-commenter
Copy link

codecov-commenter commented Oct 9, 2024

Codecov Report

Attention: Patch coverage is 25.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 52.92%. Comparing base (3ab5752) to head (7fd3a17).

Files with missing lines Patch % Lines
rollup/internal/controller/sender/sender.go 25.00% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1531      +/-   ##
===========================================
+ Coverage    52.78%   52.92%   +0.14%     
===========================================
  Files          157      157              
  Lines        12652    12624      -28     
===========================================
+ Hits          6678     6681       +3     
+ Misses        5392     5362      -30     
+ Partials       582      581       -1     
Flag Coverage Δ
rollup 59.03% <25.00%> (-0.04%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

colinlyguo
colinlyguo previously approved these changes Oct 9, 2024
@jonastheis
Copy link

After running for a while, the suggested gas price will drop to 0.01GWei, and gas oracle sender couldn't send any tx successfully.

The question is where does this 0.01GWei come from? Is it returned from the L2 node when querying the gas price or is it s.config.MinGasTip? See here:

func (s *Sender) estimateLegacyGas(to *common.Address, data []byte, fallbackGasLimit uint64) (*FeeData, error) {

Then they have to manually send a tx with gas price = baseFee. After that, the gas oracle sender can resume working.

I can only speculate but maybe something like this happened: the first transaction was not going through (send via SendTransaction here) for example because the L2 base fee went up (due to L1 base fee changes). So this tx (and nonce) was "stuck". Now in the resubmitTransaction we didn't account for the base fee for legacy transactions which is why it couldn't recover.

@colinlyguo
Copy link
Member

After running for a while, the suggested gas price will drop to 0.01GWei, and gas oracle sender couldn't send any tx successfully.

The question is where does this 0.01GWei come from? Is it returned from the L2 node when querying the gas price or is it s.config.MinGasTip? See here:

func (s *Sender) estimateLegacyGas(to *common.Address, data []byte, fallbackGasLimit uint64) (*FeeData, error) {

Then they have to manually send a tx with gas price = baseFee. After that, the gas oracle sender can resume working.

I can only speculate but maybe something like this happened: the first transaction was not going through (send via SendTransaction here) for example because the L2 base fee went up (due to L1 base fee changes). So this tx (and nonce) was "stuck". Now in the resubmitTransaction we didn't account for the base fee for legacy transactions which is why it couldn't recover.

agree. the probability of this speculation is higher when the network's L2 txns are mainly formed by gas oracle price update (txns updating L1 base fee and L1 blob base fee).

Thegaram
Thegaram previously approved these changes Oct 11, 2024
@colinlyguo colinlyguo dismissed stale reviews from Thegaram and themself via 7fd3a17 November 15, 2024 15:31
Copy link

coderabbitai bot commented Nov 15, 2024

Walkthrough

The changes in this pull request include an update to the version number in common/version/version.go, changing it from "v4.4.72" to "v4.4.73". Additionally, modifications were made to the resubmitTransaction method in rollup/internal/controller/sender/sender.go to adjust the gas price for legacy transactions, ensuring it meets the base fee requirement. Minor adjustments to logging statements were also included to enhance clarity regarding gas price adjustments.

Changes

File Path Change Summary
common/version/version.go Updated variable tag from "v4.4.72" to "v4.4.73"; no other changes.
rollup/internal/controller/sender/sender.go Modified resubmitTransaction method to ensure gas price meets base fee; updated logging for clarity.

Possibly related PRs

Suggested reviewers

  • 0xmountaintop
  • georgehao

🐰 In the code where I hop and play,
A version change has come my way.
Gas prices rise, adjustments made,
With clearer logs, I'm not afraid!
Hopping forward, I’ll keep it bright,
Each transaction, a joyful flight! 🌟


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 your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
rollup/internal/controller/sender/sender.go (1)

360-363: Consider optimizing for rapid base fee increases.

In scenarios where the base fee increases rapidly, the current implementation might require multiple resubmissions before a transaction is included. Consider adding a small multiplier (e.g., 1.1x) to the base fee to provide a buffer against near-term base fee increases.

 baseFeeInt := new(big.Int).SetUint64(baseFee)
+// Add 10% buffer to handle near-term base fee increases
+baseFeeInt = new(big.Int).Mul(baseFeeInt, big.NewInt(11))
+baseFeeInt = new(big.Int).Div(baseFeeInt, big.NewInt(10))
 if gasPrice.Cmp(baseFeeInt) < 0 {
     gasPrice = baseFeeInt
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3ab5752 and 7fd3a17.

📒 Files selected for processing (2)
  • common/version/version.go (1 hunks)
  • rollup/internal/controller/sender/sender.go (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • common/version/version.go
🔇 Additional comments (1)
rollup/internal/controller/sender/sender.go (1)

360-363: LGTM! Implementation correctly ensures gas price meets base fee requirement.

The added check properly ensures that resubmitted legacy transactions have a gas price at least equal to the current base fee, which directly addresses the issue where transactions were failing due to insufficient gas price.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bump-version Bump the version tag for deployment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants