L1: TX Spammer gets more transactions included when it hits another node's RPC

[rodrigo-o]

With the same setup, if the first node is not our own there are more transactions included on the second phase of every spam. For detailed info read the first comment

[rodrigo-o]

Spammer execution
As part of the spammer configuration we have two important parameters --accounts(a) and --txcount(b), accounts are the amount of accounts affected by transactions, and txcount the amount of transactions send per any account. The spammer works in a 2 step process, first it send 1 tx for every account, which ends up in the first block a a number of transactions. If those succeed it send txcount transactions for each account, ie a x b number of transactions in a subsequent block.

Right now we are not sharing tx through p2p so we are the only ones receiving them, otoh if we are not the first client in the kurtosis yaml, that one receives them and given we are not processing them yes just the other clients get access to those. This shows the first difference between our current state and for example geth.

Diff 1: Amount of Transactions
Given the previous explanation if we configure the spammer with --txcount=2 --accounts=100, we'll see an initial block with 100 tx, a follow up one with 200 tx, and a repeat ad infinitum. Geth displays this behaviour, but in our case we have an initial one of 100 and the second one between 100~140. I'll create a new issu to track this, we are rejecting or ignoring some of those transactions. What i was able to validate is that they are not filtered out, at least as far as I could check, so they were rejected prior to being added to the mempool.