rewrite of sei-load generator and sender.

[pompon0]

Primary reason for the rewrite is support for non-happy paths for autobahn loadtesting - rejected transactions/not successfully executed/etc. The idea is that if sending a tx fails, we need to check the account nonce before sending the next transaction. Note that this affects only accounts from the long-lived pools - accounts generated for the sake of sending just 1 transaction (aka "new accounts") do not benefit from this extra logic.

The nonces, as well as the txs waiting to be sent are managed by TxsQueue, which ensures that:

• inserted (generated) transactions have expected nonces
• transactions per account are sent sequentially (otherwise they will be rejected by autobahn)

TxsQueue is managed by ShardedSender.

Additionally

• removed unnecessary abstractions in both sender and generator logic
• made Generator.Run accept the sender which exposes Nonce(), Flush() and Send() calls
• added Generator <-> Sender integration tests
• removed open/closed loop logic (might need to be reintroduced later if needed)
• removed utils/rng in favor of just using a single Rand synchronously (we don't have other use cases). If concurrent Rand usage is needed, a SplitRng method was introduced (slower but robust alternative to SplitMix).

[cursor]

Buffer size no longer bounds queue

Medium Severity

NewShardedSender sizes TxsQueue only from Settings.MaxInFlight. Settings.BufferSize and LoadConfig.TotalQueueSize() are no longer used, so existing configs that tune bufferSize/--buffer-size do not limit queue depth or memory as before.

 

^{Reviewed by Cursor Bugbot for commit 34ba3fe. Configure here.}

[cursor]

Deploy nonces skip unused slots

High Severity

Sequential scenario deployment passes the scenario list index as the deployer nonce. Instances that do not broadcast a deployment transaction still advance that index, so the next contract deployment can be signed with a nonce above the account’s on-chain nonce and be rejected.

 

^{Reviewed by Cursor Bugbot for commit cce23ae. Configure here.}

[cursor]

TxsWriter emits unsigned payloads

High Severity

Transaction signing moved into ShardedSender, so generators now hand off unsigned txs. The TxsDir path uses TxsWriter, which marshals EthTx directly without signing. Written tx_payloads are therefore not valid raw transactions for later submission.

Additional Locations (2)

• generator/scenarios/EVMTransfer.go#L47-L83
• main.go#L281-L295

 

^{Reviewed by Cursor Bugbot for commit 10fe1d9. Configure here.}

[cursor]

Funding skipped for txs-dir path

Medium Severity

Account funding now runs only in the ShardedSender branch. When TxsDir is set, FundAccounts is never called even if cfg.Funding is configured, so written txs can target unfunded accounts when replayed.

 

^{Reviewed by Cursor Bugbot for commit 59dd2f4. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 7 total unresolved issues (including 6 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7aa4303. Configure here.}

[cursor]

Unused EthClient interface left behind

Low Severity

The new exported-looking EthClient interface in generator is never referenced. Dead API surface next to the real TxSender interface makes the generator↔sender contract harder to follow.

 

^{Reviewed by Cursor Bugbot for commit 7aa4303. Configure here.}