lambdaclass / lambdaclass/lambda_ethereum_consensus
The tx_spammer migration to the tx_fuzz works different on the amount of transactions sent.
Open
Nobody has claimed this yet.
bug
deneb
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
After upgrading to the latest version of the ethereum-package the previously working tx_spammer that generate 3 account x 80 txs (240 in total) is now generating less than 100. This might be because a change in how the params work, but probably an issue in how we parse transactions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the tx_spammer migration to tx_fuzz, focusing first on how the parameters are interpreted and how transactions are parsed. Reproduce the case with 3 accounts sending 80 transactions each, then verify that the result is 240 transactions rather than fewer than 100.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100