You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the payload, was able to reproduce the error by sending the raw bytes to our RPC.
I took the payload and put it in a JSON locally to try to make a unit test. I just made the following two changes in the pool validate for my test (because these two assertions are not at all related to the error):
I temporarily removed the test chain ID (when entering the mempool) because the chain ID provided by the payload (production chain ID) is not the one used in the tests so there is a mismatch
The user balance check because of course locally this address has no funds so it would have been necessary to fund it and I would have spent more time investigating for nothing because it was just a question of validating the eth_sendRawTransaction endpoint not the complete execution of the transaction.
So my best guess is that this issue is ultimately completely related to #1478 and because we don't prune the pool, the transactions remain and for some reason this produces a conflict leading to the mentioned error. cc @greged93@eugypalu@ClementWalter
Bug Report
Current behavior:
When sending a transaction using
eth_sendRawTransaction
, some partners have received the following error message:We would expect the transaction to pass since
7000000
<10636872
.Other information
The following document contain the parameters sent to the
eth_sendRawTransaction
endpoint: kakarot-error.txt.Tasks
Duration: 4 hours
The text was updated successfully, but these errors were encountered: