network: Add status method to ReceiptResponse trait

crates/network/src/any/mod.rs

@@ -81,6 +81,10 @@ impl ReceiptResponse for AnyTransactionReceipt {
     fn contract_address(&self) -> Option<alloy_primitives::Address> {
         self.contract_address
     }
+
+    fn status(&self) -> bool {
+        self.inner.inner.status()
+    }
 }
 
 impl TransactionResponse for WithOtherFields<Transaction> {

crates/network/src/ethereum/mod.rs

@@ -35,6 +35,10 @@ impl ReceiptResponse for alloy_rpc_types_eth::TransactionReceipt {
     fn contract_address(&self) -> Option<alloy_primitives::Address> {
         self.contract_address
     }
+
+    fn status(&self) -> bool {
+        self.inner.status()
+    }
 }
 
 impl TransactionResponse for alloy_rpc_types_eth::Transaction {

crates/network/src/lib.rs

@@ -34,6 +34,21 @@ pub use alloy_eips::eip2718;
 pub trait ReceiptResponse {
     /// Address of the created contract, or `None` if the transaction was not a deployment.
     fn contract_address(&self) -> Option<Address>;
+
+    /// Status of the transaction.
+    ///
+    /// ## Note
+    ///
+    /// Caution must be taken when using this method for deep-historical
+    /// receipts, as it may not accurately reflect the status of the
+    /// transaction. The transaction status is not knowable from the receipt
+    /// for transactions before [EIP-658].
+    ///
+    /// This can be handled using [`TxReceipt::status_or_post_state`].
+    ///
+    /// [EIP-658]: https://eips.ethereum.org/EIPS/eip-658
+    /// [`TxReceipt::status_or_post_state`]: alloy_consensus::TxReceipt::status_or_post_state
+    fn status(&self) -> bool;
 }
 
 /// Transaction Response