Skip to content

feat(op-stack): add deposit receipt fields to OpStackTransactionReceipt#4817

Merged
jxom merged 2 commits into
wevm:mainfrom
davidperk:main
Jul 8, 2026
Merged

feat(op-stack): add deposit receipt fields to OpStackTransactionReceipt#4817
jxom merged 2 commits into
wevm:mainfrom
davidperk:main

Conversation

@davidperk

Copy link
Copy Markdown
Contributor

Summary

Adds OP Stack deposit receipt support to OpStackTransactionReceipt and OpStackRpcTransactionReceipt.

  • Extends OpStackRpcTransactionReceiptOverrides with optional depositNonce and depositReceiptVersion (RPC hex quantities)
  • Extends OpStackTransactionReceiptOverrides with optional depositNonce (bigint) and depositReceiptVersion (number)
  • Formats both fields in the OP Stack transactionReceipt formatter when present on the RPC response
  • Adds formatter runtime and type tests

These fields appear on deposit transaction receipts (type: "0x7e") starting with the Regolith and Canyon hardforks, respectively.

Spec vs. implementation naming

The OP Stack deposit receipt spec documents the Canyon-era receipt extension as depositNonceVersion:

depositNonceVersion (unique extension): Optional field. The value must be 1 if the field is present
Before Canyon, these depositNonce & depositNonceVersion fields must always be omitted.
With Canyon, these depositNonce & depositNonceVersion fields must always be included.

The reference implementation and JSON-RPC wire format use depositReceiptVersion instead:

This PR follows the JSON-RPC field names (depositNonce, depositReceiptVersion) returned by OP Stack nodes, not the spec's depositNonceVersion prose label.

@changeset-bot

changeset-bot Bot commented Jul 7, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 25ec7c2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
viem Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercel Bot commented Jul 7, 2026

Copy link
Copy Markdown

@davidperk is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

@jxom jxom merged commit 2825f37 into wevm:main Jul 8, 2026
2 of 3 checks passed
@github-actions github-actions Bot mentioned this pull request Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants