Skip to content

Conversation

@idalithb
Copy link
Contributor

request by InfraDAO

@idalithb idalithb requested a review from a team as a code owner October 22, 2025 21:10

The `totalDifficulty` field was [officially removed](https://github.com/ethereum/execution-apis/pull/570) from the `eth_getBlockByNumber` response. Additionally, the `difficulty` field—previously used in Proof of Work—was retained as **optional** but is now considered obsolete and typically returned as `"0x0"` by spec-compliant clients. While some clients continue to include these fields for backward compatibility, developers relying on them should update their subgraphs and tooling to accommodate these schema changes. Full schema details are available in the [Ethereum Execution APIs documentation](https://ethereum.github.io/execution-apis/). We've added a chart with the current client compatibility with these updates as of July 17, 2025. **Please check for specific client updates as needed**.

**Ethereum JSON‑RPC Schema Changes Post-Merge**
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe this should be a heading?

| `difficulty` | ⚠️ Optional, expected to be `0x0` post-Merge, but many clients still return |
| `size` | ⚠️ Optional; may be omitted depending on client |

**Execution Client Compatibility**
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here?

Copy link
Contributor

@benface benface left a comment

Choose a reason for hiding this comment

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

But really, LGTM 👍

@idalithb idalithb merged commit 79cfb09 into main Oct 22, 2025
4 checks passed
@idalithb idalithb deleted the eth-section branch October 22, 2025 21:28
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