op-acceptance-tests: interop: use different EOAs in load test #16044
Labels
A-acceptance-tests
C-load-testing
go
Pull requests that update Go code
H-interop
Hardfork: change planned for interop upgrade
Uh oh!
There was an error while loading. Please reload this page.
The load test in #16032 uses the same EOAs to spam transactions. This could hit existing mempool DoS protections since op-geth op-geth limits the number of concurrent pending txs per account.
For the interop load test, we want to the interop implementation to be the limiting factor.
To resolve this, we should spam transactions from different EOAs, maybe even using a fresh EOA each time for simplicity.
The text was updated successfully, but these errors were encountered: