From e0ba04d19846221dfd962de9704de56845785e7b Mon Sep 17 00:00:00 2001
From: Michael Sproul <michael@sigmaprime.io>
Date: Tue, 12 May 2026 12:09:01 +1000
Subject: [PATCH] Put back irrelevant status with caveat comment

---
 testing/ef_tests/src/cases/fork_choice.rs | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/testing/ef_tests/src/cases/fork_choice.rs b/testing/ef_tests/src/cases/fork_choice.rs
index 34d25d2e36..1113cbe72f 100644
--- a/testing/ef_tests/src/cases/fork_choice.rs
+++ b/testing/ef_tests/src/cases/fork_choice.rs
@@ -854,6 +854,9 @@ impl<E: EthSpec> Tester<E> {
                 .seconds_from_current_slot_start()
                 .unwrap();
 
+            // FIXME(sproul): this whole concept is a bit ill-conceived, the blocks just get
+            // rejected here due to passing payload status irrelevant, which is not a real codepath
+            // that should be reached
             let result = self
                 .harness
                 .chain
@@ -865,7 +868,7 @@ impl<E: EthSpec> Tester<E> {
                     block_root,
                     block_delay,
                     &state,
-                    PayloadVerificationStatus::Optimistic,
+                    PayloadVerificationStatus::Irrelevant,
                     block.message().proposer_index(),
                     &self.harness.chain.spec,
                 );