Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase zkCounter limit, decouple sequencer from prover #1595

Open
doutv opened this issue Dec 23, 2024 · 0 comments
Open

Increase zkCounter limit, decouple sequencer from prover #1595

doutv opened this issue Dec 23, 2024 · 0 comments
Labels
question Further information is requested

Comments

@doutv
Copy link
Collaborator

doutv commented Dec 23, 2024

Problem: 4337 Account Abstraction signature verification throughput is low
1 user operation = 1 EOA + 1 Passkey signature verification

Current state:

  • TPS: 50
  • 25 user operations per block, due to zkCounter limit

I increase zkCounter to 1<<27. The sequencer throughput is much better:

  • TPS: 90
  • 69 user operations per block

forkId11TotalSteps = 1 << 25

Completely decouple sequencer from prover

According to the official docs, the design philosophy is to decouple sequencer from prover.
But zkCounter indeed slows down sequencer

image

Can we support larger zkCounter in zkEVM-prover?

Larger zkCounter, higher memory, slower proving time.
Is there a way to adjust how many blocks proved in a batch?

@doutv doutv changed the title Increase zkCounter limit, in order to increase signature verification throughput Increase zkCounter limit, decouple sequencer from prover Dec 23, 2024
@revitteth revitteth added the question Further information is requested label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants