Skip to content

Assess native Chonk verification time requirements #1635

Description

@ledwards2225

To include:

  • Understanding and documenting the points in the network where native Chonk verification time is a TPS bottleneck
  • Making an informed assessment of a "good enough" target
  • Assessing whether engineering-style tactics (e.g. optimistic batched IPA verification) are useful/sufficient (maybe in some places but not all?)
  • Getting buy in from stake-holders on said targets

Activity

  1. ledwards2225 commented on Mar 9, 2026

    @ledwards2225
    CollaboratorAuthor

    Batched Chonk verifier has been merged so this issue is now about assessing whether it get's us where we need to be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions