execution-spec-tests
execution-spec-tests copied to clipboard
ethereum
A Python framework and collection of test cases to generate test vectors for Ethereum execution clients
## Description Port over all tests from `ethereum/tests` to EEST. This can be achieved in 3 ways: 1) Manually port multiple test cases taking advantage of pytest parameterization. 2) Write...
We currently have `CREATE2` -> `SELFDESTRUCT` in `tests/cancun/eip6780_selfdestruct/test_selfdestruct.py::test_create_selfdestruct_same_tx`, and the self-destructing contract is called several times to do a self-destruct, but we don't have a test that attempts to do...
I think we should ensure that the withdrawal indices here are monotonically increasing, or the test may not be valid (we define two withdrawals with `index=0`): https://github.com/ethereum/execution-spec-tests/blob/51d30bdd4e77199e7bddb70857fe8f5cc5475d63/tests/shanghai/eip4895_withdrawals/test_withdrawals.py#L611-L623 According to geth's...
https://github.com/ethereum/execution-spec-tests/blob/51d30bdd4e77199e7bddb70857fe8f5cc5475d63/tests/cancun/eip4844_blobs/test_blob_txs.py#L767 This is a less-than-ideal workaround to verify that a block is rejected when a transaction type-3 with an empty `to` field. Basically we trick t8n into executing the transaction...
For example, see https://github.com/jochem-brouwer/execution-spec-tests/blob/dccaec30b31625c9eb4e6395d6caa854307204cd/tests/byzantium/precompiles/test_05_modexp.py which calls `state_test` in a for loop in a test function. While every `state_test()` execution, respectively, test vector in `data`, will get filled, only the last...
Create a python tool in this repository that is capable of creating a blockchain test from an invalid block on any devnet, testnet or shadowfork. The tool must perform the...
https://github.com/ethereum/evmone/pull/743 added state test fixture generation from evmone's unit tests. We could consider generating these state test fixtures as part of our fixture release CI flow to make them available...
Tracker for issues that clients have found when syncing the main chain and were not caught by tests: EELS: https://github.com/ethereum/execution-specs/issues/374
``` E ethereum_test_tools.common.types.Storage.KeyValueMismatch: incorrect value in address 0x095e7baea6a6c7c4c2dfeb977efac326af552d87 for key 0x00: want 0x0400000000000000000000000000000000000000000000000000000000000000 (dec:1809251394333065553493296640760748560207343510400633813116524750123642650624), got 0x0300000000000000000000000000000000000000000000000000000000000000 (dec:1356938545749799165119972480570561420155507632800475359837393562592731987968) ``` this is printed in one line. need to print it nicely like...
## Verkle Info Page - https://verkle.info/ ## Execution Layer EIPs for inclusion - [**EIP-6800:**](https://eips.ethereum.org/EIPS/eip-6800) Ethereum state using a unified Verkle tree, - Introduces a new Verkle state tree alongside the...