chore: move boxes out of yarn-project

[dan-aztec]

boxes are purely downstream of the other TS packages in the workspace

[AztecBot]

Benchmark results

No metrics with a significant change found.

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 ff893b23 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	222,936	867,692	3,447,848
l1_rollup_execution_gas	842,023	3,594,800	22,203,217
l2_block_processing_time_in_ms	2,207	8,449	35,064
note_successful_decrypting_time_in_ms	317 (+2%)	914	3,334 (+1%)
note_trial_decrypting_time_in_ms	27.2 (+29%)	40.2 (+4%)	197 (-1%)
l2_block_building_time_in_ms	20,215	80,521	321,816
l2_block_rollup_simulation_time_in_ms	16,690	66,606	266,192
l2_block_public_tx_process_time_in_ms	3,493 (-1%)	13,847	55,382

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	25,056 (+2%)	47,760 (+1%)
note_history_successful_decrypting_time_in_ms	2,210 (+4%)	4,164
note_history_trial_decrypting_time_in_ms	163 (+1%)	227
node_database_size_in_bytes	3,406,957 (-6%)	3,804,587 (-3%)
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	199	43,109	20,441
private-kernel-ordering	115 (+1%)	25,833	9,689
base-rollup	2,955	667,692	873
root-rollup	86.4 (-2%)	4,072	881
private-kernel-inner	260	64,516	20,441
public-kernel-private-input	171	25,203	20,441
public-kernel-non-first-iteration	168	25,245	20,441
merge-rollup	10.9 (+1%)	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	25,938

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
eslint-config-prettier	9.0.0	None	+0	20.8 kB	lydell
@types/mocha	10.0.6	None	+0	95.6 kB	types
@types/react-dom	18.2.17	None	+0	33.1 kB	types
formik	2.4.5	environment	+4	1.23 MB	jaredpalmer
react	18.2.0	None	+0	316 kB	gnoff
react-dom	18.2.0	None	+4	5.32 MB	gnoff
yup	1.3.2	None	+2	269 kB	monastic.panic
memfs	4.6.0	None	+1	988 kB	streamich
eslint-plugin-react-refresh	0.4.4	None	+0	448 kB	arnaud-barre
@typescript-eslint/parser	6.5.0...6.2.1	None	+0/-5	19 kB	jameshenry

🚮 Removed packages: @types/[email protected], @types/[email protected], @types/[email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]

[charlielye]

Def don't want these committed. Surprised it doesn't break ci build. Should prob add catch all .tsbuildinfo to root .gitignore for safety.

[charlielye]

Can these be implemented using our standard container runner cond_run_container or cond_spot_run_container, or compose cond_run_compose or cond_spot_run_compose scripts?

[dan-aztec]

yes i think so! I can do that in a follow up PR to keep this one digestible

[dan-aztec]

re-opening without conflicts in another branch