ethereum / ethereum/execution-specs
bug(tests): released fixtures in tests-zkevm@v0.6.2 contain blocks without statelessInputBytes
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 505
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 116
Description
I downloaded [fixtures from tests-zkevm@v0.6.2](https://github.com/ethereum/execution-specs/releases/download/tests-zkevm%40v0.6.2/fixtures_zkevm.tar.gz). I am using `statelessInputBytes` to test my zkEVM guest.
There's a file that contains many blocks
```
% grep blockHeader blockchain_tests/for_amsterdam/cancun/eip4844_blobs/excess_blob_gas/invalid_negative_excess_blob_gas.json | wc -l
5292
```
but not so many statelessInputBytes
```
% grep statelessInputBytes blockchain_tests/for_amsterdam/cancun/eip4844_blobs/excess_blob_gas/invalid_negative_excess_blob_gas.json | wc -l
2548
```
At the moment I am not running most blocks in this file.
Should there be statelessInputBytes in every block?
Contributor guide
Research direction
Start with blockchain_tests/for_amsterdam/cancun/eip4844_blobs/excess_blob_gas/invalid_negative_excess_blob_gas.json in the tests-zkevm@v0.6.2 fixture archive and compare its blockHeader and statelessInputBytes entries. Trace how this fixture is produced or released, then establish whether every block is expected to include statelessInputBytes and verify the published archive matches that expectation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100