fix: typo fix roundup

[ludamad]

We now have a policy about trivial changes. We regret this, but have felt it is the right call on balance to deal with a precendent set with using github commit counts for airdrops. We will revisit this. Rounding up these changes:

commit d26a855d989c8bca7787e979024a6fbfc7af15c6
Author: Darigov Research [email protected]
Date: Sun Nov 12 13:34:24 2023 +0000

fix: Corrects typo in privacy considerations page

commit ce63e9875041542ed537c18ee7227101a8cb775e
Author: Darigov Research [email protected]
Date: Sun Nov 12 13:28:49 2023 +0000

fix: Removes unintended new line

commit 34c841ff40b3a6126b7abf25e5a81ec18c7e472a
Author: Darigov Research [email protected]
Date: Sun Nov 12 13:27:42 2023 +0000

fix: Makes typo corrections to limitations page of docs

commit 7be85ee645a120d260d3c679bf8aa7158e419f2d
Author: Darigov Research [email protected]
Date: Sun Nov 12 13:10:25 2023 +0000

refactor: Makes Boxes subrepo readme easier to consume

commit 6c481f6667633fe602ab56bcce162168283918ea
Author: Darigov Research [email protected]
Date: Sun Nov 12 13:04:06 2023 +0000

fix: corrects typos in aztec-sandbox readme

commit 718a33684f126f24213d6b0ebd0e9d63e1d2cc13
Author: Darigov Research [email protected]
Date: Sun Nov 12 13:00:23 2023 +0000

refactor: Updates packages readme to make commands one click copyable

commit 3ffd0fc56d3fd725b7301d782ff512345cd1581c
Author: Darigov Research [email protected]
Date: Sun Nov 12 12:48:46 2023 +0000

refactor: removes incorrect adjustment

commit 07a203327a05eb6ba43f15d3eb98c42fbb34cfa5
Author: Darigov Research [email protected]
Date: Sun Nov 12 12:46:43 2023 +0000

fix: Corrects typo in circuits readme

commit ac0d407699ff069cfb8cff197dec8ac580badf14
Author: Darigov Research [email protected]
Date: Sat Nov 11 23:20:26 2023 +0000

fix: Makes nargo install command one click copyable

commit 19f499c06c9eb933870e6734e9e44da466c18150
Author: Darigov Research [email protected]
Date: Sat Nov 11 22:43:34 2023 +0000

fix: Updates storage_slots.md in docs to be easier to read

commit e75dce05ff23d55b374a76d07290db70e54e756c
Author: Darigov Research [email protected]
Date: Sat Nov 11 22:20:33 2023 +0000

fix: Corrects copy in state model page

commit 5ae91ba138a21340942af73fd380aaabce3140b7
Author: Web-person [email protected]
Date: Sat Nov 11 21:50:37 2023 +0100

typos in public_vm.md

fix typos

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.

[ludamad]

@web3-person @darigovresearch Again, regret the policy, it isn't an easy choice. I have bundled your changes here and reference the history in the commit message. Thank you for the contributions, we will continue to find a way to get changes in, and will revisit this soon.

[web3-person]

@web3-person @darigovresearch Again, regret the policy, it isn't an easy choice. I have bundled your changes here and reference the history in the commit message. Thank you for the contributions, we will continue to find a way to get changes in, and will revisit this soon.

Sure thing, I don’t really care how they get in so long as they do :)

[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 f1095124 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,172	3,446,420
l1_rollup_execution_gas	842,095	3,595,280	22,201,789
l2_block_processing_time_in_ms	2,000 (+1%)	7,657	29,771 (-1%)
note_successful_decrypting_time_in_ms	297 (+1%)	872 (-1%)	3,189
note_trial_decrypting_time_in_ms	100 (+4%)	82.0 (-10%)	135 (+1%)
l2_block_building_time_in_ms	13,401 (+1%)	52,815	209,954
l2_block_rollup_simulation_time_in_ms	12,030 (+1%)	47,481	188,791
l2_block_public_tx_process_time_in_ms	1,326 (+1%)	5,203 (-1%)	20,671 (-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	21,874 (-1%)	42,744
note_history_successful_decrypting_time_in_ms	2,125 (+2%)	4,165 (+3%)
note_history_trial_decrypting_time_in_ms	121	145
node_database_size_in_bytes	1,629,513	1,095,829
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	763	61,697	18,905
private-kernel-ordering	126 (+1%)	24,297	8,153
base-rollup	1,769	656,311	814
root-rollup	178 (+6%)	4,072	1,097
private-kernel-inner	788	81,568	18,905
public-kernel-private-input	41.3	41,519	18,841
public-kernel-non-first-iteration	26.0	41,497	18,841
merge-rollup	15.3 (+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	8,787	27,547

[darigovresearch]

@web3-person @darigovresearch Again, regret the policy, it isn't an easy choice. I have bundled your changes here and reference the history in the commit message. Thank you for the contributions, we will continue to find a way to get changes in, and will revisit this soon.

@ludamad & @kevaundray thanks for letting us know, in general it's your repo so you and other mods can manage contributors however you deem is best

For context we were going through the docs and using the edit button in the UI to update the docs as that was easier than forking the whole repo and finding the files in the monorepo.

Some suggestions come to mind from the new policy and it raises some questions that could be clarified further. Could you please provide some thoughts and advise on the queries when you have a moment to ensure that any future pull requests match your new policy?

Hope you and your team are all well and will continue to try to make significant contributions!

Suggestions:

• When collating merging minor changes would suggest using the GitHub feature to add an author to a commit so that it can be attributed correctly in a diff & not just referenced in an issue
• It would make sense to outline under the contributing guidelines this new policy to avoid disheartening genuine contributors in particular who want to improve on your work

Queries:

• What counts as a significant contribution?
  • Would it be adding new pages and content, big feature additions in terms of code. big corrections to the documentations etc
• What is the new precedent that you mention?
  • i.e. would multiple text corrections across multiple files in one commit okay but multiple minor commits not okay etc