You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the official docs, the design philosophy is to decouple sequencer from prover. But zkCounter indeed slows down sequencer
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?
The text was updated successfully, but these errors were encountered:
doutv
changed the title
Increase zkCounter limit, in order to increase signature verification throughput
Increase zkCounter limit, decouple sequencer from prover
Dec 23, 2024
Problem: 4337 Account Abstraction signature verification throughput is low
1 user operation = 1 EOA + 1 Passkey signature verification
Current state:
I increase zkCounter to
1<<27
. The sequencer throughput is much better:cdk-erigon/core/vm/zk_counters_limits.go
Line 15 in 451cb91
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
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?
The text was updated successfully, but these errors were encountered: