test_tx_invalid_first_in_block()¶
Documentation for tests/frontier/validation/test_transaction.py::test_tx_invalid_first_in_block@ffe48572.
Generate fixtures for these test cases for Bogota with:
The first transaction of a block is invalid and the valid one after it would have made it valid had it run first; the block is rejected at the first transaction.
This guards clients that execute a block's transactions in parallel, as
block access lists (EIP-7928) allow: they must reject the block without
help from the transactions after the invalid one, which a sequential
client never looks at. insufficient_funds: the later transaction funds
the unfunded sender. nonce_too_high: the sender's nonce 1 arrives
before its nonce 0. The later transaction also puts the sender in the
block access list, which a client reading state through the list needs
before it reaches the check under test. The next block replays it at the
same nonce, so it must have left no trace.
Source code in tests/frontier/validation/test_transaction.py
398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 | |
Parametrized Test Cases¶
This test generates 2 parametrized test cases across 17 forks.