chore(docs): Add 2.0.2 testnet docs, remove old versions and replace references to 1.2.0 (#17129)

adds the latest testnet release version

Author: AztecBot

docs/CLAUDE.md

@@ -67,7 +67,7 @@ Uses Docusaurus versioning with:
 - `versioned_docs/version-X.X.X/` contains historical versions
 - `versioned_sidebars/` contains version-specific sidebar configurations
 - Macros (`#include_code`, `#include_aztec_version`, etc.) only work in source `docs/` folder, not in versioned copies
-- Version dropdown shows: `Next`, `alpha-testnet`, and latest sandbox release versions
+- Version dropdown shows: `Next`, `testnet`, and latest sandbox release versions
 
 ## Documentation Review Standards
 

docs/README.md

@@ -24,7 +24,7 @@ The .md files in the `docs/` directory are the docs. See the [Docusaurus website
 
 Aztec Docs are versioned. Every version known is literally a copy of the website, and is in `versioned_docs` (sidebars are in `versioned_sidebars`). Seems silly but it's not, it allows you to hot-fix previous versions.
 
-When you look at the published docs site, you will see three versions in the version dropdown: `Next`, `alpha-testnet`, and the latest sandbox release e.g. `v0.86.0`. Updating the files in the `docs` folder will update the next version (which is not currently published, but will be when the next release is cut), updating the files in `versioned_docs/version-v0.87.8` folder will update the `0.87.8` version. Note that you cannot use the macros (`#include_aztec_version` and `#include_code`) in the `versioned_docs` folder, since those docs have already been processed and built. Instead, just drop the code snippets, version numbers or links directly in the docs as you'd like them to be rendered.
+When you look at the published docs site, you will see three versions in the version dropdown: `Next`, `testnet`, and the latest sandbox release e.g. `v0.86.0`. Updating the files in the `docs` folder will update the next version (which is not currently published, but will be when the next release is cut), updating the files in `versioned_docs/version-v0.87.8` folder will update the `0.87.8` version. Note that you cannot use the macros (`#include_aztec_version` and `#include_code`) in the `versioned_docs` folder, since those docs have already been processed and built. Instead, just drop the code snippets, version numbers or links directly in the docs as you'd like them to be rendered.
 
 The way docs builds work is the following:
 

docs/docs/developers/guides/getting_started_on_testnet.md

@@ -64,7 +64,7 @@ Set the required environment variables:
 
 ```bash
 export NODE_URL=https://aztec-alpha-testnet-fullnode.zkv.xyz
-export SPONSORED_FPC_ADDRESS=0x19b5539ca1b104d4c3705de94e4555c9630def411f025e023a13189d0c56f8f2
+export SPONSORED_FPC_ADDRESS=0x299f255076aa461e4e94a843f0275303470a6b8ebe7cb44a471c66711151e529
 ```
 
 ### Step 2: Create and deploy an account

docs/docs/developers/reference/environment_reference/cli_reference.md

@@ -76,7 +76,7 @@ Options:
 
 #### Network Options
 
-- `--network <value>`: Network to run Aztec on, e.g. `alpha-testnet`. By default connects to sandbox (local network)
+- `--network <value>`: Network to run Aztec on, e.g. `testnet`. By default connects to sandbox (local network)
 
 #### API Options
 
@@ -122,10 +122,10 @@ Options:
 
 ##### Example Usage
 
-Here is an example of how to start a node that connects to the alpha-testnet.
+Here is an example of how to start a node that connects to the testnet.
 
 ```bash
-aztec-up alpha-testnet
+aztec-up latest
 
 export DATA_DIRECTORY=/any/directory/to/store/node/data
 export BLOB_SINK_URL=<blob-sink-url>

docs/docs/developers/reference/environment_reference/cli_wallet_reference.md

@@ -163,7 +163,7 @@ To connect to the testnet, pass the `AZTEC_NODE_URL` to the wallet with the `--n
 
 ```bash
 export AZTEC_NODE_URL=<testnet-ip-address>
-export SPONSORED_FPC_ADDRESS=0x19b5539ca1b104d4c3705de94e4555c9630def411f025e023a13189d0c56f8f2
+export SPONSORED_FPC_ADDRESS=0x299f255076aa461e4e94a843f0275303470a6b8ebe7cb44a471c66711151e529
 # Register a new account
 aztec-wallet create-account --register-only -a main -n $AZTEC_NODE_URL
 aztec-wallet register-contract $SPONSORED_FPC_ADDRESS SponsoredFPC --from main -n $AZTEC_NODE_URL --salt 0 -a sponsoredfpc

docs/docs/the_aztec_network/guides/run_nodes/how_to_run_prover.md

@@ -207,7 +207,7 @@ services:
       - --prover-node
       - --archiver
       - --network
-      - alpha-testnet
+      - testnet
     depends_on:
       prover-broker:
         condition: service_started
@@ -237,7 +237,7 @@ services:
       - start
       - --prover-broker
       - --network
-      - alpha-testnet
+      - testnet
     environment:
       DATA_DIRECTORY: /var/lib/data
       ETHEREUM_HOSTS: ${ETHEREUM_HOSTS}
@@ -255,7 +255,7 @@ services:
       - start
       - --prover-agent
       - --network
-      - alpha-testnet
+      - testnet
     environment:
       PROVER_AGENT_COUNT: ${PROVER_AGENT_COUNT}
       PROVER_AGENT_POLL_INTERVAL_MS: ${PROVER_AGENT_POLL_INTERVAL_MS}

docs/docs/the_aztec_network/guides/run_nodes/how_to_run_sequencer.md

@@ -55,7 +55,6 @@ Furthermore, as this guide uses Docker compose, you will need to install it. Ple
 
 Finally, this guide requires you to have endpoints of an L1 node stack of an execution and consensus client. If you do not have one set up, you can see a good guide on how to do that [here at Eth Docker](https://ethdocker.com/Usage/QuickStart).
 
-
 ## Configure the sequencer
 
 There are a few important things to note when setting up a sequencer. This guide will guide you in setting up and running a sequencer with a standard setup using Docker compose with a .env file.
@@ -162,39 +161,39 @@ Now that you have done all the setup, create a Docker compose file named `compos
 
 ```yaml
 services:
- aztec-sequencer:
-  image: "aztecprotocol/aztec:1.2.1"
-  container_name: "aztec-sequencer"
-  ports:
-    - ${AZTEC_PORT}:${AZTEC_PORT}
-    - ${P2P_PORT}:${P2P_PORT}
-    - ${P2P_PORT}:${P2P_PORT}/udp
-  volumes:
-    - ${DATA_DIRECTORY}:/var/lib/data
-    - ${KEY_STORE_DIRECTORY}:/var/lib/keystore
-  environment:
-    KEY_STORE_DIRECTORY: /var/lib/keystore
-    DATA_DIRECTORY: /var/lib/data
-    LOG_LEVEL: ${LOG_LEVEL}
-    ETHEREUM_HOSTS: ${ETHEREUM_HOSTS}
-    L1_CONSENSUS_HOST_URLS: ${L1_CONSENSUS_HOST_URLS}
-    P2P_IP: ${P2P_IP}
-    P2P_PORT: ${P2P_PORT}
-    AZTEC_PORT: ${AZTEC_PORT}
-  entrypoint: node /usr/src/yarn-project/aztec/dest/bin/index.js
-  command: >-
-    start
-    --network alpha-testnet
-    --node
-    --archiver
-    --sequencer
-  networks:
-   - aztec
-  restart: always
+  aztec-sequencer:
+    image: "aztecprotocol/aztec:latest"
+    container_name: "aztec-sequencer"
+    ports:
+      - ${AZTEC_PORT}:${AZTEC_PORT}
+      - ${P2P_PORT}:${P2P_PORT}
+      - ${P2P_PORT}:${P2P_PORT}/udp
+    volumes:
+      - ${DATA_DIRECTORY}:/var/lib/data
+      - ${KEY_STORE_DIRECTORY}:/var/lib/keystore
+    environment:
+      KEY_STORE_DIRECTORY: /var/lib/keystore
+      DATA_DIRECTORY: /var/lib/data
+      LOG_LEVEL: ${LOG_LEVEL}
+      ETHEREUM_HOSTS: ${ETHEREUM_HOSTS}
+      L1_CONSENSUS_HOST_URLS: ${L1_CONSENSUS_HOST_URLS}
+      P2P_IP: ${P2P_IP}
+      P2P_PORT: ${P2P_PORT}
+      AZTEC_PORT: ${AZTEC_PORT}
+    entrypoint: node /usr/src/yarn-project/aztec/dest/bin/index.js
+    command: >-
+      start
+      --network testnet
+      --node
+      --archiver
+      --sequencer
+    networks:
+      - aztec
+    restart: always
 
 networks:
- aztec:
-  name: aztec
+  aztec:
+    name: aztec
 ```
 
 Please note that we are setting only the necessary configuration for running this sequencer. The full list of settings and flags can be explored here at the [cli reference](../../reference/cli_reference.md). A lot of these options are preset to defaults by the `--network` flag above. This downloads defaults for the specified network and applies them to the node.

docs/docs/the_aztec_network/index.md

@@ -68,10 +68,10 @@ echo 'export PATH="$HOME/.aztec/bin:$PATH"' >> ~/.bashrc
 source ~/.bashrc
 ```
 
-The next step is to install the correct version of aztec that is running on testnet. The correct version of the aztec network currently is `1.2.0`. If that is not the version that was installed in the previous step, please run this to ensure the correct version is installed.
+The next step is to install the correct version of aztec that is running on testnet. The correct version of the aztec network currently is #include_testnet_version. If that is not the version that was installed in the previous step, please run this to ensure the correct version is installed.
 
 ```console
-aztec-up 1.2.0
+aztec-up #include_testnet_version
 ```
 
 The user can confirm that they are running on the correct version with:

docs/docs/the_aztec_network/reference/operator_faq.md

@@ -16,9 +16,9 @@ Here is a list of common issues node operators may face. If you don't find your
 
 If it is regarding a beacon call, it has failed to the beacon rpc call. If it is regarding the execution endpoint, then it is likely just reporting.
 
-## Update aztec alpha-testnet version
+## Update aztec testnet version
 
-To make sure you're using the latest version, run: `aztec-up alpha-testnet`, then restart your node.
+To make sure you're using the latest version, run: `aztec-up latest`, then restart your node.
 
 ## "rpc rate", "quota limit"
 

docs/docs/the_aztec_network/reference/reacting_to_upgrades.md

@@ -11,7 +11,7 @@ This is a guide for sequencer operators to understand how to react to protocol u
 To signal for governance upgrades, sequencers must set their `GOVERNANCE_PROPOSER_PAYLOAD` on their sequencer node to the address of a `payload`. This will register their signal with the GovernanceProposer contract.
 
 :::info
-the `payload` is a contract on L1 that specifies the address of the new rollup contract to be upgraded to. The payloads to be voted on during alpha-testnet will be communicated to sequencers on the forum and on community channels like discord.
+the `payload` is a contract on L1 that specifies the address of the new rollup contract to be upgraded to. The payloads to be voted on during testnet will be communicated to sequencers on the forum and on community channels like discord.
 :::
 
 This signalling phase will pass once `N` sequencers in a round of `M` L2 blocks have signalled for the same payload. Once the quorum is met, anyone can call the `executeProposal(roundNumber)` function on the Governance Proposer contract to advance the upgrade into the next stage.