For non-conflicting scenario like peace there are no errors.
For conflicting scenarios like guava we see that some portion of blocks is not posted due to error but that is expected behavior.
e.g 1532/11356 rejected block for guava
2024-04-23T18:16:20+02:00 INFO EvilTools.Spammer Blocks issued so far: 11356, faucet outputs left: 5361, errors encountered: 1532
Issue: Deeper scenarios were not working properly, e.g. guava was eating up 5 fresh faucet outputs but shuld use only 1 and reuse 4 other created in the same batch.
After fixing this bug (tempID was calculated on the older output struct, outputID was set after tx was built) the deeper spams were no longer working.
Node returns:
2024-04-23T16:09:57+02:00 ERROR EvilTools.accounts failed to post block: internal server error: url
http://localhost:8050/api/core/v3/blocks, error message: Internal Server Error, error: code=500, message=Internal
Server Error: failed to attach block: error issuing model block: context deadline exceeded whilst waiting for ev
ent on block BlockID(0x6adec2e818a2693c140361a78cc5f0c830b24f044e5b23239072f1e01c69b21015000000:21)
this message is unclear, but the problem is that blocks were dropped because we tried to spend not yet accepted outputs.
Now we added, await for acceptance of the transaction after each batch is sent, this leads to many more go rutines spammed and awating but has solved the problem.
peacethere are no errors.guavawe see that some portion of blocks is not posted due to error but that is expected behavior. e.g 1532/11356 rejected block for guavaIssue: Deeper scenarios were not working properly, e.g. guava was eating up 5 fresh faucet outputs but shuld use only 1 and reuse 4 other created in the same batch.
After fixing this bug (tempID was calculated on the older output struct, outputID was set after tx was built) the deeper spams were no longer working. Node returns:
this message is unclear, but the problem is that blocks were dropped because we tried to spend not yet accepted outputs. Now we added, await for acceptance of the transaction after each batch is sent, this leads to many more go rutines spammed and awating but has solved the problem.