Str-998: Implement different transaction types for the load testing.

[evgenyzdanovich]

Description

• Implement different transaction types for the load testing.
  • transfers
  • smart contracts (Counter, ERC20, basic Uniswap)
  • all transactions support legacy transaction format, EIP2930 (access-list txs) and EIP1559 (London fork txs)
• Structured logging for each load job.
  • special logging for transactions so it's clear what is the meaning for every transaction.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature/Enhancement (non-breaking change which adds functionality or enhances an existing one)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor
• New or updated tests
• Dependency Update

Notes to Reviewers

Apologies for the big change, I tried my best to make it as structured and polished as possible.

Checklist

• I have performed a self-review of my code.
• I have commented my code where necessary.
• I have updated the documentation if needed.
• My changes do not introduce new warnings.
• I have added tests that prove my changes are effective or that my feature works.
• New and existing tests pass with my changes.

Related Issues

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.66%. Comparing base (004be7c) to head (812e814).
Report is 3 commits behind head on main.

@@            Coverage Diff             @@
##             main     #658      +/-   ##
==========================================
- Coverage   54.68%   54.66%   -0.02%     
==========================================
  Files         317      317              
  Lines       33929    33939      +10     
==========================================
- Hits        18553    18552       -1     
- Misses      15376    15387      +11     

see 5 files with indirect coverage changes

[github-actions]

Commit: 0fb4c7e

SP1 Performance Test Results

program	cycles	success
BTC_BLOCKSPACE	30,370,596	✅
EL_BLOCK	97,975	✅
CL_BLOCK	89,783	✅
L1_BATCH	30,419,814	✅
L2_BATCH	3,566	✅
CHECKPOINT	25,699	✅

[delbonis]

Comment, not sure if correct:

If we have these solidity contracts in the repo now does that mean that the load testing run requires having a solidity compiler in ci and running it? If so, would it instead be faster to have compiled initcode checked in and deploy from that instead?

[evgenyzdanovich]

@delbonis the load test is disabled for now in the CI.

your suggestion makes sense, I think that's a way to go if/when we enable it for the CI

[storopoli]

ACK 812e814