fix: do not publish empty contract data#4022
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. 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.
|
| this.log(`Failed to publish new contract data for block ${block.number}`); | ||
| const newContracts = validTxs.flatMap(tx => tx.newContracts).filter(cd => !cd.isEmpty()); | ||
|
|
||
| if (newContracts.length > 0) { |
There was a problem hiding this comment.
Don't suppose we could invert the check, early return and reduce the nesting?
This PR fixes the sequencer publishing contract for every transaction. Fix AztecProtocol#2970
This PR fixes the sequencer publishing contract for every transaction.
Fix #2970