You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to give a heads-up on the upcoming change to latest chain headers rpc response format change. The change is currently deployed to testnet and will soon be pushed to mainnet. This is required to make ethereum tooling compatible (e.g., chainlink). I am aware that many validator tools rely on this, hence asking if there any concerns in updating your tooling.
I wanted to give a heads-up on the upcoming change to latest chain headers rpc response format change. The change is currently deployed to testnet and will soon be pushed to mainnet. This is required to make ethereum tooling compatible (e.g., chainlink). I am aware that many validator tools rely on this, hence asking if there any concerns in updating your tooling.
Before:
After:
Also the rpcs impacted are:
and
Also, the
newBlockHeaders
subscription:PRs responsible for this change: #3655, #3658, and #3659
The text was updated successfully, but these errors were encountered: