chore: rm execution requests from v4 payload fn (#401)

closes #395
alloy-rs · Jan 25, 2025 · 5b28b7b · 5b28b7b
1 parent f38e1cc
commit 5b28b7b
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/crates/provider/src/ext/engine.rs b/crates/provider/src/ext/engine.rs
@@ -54,7 +54,6 @@ pub trait OpEngineApi<N, T> {
         &self,
         payload: ExecutionPayloadV3,
         parent_beacon_block_root: B256,
-        execution_requests: Vec<Bytes>,
     ) -> TransportResult<PayloadStatus>;
 
     /// Updates the execution layer client with the given fork choice, as specified for the Shanghai
@@ -211,10 +210,11 @@ where
         &self,
         payload: ExecutionPayloadV3,
         parent_beacon_block_root: B256,
-        execution_requests: Vec<Bytes>,
     ) -> TransportResult<PayloadStatus> {
-        // Note: The `versioned_hashes` parameter is always an empty array for OP chains.
+        // Note: The `versioned_hashes`, `execution_requests` parameters are always an empty array
+        // for OP chains.
         let versioned_hashes: Vec<B256> = vec![];
+        let execution_requests: Vec<Bytes> = vec![];
 
         self.client()
             .request(