RPC2026-03-23_023

RPC Standards #023

2026-03-23 2 decisions 334 transcript lines

Transcript

At a glance

Safe block tag repurposed for FCR instead of justification
Close PR #297 (JWT secrets) due to lack of client interest
End of March - First FCR clients ready for testing
Q2 2026 - FCR expected in productionverify date

Detailed notes

Organizational

  • •JWT secrets PR (297) closed; no client consensus after 3 years00:33:01
  • •Engine API and REST endpoint changes not in scope for RPC call00:46:48

Rpc Method Updates

  • •testing_buildBlockV1 ready to merge after conflict resolution00:24:00
  • •eth_getStorageValues implemented in Geth, Reth, Erigon; Nethermind in progress00:28:52
  • •eth_getTransactionBySenderAndNonce requires new index; implementation complexity uncertain00:35:58

Fast Confirmation Rule

  • •FCR decreases confirmation time from 13 minutes to 13 seconds00:06:45
  • •Safety assumptions: network synchrony and <25% adversarial stake00:09:08
  • •~95% of blocks fast-confirmed within 12 seconds00:10:29
  • •Safe block tag repurposed from justification to FCR00:14:42
  • •First clients ready for testing end of March; production Q200:15:29
  • •Different clients may return different safe blocks during transition00:16:14

Action items

  • •Announce merged error code spec to client teamsSimsonraj
  • •Resolve conflicts and merge testing_buildBlockV1 PR #747Chase Wright
  • •Merge eth_getStorageValues PR #756 to specFelix (Geth)

Agenda

From the call issue #1974Show

Agenda (more items to be added):

  1. Fast Confirmation Rule (FCR) — Presented by Julian & Will
    • Overview of FCR and how it works
    • Impact on the 'safe' block tag
    • Q&A

Should Merge:

Needs review / Discussion:

Key decisions

  • Safe block tag repurposed for FCR instead of justification

    Fast Confirmation Rule (FCR) changes
  • Close PR #297 (JWT secrets) due to lack of client interest

    PR #297 (JWT secrets) closed

AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.