Skip to content

Parallelize commitment validation using block access lists #17377

Closed

Description

@yperbasis

Block-Level Access Lists provide post-state, so it's possible to do state root validation on multiple CPUs in parallel as well as concurrently with EVM execution validation. (Not helpful for block building performance since we don't have the BAL then yet, but should be a boon for block validation performance.)

Activity

  1. added this to the 3.4.0 milestone on Oct 7, 2025
  2. VBulikov commented on Oct 7, 2025

    @VBulikov
    Member

    yperbasis added Imp1 as Importance

  3. changed the title [-]Parallelize commitment using block access lists[/-] [+]Parallelize commitment validation using block access lists[/+] on Oct 7, 2025
  4. modified the milestones: 3.4.0, 3.5.0 on Jan 8, 2026
  5. removed this from the 3.5.0 milestone on May 6, 2026
  6. 2 remaining items

  7. modified the milestones: 3.6.0, 3.7.0 on Jul 24, 2026
  8. modified the milestones: 3.7.0, 3.8.0 on Sep 16, 2026
  9. modified the milestones: 3.8.0, 3.9.0 on Sep 30, 2026
  10. awskii commented on Oct 16, 2026

    @awskii
    Member

    Done in #21416: BAL-driven commitment computes the root ahead of execution and checks it against the header (committer.go#L646); on by default, parallel trie default since #23831. Tip blocks don't compute ahead (committer.go#L659), tracked in #23091.

  11. modified the milestones: 3.9.0, 3.8.0 on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions