-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Erigon3 "fee cap less than block base fee" RPC errors #12247
Comments
TL;DR:
eth_getTransactionReceipt:
|
AskAlexSharov
added a commit
that referenced
this issue
Oct 25, 2024
… in `backend.go` (#12413) I found that external RPCDaemon using custom logic/methods to open `engine` db and create `engine` object. Need re-use logic (and don't loose `.Accede()` when opening databases from external rpcdaemon) on Gnosis: next request doesn't work if `optimize=false` and works if `optimize=true`: ``` curl -X POST http://localhost:8549 -H 'Content-Type: application/json' -d '{"jsonrpc": "2.0", "method": "eth_getTransactionReceipt", "params": ["0x7fb21774eed37fa229d59cdf4b991f951aee185066d86b432ed1cc1e29764577"], "id": 293}' ``` for: #12247 error message is: ``` WARN[10-22|08:12:17.321] [rpc] served conn=127.0.0.1:35698 method=eth_getTransactionReceipt reqid=293 err="getReceipt error: ReceiptGen.GetReceipt: bn=19040024, txnIdx=0, fee cap less than block base fee: address 0x67342Ec1440bFB760Ba9805a7735e0D12Bb9fEc7, gasFeeCap: 0 baseFee: 141015840" ```
fixed by #12640 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Erigon version: erigon version 3.00.0-alpha4-4d3b9054
OS & Version: Ubuntu 2204
Commit hash: 4d3b905
Erigon Command (with flags/config):
Consensus Layer: internal CL
Consensus Layer Command (with flags/config): N/A
Chain/Network: gnosis
Expected behaviour
While indexing certain subgraphs, the RPC returns an error, which doesn't happen on Erigon V2.
Actual behaviour
Erigon logs:
Subgraph logs:
Steps to reproduce the behaviour
I have extracted the following requests to the RPC that the graph-node sends, which may help identify the error
The very last request is what produces the actual errors on Erigon's side:
Backtrace
The text was updated successfully, but these errors were encountered: