Merge branch 'next' into merge-train/docs

Author: AztecBot

docs/developer_versioned_docs/version-v3.0.0-devnet.20251212/getting_started_on_local_network.md

@@ -46,6 +46,12 @@ Run:
 bash -i <(curl -s https://install.aztec.network)
 ```
 
+Once the installation is complete, install the specific version:
+
+```bash
+aztec-up 3.0.0-devnet.20251212
+```
+
 This will install the following tools:
 
 - **aztec** - compiles and tests aztec contracts and launches various infrastructure subsystems (full local network, sequencer, prover, pxe, etc) and provides utility commands to interact with the network
@@ -84,26 +90,6 @@ You'll know the local network is ready to go when you see something like this:
 [INFO] Aztec Server listening on port 8080
 ```
 
-### Codespaces
-
-If you do not want to run the local network locally, or if your machine is unsupported (eg Windows), it is possible to run it within a GitHub Codespace.
-
-[GitHub Codespaces](https://github.com/features/codespaces) are a quick way to develop: they provision a remote machine with all tooling you need for Aztec in just a few minutes. You can use some prebuilt images to make it easier and faster.
-
-Choose a boilerplate and click "create new codespace":
-
-[![One-Click React Starter](/img/codespaces_badges/react_cta_badge.svg)](https://codespaces.new/AztecProtocol/aztec-packages?devcontainer_path=.devcontainer%2Freact%2Fdevcontainer.json) [![One-Click HTML/TS Starter](/img/codespaces_badges/vanilla_cta_badge.svg)](https://codespaces.new/AztecProtocol/aztec-packages?devcontainer_path=.devcontainer%2Fvanilla%2Fdevcontainer.json) [![One-Click Token Starter](/img/codespaces_badges/token_cta_badge.svg)](https://codespaces.new/AztecProtocol/aztec-packages?devcontainer_path=.devcontainer%2Ftoken%2Fdevcontainer.json)
-
-This creates a codespace with a prebuilt image containing one of the "Aztec Boxes" and a development network (local network).
-- You can develop directly on the codespace, push it to a repo, make yourself at home.
-- You can also just use the local network that comes with it. The URL will be logged, you just need to use it as your `PXE_URL`.
-
-You can then start, stop, or see the logs of your local network just by calling `local-network` or `npx aztec-app local-network`. Run `local-network -h` for a list of commands.
-
-Codespaces are way more powerful than you may initially think. For example, you can connect your local `vscode` to a remote codespace, for a fully contained development environment that doesn't use any of your computer resources!
-
-Visit the [codespaces documentation](https://docs.github.com/en/codespaces/overview) for more specific documentation around codespaces.
-
 ## Using the local network test accounts
 
 import { CLI_Add_Test_Accounts } from '@site/src/components/Snippets/general_snippets';
@@ -121,12 +107,18 @@ We'll use the first test account, `test0`, throughout to pay for transactions.
 ## Creating an account in the local network
 
 ```bash
-aztec-wallet create-account -a my-wallet --payment method=fee_juice,feePayer=test0
+aztec-wallet create-account -a my-wallet -f test0
 ```
 
+:::info
+`aztec-wallet` will generate transaction proofs by default. This is not required when sending transactions on the local network, but it is required when sending transactions on the devnet or mainnet.
+
+You can turn off proof generation by adding the `--prover none` flag to the command or setting `PXE_PROVER=none`.
+:::
+
 This will create a new wallet with an account and give it the alias `my-wallet`. Accounts can be referenced with `accounts:<alias>`. You will see logs telling you the address, public key, secret key, and more.
 
-On successful depoyment of the account, you should see something like this:
+On successful deployment of the account, you should see something like this:
 
 ```bash
 New account:
@@ -231,7 +223,7 @@ Simulation result:  100n
 
 ## Playing with hybrid state and private functions
 
-In the following steps, we'll moving some tokens from public to private state, and check our private and public balance.
+In the following steps, we'll move some tokens from public to private state and check our private and public balance.
 
 ```bash
 aztec-wallet send transfer_to_private --from accounts:test0 --contract-address testtoken --args accounts:test0 25

yarn-project/p2p/src/services/tx_provider.test.ts

@@ -203,7 +203,7 @@ describe('TxProvider', () => {
     // Check instrumentation calls
     expect(incTxsFromMempoolSpy).toHaveBeenCalledWith(5);
     expect(incTxsFromProposalsSpy).toHaveBeenCalledWith(1);
-    expect(incTxsFromP2PSpy).toHaveBeenCalledWith(2);
+    expect(incTxsFromP2PSpy).toHaveBeenCalledWith(2, 10);
     expect(incMissingTxsSpy).toHaveBeenCalledWith(2);
   });