-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Transactions stuck in mempool since days/months/years #2699
Comments
this is due to its high GasLimit, currently max GasLimit on BSC mainnet is 120000000, it has been addressed by PR #2680, will be included in next release.
these transaction will be discarded in the future, as they will never be accepted by validator. |
ok cool! please wait to close this. I want to add logs to make sure that those txs have really a high gas limit. As far as i remember when i checked into them, some of them were ok. Give me ~20 minutes |
|
once the first transaction from the account triggered this issue, its following transaction will be pending as well, even they has smaller GasLimit, take addr: 0x8c6Db404C9f25134103075030e8b776be1F6E868 for example
this transaction is from 0x8c6Db404C9f25134103075030e8b776be1F6E868, with nonce 1165 |
ok cool and make sense. Thanks for explaination and sorry for your time loss on this <3 |
Hi 👋
I'm sure other mev bot / block builder developers noticed this as well.
There are transactions flying around since a lot of time (even years) which are never being mined.
I'm genuinely curious to understand what is the problem with such transactions as it is impacting building performances (simulated over and over and attempts to commit in current states).
My current workaround is discarding transactions that I received > 30s, as I see no reason for transactions to not being mined in 6 seconds (2 blocks). When i went deeper into it, im sure some of those were meeting nonce/gas limit constraints (otherwise why is my mempool promoting them?).
Adding code to also purge them from my mempool is not enough as they would get broadcasted again by other peers.
cc @Jolly23
here are some examples:
https://bscscan.com/tx/0x47bce3e6ab37c0a8078d66da2a2e8fd6094bc458383775b717594bd741a39da3
https://bscscan.com/tx/0x8becb5f51553402b7fde3826a03905a78d79dcdfc20c9eb905f3588930f70079
https://bscscan.com/tx/0x786766fe215cfcfa2559af0aadd669401357f05910ce736ba9a42f5a4c7561f4
https://bscscan.com/tx/0x8015827a969e42b6db1504bc1a0e97f68e84b6139d1206b1b1a7f105cfa836f8
https://bscscan.com/tx/0x93f5063951780295d225d6526dfab8757bc36d07ff3c2e022c72c4a25babb2a1
https://bscscan.com/tx/0x3d3c377d7c692150f93f195d90683f7df02b199deba323613a7c97613fc8f698
but there are many more.
The text was updated successfully, but these errors were encountered: