-
Notifications
You must be signed in to change notification settings - Fork 42
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
"maxFeePerGas" may be lower than maxPriorityFeePerGas #1994
Comments
Needs patch to activate, decided to postpone and include into 3.1 |
olehnikolaiev
added a commit
that referenced
this issue
Jan 8, 2025
olehnikolaiev
added a commit
that referenced
this issue
Jan 8, 2025
olehnikolaiev
added a commit
that referenced
this issue
Jan 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Skale uses maxFeePerGas as a gasPrice for type0,1 transactions.
maxPriorityFeePerGas doesn't use anywhere within the skaled functionality
But, eip 1559 provides the formula
maxFeePerGas = baseFeePerGas + maxPriorityFeePerGas
Where maxFeePerGas cannot be lower than maxPriorityFeePerGas.
Versions
skalenetwork/schain:3.19.2-beta.0
Preconditions
Active schain medium type
To Reproduce
Expected behavior
Skaled should return the error
Actual state
Skaled sends the transaction and receives the transaction by hash without any errors.
Log
The text was updated successfully, but these errors were encountered: