-
Notifications
You must be signed in to change notification settings - Fork 820
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
Transaction pool only reduces single transaction per block even though lots of transaction in pool #7240
Comments
Hi there - are you sending all of the transactions from the same account? and with the same nonce? are you incrementing the nonce? I am not sure how you are sending these txs, probably web3j. There may be documentation on how to increment the nonce on that side. If there is a nonce gap as well, that could cause issues. Transactions with the same sender and same nonce will not be included and are considered invalid. Nonces cannot be re-used. Let me know if this was helpful or if there is more of a bug here that we can try to reproduce. |
Thanks for response. I sent transactions from various users to itself so nonce didnt affect any problems. But I found a different issue, caused by 'gas limit'. But when I set same gas limit inside go-ethereum while building transaction, It always send single transaction even though there is enough usable gas. tx := types.NewTx(&types.LegacyTx{
...
Gas: uint64(9007199254740990)
} But when client calculates gas limit real-time and allocate it to transaction (using ethclient.EstimateGas), lots of transactions can be sent in single block. Here is my assumptions.
Is there someone can help me? |
Please report the Besu configuration overview that is printed at the beginning just after you start it, because I am not sure which txpool implementation you are using |
I have the same issue as @wnjoon. I used --tx-pool="sequence". Here my genesis file
here is config.toml file:
The besu version i used is 24.5.4 |
Scenario
here is my configurations
genesis.json
run script
application is configured using free-gas-network written in official docs.
I guess since all transactions are added to txpool simultaneously and it means sending is not a problem. and nework setting is might be problem.
thanks.
The text was updated successfully, but these errors were encountered: