Make the tx_spammer additional service start working with our client
Closed this issue · 0 comments
rodrigo-o commented
After solving #847 we were able to be the first node in the network_params.yaml file, and so, being the target of the transaction spammer. The node was working as part of the kurtosis devnet and assertoor test went through but the tx spammer immediately stops with:
No seed provided, creating one
Internal Error: Could not resolve block number
sending at f93ee4cf8c6c40b329b0c0626f28333c132cf241
error getting pending nonce; could not airdrop: Internal Error: Could not resolve block number
The objective of this issue is having the tx spammer running, not solving every issue that appears on the runs, if we are able to get an initial transaction going through, then we can start creating new issues for specific errors encountered by the fuzzer.