EIPsInsight

Loading Experience

Preparing your insights...

Loading0%
RPC2026-03-23_023

RPC Standards #023

2026-03-23 2 decisions 334 transcript lines

Transcript

Call summary

Targets
  • End of March - First FCR clients ready for testing - 00:15:29
  • Q2 2026 - FCR expected in production - 00:15:36
Decisions
  • Safe block tag repurposed for FCR instead of justification - 00:14:42
  • Close PR #297 (JWT secrets) due to lack of client interest - 00:33:50
Highlights
  • Organizational:
    • ·JWT secrets PR (297) closed; no client consensus after 3 years - 00:33:01
    • ·Engine API and REST endpoint changes not in scope for RPC call - 00:46:48
  • Rpc Method Updates:
    • ·testing_buildBlockV1 ready to merge after conflict resolution - 00:24:00
    • ·eth_getStorageValues implemented in Geth, Reth, Erigon; Nethermind in progress - 00:28:52
    • ·eth_getTransactionBySenderAndNonce requires new index; implementation complexity uncertain - 00:35:58
  • Fast Confirmation Rule:
    • ·FCR decreases confirmation time from 13 minutes to 13 seconds - 00:06:45
    • ·Safety assumptions: network synchrony and <25% adversarial stake - 00:09:08
    • ·~95% of blocks fast-confirmed within 12 seconds - 00:10:29
    • ·Safe block tag repurposed from justification to FCR - 00:14:42
    • ·First clients ready for testing end of March; production Q2 - 00:15:29
    • ·Different clients may return different safe blocks during transition - 00:16:14
Action Items
  • Simsonraj - Announce merged error code spec to client teams - 00:23:05
  • Chase Wright - Resolve conflicts and merge testing_buildBlockV1 PR #747 - 00:28:47
  • Felix (Geth) - Merge eth_getStorageValues PR #756 to spec - 00:30:02

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.

Contact dev@avarch.org