-
Notifications
You must be signed in to change notification settings - Fork 305
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
refactor: contract deployment cleanup #4137
Conversation
Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
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. Values are compared against data from master at commit 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 16 txs.
Circuits statsStats on running time and I/O sizes collected for every circuit run across all benchmarks.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contracts are deployed in the tx.
Transaction processing duration by data writes.
|
b9e80cc
to
86428cf
Compare
766e985
to
055a4ce
Compare
@@ -25,6 +25,7 @@ | |||
], | |||
"dependencies": { | |||
"@aztec/foundation": "workspace:^", | |||
"@aztec/l1-artifacts": "workspace:^", |
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.
This seems like an anti-pattern. Pretty much everything in yarn-project will now depend on l1-artifacts when most of it shouldn't need to should it?
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.
Perhaps look to extract ethereum
from so far up the dependency tree if we want to do this.
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.
Good point. I checked and negatively affected by this are these packages:
Boxes
Pxe
Sequencer-client
Circuit-types
aztec.js
Aztec-node
Aztec-faucet
I will rework this.
There were too many wrappers around a simple deployment L1 contract functions and a ton of unused abstractions that I decided to clean it all up.