Skip to content

Conversation

@m4sterbunny
Copy link
Contributor

@m4sterbunny m4sterbunny commented Nov 14, 2025

Description

Simplified page with methods table showing diagnostic options per method
Added note about generic trace handling (dynamic field support)
Documented creationMethod field (create or create2)
Updated trace_filter description: 100 block limit per query on mainnet/Sepolia
Minor proofing round of current key:value table to better align with response object
Minor proof subtraces (tag along fix)

Issue(s) fixed

Fixes #2473

Preview

Checklist

  • If this PR updates or adds documentation content that changes or adds technical meaning, it has received an approval from an engineer or DevRel from the relevant team.
  • If this PR updates or adds documentation content, it has received an approval from a technical writer.

External contributor checklist

  • I've read the contribution guidelines.
  • I've created a new issue (or assigned myself to an existing issue) describing what this PR addresses.

Note

Refactors trace docs with a methods-to-diagnostics table, documents additional trace fields, adds a caution on generic responses, clarifies trace_filter’s 100-block range limit, and normalizes subtraces casing.

  • Docs: Ethereum trace methods
    • Add methods table mapping to diagnostic options in services/reference/ethereum/json-rpc-methods/trace-methods/index.md.
    • Add caution on generic trace responses requiring graceful handling.
    • Expand trace schema: document creationMethod, broaden callType, add init, code, clarify subtraces, and refine transactionPosition text.
    • Minor cleanup of stateDiff symbol descriptions.
  • Docs: trace_filter
    • Update _trace_filter-description.mdx to state a 100-block range limit per query.
  • Docs: Linea trace methods
    • Normalize key name to subtraces in services/reference/linea/.../trace-methods/index.md.

Written by Cursor Bugbot for commit 1e6c032. This will update automatically on new commits. Configure here.

@m4sterbunny m4sterbunny requested review from a team as code owners November 14, 2025 13:48
@vercel
Copy link

vercel bot commented Nov 14, 2025

@m4sterbunny is attempting to deploy a commit to the Consensys Team on Vercel.

A member of the Team first needs to authorize it.

@m4sterbunny m4sterbunny marked this pull request as draft November 14, 2025 13:48
@m4sterbunny m4sterbunny self-assigned this Nov 18, 2025
@m4sterbunny m4sterbunny marked this pull request as ready for review November 18, 2025 15:36
@vercel
Copy link

vercel bot commented Nov 18, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
metamask-docs Ready Ready Preview Comment Nov 19, 2025 4:55pm

@m4sterbunny m4sterbunny changed the title starts updates for trace methods Updates for trace methods Nov 18, 2025
Comment on lines +17 to +23
| Method | Diagnostic options |
|-----------------------|-------------------------------------------|
|[`trace_block`](trace_block.mdx)|[`trace`](#trace)|
|[`trace_call`](trace_call.mdx)|[`trace`](#trace), [`stateDiff`](#statediff)|
|[`trace_callMany`](trace_callmany.mdx)|[`trace`](#trace), [`stateDiff`](#statediff)|
|[`trace_transaction`](trace_transaction.mdx)|[`trace`](#trace)|
|[`trace_filter`](trace_filter.mdx)|[`trace`](#trace)|
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the previous note might be more accurate than the table. For trace_block, trace_transaction, and trace_filter, there are no "diagnostic options," the methods just always return trace information.

| `to` | Target of the transaction. |
| `value` | Value transferred in the transaction. |
|   - `creationMethod` | Opcode used during contract creation: `create` or `create2`. Returned for `create` operations. |
|   - `callType` | Whether the transaction is `call`, `staticcall`, `delegatecall`. Returned for `call` operations. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
|   - `callType` | Whether the transaction is `call`, `staticcall`, `delegatecall`. Returned for `call` operations. |
|   - `callType` | Whether the transaction is `call`, `staticcall`, or `delegatecall`. Returned for `call` operations. |

Comment on lines +87 to +89
- `+` indicates the field didn’t exist before and now has the specified value
- `-` indicates a deleted value
- `*` has a `from` and a `to` value
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `+` indicates the field didnt exist before and now has the specified value
- `-` indicates a deleted value
- `*` has a `from` and a `to` value
- `+` indicates the field didn't exist before and now has the specified value.
- `-` indicates a deleted value.
- `*` has a `from` and a `to` value.

Nit: these are complete sentences, so the periods should stay.

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.

Update to Ethereum trace methods

2 participants