TransactionReceipt status type should be nullable

[nicklatkovich]

Check existing issues

• I checked there isn't already an issue for the bug I encountered.

Viem Version

2.33.2

Current Behavior

TransactionReceipt['status'] is 'success' | 'reverted'

Expected Behavior

TransactionReceipt['status'] is 'success' | 'reverted' | null

Steps To Reproduce

  const client = createPublicClient({ transport: http(CONFIG.WEB3_PROVIDER) });
  const hash: Hash = "0x592ae92598bffc4e142d0b68b720788451d320d6e34da06fd765c488e7330027";
  const receipt = await client.getTransactionReceipt({ hash });
  // TS with strict:true doesn't fail here, but it should, since `receipt.status` is null
  const status: string = receipt.status;

Link to Minimal Reproducible Example

No response

Anything else?

No response

[jxom]

Receipts must have a 0x1 (success) or 0x0 (failure). How is null coming through?

[nicklatkovich]

The status field in receipts was introduced in the Byzantium hard fork. Receiving older receipts will result in receipt.status being null. See the original message for a real example (Ethereum mainnet).

[nicklatkovich]

Looks like eth.merkle.io (the default RPC in Viem) returns status as expected. However, the issue can be reproduced using Geth, so it should not be ignored, in my opinion. Infura also returns null for such transactions.