-
Notifications
You must be signed in to change notification settings - Fork 272
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
feat: reduce the amount of key hashing required to fetch public keys #7997
Conversation
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. Proof generationEach column represents the number of threads used in proof generation.
L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 8 txs.
Circuits statsStats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.
Stats on running time collected for app circuits
AVM SimulationTime to simulate various public functions in the AVM.
Public DB AccessTime to access various public DBs.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contract classes are registered in the tx.
Transaction size based on fee payment method | Metric | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cute 🐣💖😊🌸✨
This is failing because my new unconstrained helper creates an Fixing this is not terribly hard but also not trivial, so I'll leave this open since we're unsure about whether we'll keep key rotation at all. |
Closing this as we're changing how addresses and keys are related. |
Closes #7825
We now hash each set of public keys once instead of twice by having a smarter oracle function that always returns the correct value, instead of two that we need to call conditionally.
This reduces the gate count of a token transfer by ~3k, though this reduction is expected to be lower and closer to ~1k once #7954 is closed, since we'll then be performing fewer total key read operations.