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

[provider] Determine if eth_feeHistory is a reliable way to get pending base fee across chains #821

Closed
6 of 7 tasks
dancoombs opened this issue Oct 2, 2024 · 3 comments
Closed
6 of 7 tasks
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@dancoombs
Copy link
Collaborator

dancoombs commented Oct 2, 2024

Describe the feature
If not, find a different way to get pending base fee for those chains.

Chains to check:

  • Ethereum
  • OP Stack chains
  • Arbitrum Orbit/Nitro chains
  • Avalance
  • Flow
  • Berachain
  • Polygon
@dancoombs dancoombs added enhancement New feature or request needs-triage Issue needs triage and removed needs-triage Issue needs triage labels Oct 2, 2024
@dancoombs dancoombs self-assigned this Oct 2, 2024
@dancoombs dancoombs added this to the v0.4 milestone Oct 2, 2024
@dancoombs
Copy link
Collaborator Author

dancoombs commented Oct 3, 2024

Doesn't support:

  • Cleo mainnet: but will once upgrade to L2
  • Avalanche: doesn't return the next block's base fee, but supports eth_baseFee
  • Polygon zkEVM (but doesn't support eip-1559 at all)
  • Flow: always returns zeros, doesn't return next block (but base fee constant - zero)

@dancoombs
Copy link
Collaborator Author

Note: Alloy's FeeHistory::latest_block_base_fee won't work on avalanche (we don't use it)

@dancoombs
Copy link
Collaborator Author

Not going to fix this now, here is the follow up ticket: #825

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant