# Pectra Hive Remaining Failures Mainnet Clients Please proceed to https://hive.ethpandaops.io/#/?group=pectra for latest hive runs. ## Besu & Erigon Passing all `consume engine/rlp`. Requires mapper update in the EEST version running hive, hence the 3 fails for `consume engine` in Besu (tested locally). ## Geth ### Consume Rlp Failing these 4 cases. Spec compliance tests. Okay for mainnet. - `eip7251_consolidations/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-nonzero_balance]` - `eip7251_consolidations/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-zero_balance]` - `eip7002_el_triggerable_withdrawals/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-nonzero_balance]` - `eip7002_el_triggerable_withdrawals/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-zero_balance]` ### Consume Engine The above plus the 20 of following deposits tests: - `eip6110_deposits/test_modified_contract.py::test_invalid_layout*` These tests cover the Sepolia log issue. Spec compliance. They return an incorrect exception however still produces an invalid block correctly. Okay for mainnet. ## Nethermind ### Consume Rlp Same 4 cases as geth. Spec compliance. Okay for mainnet. - `eip7251_consolidations/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-nonzero_balance]` - `eip7251_consolidations/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-zero_balance]` - `eip7002_el_triggerable_withdrawals/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-nonzero_balance]` - `eip7002_el_triggerable_withdrawals/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-zero_balance]` Modifies the system consol/withdrawal. contracts to return specifci errors. Spec compliance. Extremely unlikely to happen in mainnet, sanity check to make sure clients behave the same way in the off chance it happens or there’s a chain that does not have these contracts the same way in mainnet. Okay for mainnet. - `eip7251_consolidations/test_modified_consolidation_contract.py::test_system_contract_errors*` - `eip7251_consolidations/test_modified_consolidation_contract.py::test_extra_consolidations*` - `eip7002_el_triggerable_withdrawals/test_modified_withdrawal_contract.py::test_system_contract_errors*` - `eip7002_el_triggerable_withdrawals/test_modified_withdrawal_contract.py::test_extra_withdrawals*` ### Consume Engine 22 cases here. Cover the Sepolia log issue. Spec compliance. Return incorrect exception but returns an invalid block correctly. Okay for mainnet. - `eip6110_deposits/test_modified_contract.py::test_invalid_layout*` - `eip6110_deposits/test_modified_contract.py::test_invalid_log_length*` Questionable engine api error. Other clients return an invalid block. Probably okay for mainnet, but maybe nice to fix. ``` [INFO] pytest_plugins.consume.hive_simulators.engine.test_via_engine: JSONRPC error encountered: -39001 - Unexpected data at position 576 [FAIL] pytest_plugins.consume.hive_simulators.engine.test_via_engine: Unexpected error: -39001 - Unexpected data at position 576 ``` ## Reth ### Consume Rlp Same 4 cases as geth/nethermind. Spec compliance. Okay for mainnet. - `eip7251_consolidations/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-nonzero_balance]` - `eip7251_consolidations/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-zero_balance]` - `eip7002_el_triggerable_withdrawals/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-nonzero_balance]` - `eip7002_el_triggerable_withdrawals/test_contract_deployment.py::test_system_contract_deployment[fork_CancunToPragueAtTime15k-blockchain_test-deploy_after_fork-zero_balance]` Modifies the system consol/withdrawal. contracts to reach the gas limit 30M. Not possible in mainnet. Spec compliance test. - `eip7251_consolidations/test_modified_consolidation_contract.py::test_system_contract_errors[fork_Prague-blockchain_test_engine-system_contract_reaches_gas_limit-system_contract_0x0000bbddc7ce488642fb579f8b00f3a590007251]` - `eip7002_el_triggerable_withdrawals/test_modified_withdrawal_contract.py::test_system_contract_errors[fork_Prague-blockchain_test_engine-system_contract_reaches_gas_limit-system_contract_0x00000961ef480eb55e80d19ad83579a64c007002]` ### Consume Engine All `consume rlp` tests and the following below. Non issue. Tests the fork transition from Shanghai to Cancun. Okay for mainnet. - `eip4844_blobs/test_blob_txs.py::test_blob_type_tx_pre_fork[fork_ShanghaiToCancunAtTime15k-blockchain_test_engine_from_state_test-one_blob_tx]` 12 cases here. Cover the Sepolia log issue. Spec compliance. Return incorrect exception but returns an invalid block correctly. Okay for mainnet. - `eip6110_deposits/test_modified_contract.py::test_invalid_layout*` - `eip6110_deposits/test_modified_contract.py::test_invalid_log_length*` ## Ethjs Needs to see what's happening on ethjs side for the failures. ## Nimbus-EL Passing all `consume rlp`. `consume engine` fails need more work on the EEST mapper side, as expected exceptions are not what we expect. WIP currently.
Last changed by  
 
spencer
90

Read more

EEST CI Components to Port to EELS

GitHub Actions Workflows .github/workflows/ tox_verify.yaml → Rename to eest_tests.yamlMain EEST testing pipeline Jobs: lint, typecheck, spellcheck, changelog, markdownlint, mkdocs, pytest_framework, tests_deployed, tests_deployed_benchmark Add path filters for EEST codeUpdate branch: main → master coverage.yaml → evmone_coverage.yaml Evmone coverage tracking for test changes Triggers on changes to tests/eest

10/10/2025
PeerDAS Testing in EEST

Note this ignores engine-osaka test cases. We should try get this up to date before the fork. EEST Test Updates tests/cancun/eip4844.../ already contains a bunch of blob tx tests. These need be updated to use actual kzg proofs? In addition to these tests, we should create a tests/osaka/eip7594.../ path that can contain negative blob tx tests, and any more interesting positive blob txs that are not covered in tests/cancun/eip4844.../. Some negative examples: Basic RLP corruption txs.

5/13/2025
Untitled

TransactionException.INSUFFICIENT_MAX_FEE_PER_GAS We would expect something like the following: max fee per gas less than block base fee tests/prague/eip7702_set_code_tx/test_set_code_txs.py::test_set_code_transaction_fee_validations[fork_Prague-blockchain_test_engine_from_state_test-insufficient_max_fee_per_gas] tests/cancun/eip4844_blobs/test_blob_txs.py::test_invalid_normal_gas[fork_Prague-blockchain_test_engine_from_state_test-insufficient_max_fee_per_gas] TransactionException.TYPE_3_TX_MAX_BLOB_GAS_ALLOWANCE_EXCEEDED We would expect something like the following: Invalid Blob Count tests/cancun/eip4844_blobs/test_blob_txs.py::test_invalid_tx_blob_count[fork_Prague-too_many_blobs-blockchain_test_engine_from_state_test]

5/2/2025
BLS DUMP

Just to preface, I'm viewing the map-to-curve as the following process: First a field point t is passed into a SWU (simplified Shallue van de Woestijne Ulas) which I'm viewing as a "magic machine", taking t as an input and outputting a point P' on an auxiliary curve E'. Then this point P' is fed into the isogeny "machine" to give us a point P on the BLS curve E. My definition of the isogeny kernel: The set of "special" points that when input into the isogeny polynomials gives us "nothing" -> the identity point at infinity. I'm viewing these as traps during the map-to-curve process. An n degree isogeny contains n kernel points, those that map to infinity.

4/22/2025
Read more from spencer
Published on HackMD