test_blobhash_invalid_blob_index()¶
Documentation for tests/cancun/eip4844_blobs/test_blobhash_opcode.py::test_blobhash_invalid_blob_index@verkle@v0.0.6.
Generate fixtures for these test cases for Cancun with:
Cancun only:
fill -v tests/cancun/eip4844_blobs/test_blobhash_opcode.py::test_blobhash_invalid_blob_index --fork=Cancun --evm-bin=/path/to/evm-tool-dev-version
For all forks up to and including Cancun:
fill -v tests/cancun/eip4844_blobs/test_blobhash_opcode.py::test_blobhash_invalid_blob_index --until=Cancun
Tests that the BLOBHASH opcode returns a zeroed bytes32 value for invalid
indexes.
Includes cases where the index is negative (index < 0) or
exceeds the maximum number of blob_versioned_hash values stored:
(index >= len(tx.message.blob_versioned_hashes)).
It confirms that the returned value is a zeroed bytes32 for each case.
Source code in tests/cancun/eip4844_blobs/test_blobhash_opcode.py
168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 | |
Parametrized Test Cases¶
The interactive table below is also available as a standalone page.
Skipped Parameters
For more concise readability, the table below does not list the following parameter values:
fork, blockchain_test, state_test, state_test_only, eof_test, eof_state_test.
| Test ID | scenario |
|---|---|
| scenario_invalid_calls | invalid_calls |