how to deal with hundreds of transactions are going into pending

Question

I am trying to create a simple bot for sending transactions. what it does is that it sends multiple in successions with the same data but different nonce and a bit more gasPrice each time. In theory that's what you need to change in order for your transaction to be seen as completely new.

But my issue is that all transactions would stay pending forever on the nodes (i knew this by running a light client and using it as a provider). I would like to know why is this happening ? do I need to change the data on each transaction?

I tried changing the gas price up to 100Gwei in order to see if that would work but to no use.

is there something that i ma doing wrong ?

Answer 1

I looked a bit more into the tx processing in go ethereum.

First, a node holding a tx pool will replace an existing pending tx by another one if :

1. Nonce is the same
2. gasPrice is higher by at least 10% higher.

Implementation is here. So with your approach of changing nonce but higher gas price you are just flooding the tx pools.

Second thing that might directly explain your problem: if a tx with nonce n is pending, no transaction with nonce > n can proceed before (assuming the same sender, of course).

I am trying to create a simple bot for sending transactions. what it does is that it sends multiple in successions with the same data but different nonce and a bit more gasPrice each time.

So if your first transaction is pending because of too low gasPrice, no other transaction with higher nonce will proceed until you explicitly cancel / replace it. Same goes for second, third, etc...