feat(AVM): First version for mini AVM (ADD, RETURN, CALLDATACOPY)

[jeanmon]

First version of a mini AVM.

Resolves #3376
Resolves #3378
Resolves #3379
Resolves #3380
Resolves #3320
Resolves #3321

[AztecBot]

Benchmark results

Metrics with a significant change:

• note_trial_decrypting_time_in_ms (8): 40.2 (-35%)

Detailed results

All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.

This benchmark source data is available in JSON format on S3 here.

Values are compared against data from master at commit 4735bdeb and shown if the difference exceeds 1%.

L2 block published to L1

Each column represents the number of txs on an L2 block published to L1.

Metric	8 txs	32 txs	128 txs
l1_rollup_calldata_size_in_bytes	45,444	179,588	716,132
l1_rollup_calldata_gas	223,008	868,184	3,449,312
l1_rollup_execution_gas	842,095	3,595,292	22,204,681
l2_block_processing_time_in_ms	2,044 (-1%)	7,906	31,597 (-1%)
note_successful_decrypting_time_in_ms	331 (-5%)	988 (-4%)	3,691 (-1%)
note_trial_decrypting_time_in_ms	⚠️ 40.2 (-35%)	114 (-9%)	200
l2_block_building_time_in_ms	25,304 (-1%)	100,589 (-1%)	402,916 (-1%)
l2_block_rollup_simulation_time_in_ms	17,716 (-1%)	70,518 (-2%)	281,853 (-1%)
l2_block_public_tx_process_time_in_ms	7,542	29,924 (-1%)	120,503 (-1%)

L2 chain processing

Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric	5 blocks	10 blocks
node_history_sync_time_in_ms	22,842 (+1%)	44,289 (+1%)
note_history_successful_decrypting_time_in_ms	2,432 (+5%)	4,671 (+4%)
note_history_trial_decrypting_time_in_ms	167 (+4%)	236 (+3%)
node_database_size_in_bytes	3,317,494	3,657,936
pxe_database_size_in_bytes	29,748	59,307

Circuits stats

Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit	circuit_simulation_time_in_ms	circuit_input_size_in_bytes	circuit_output_size_in_bytes
private-kernel-init	400	43,077	20,441
private-kernel-ordering	126	25,833	9,689
base-rollup	3,184	659,500	873
root-rollup	92.6 (+3%)	4,072	1,097
private-kernel-inner	827	64,484	20,441
public-kernel-private-input	418	25,203	20,441
public-kernel-non-first-iteration	413	25,245	20,441
merge-rollup	10.9	2,592	873

Miscellaneous

Transaction sizes based on how many contracts are deployed in the tx.

Metric	0 deployed contracts	1 deployed contracts
tx_size_in_bytes	10,323	29,083

[Rumata888]

We use capital letters for labels

[Rumata888]

NUM_WIRES usually means the number of witness used by the circuit builder (so these are the witnesses that have just the arithmetic elements, without witness polynomials which help in creating the proof, such as grand product polynomials, inverse polynomials, etc)

[Rumata888]

Everything looks, good. I'd only change the comments style so it can be parsed by doxygen and fits the standard style in barretenberg and expand the comments a bit. And postpone sorting the ordered memory trace until proof creation

[Maddiaa0]

lgtm, minor nit then we can send it