You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3.`config/local-network.json`, `config/devnet.json`, and/or`config/testnet.json` — `settings.version` (update the configs relevant to the branch you're on)
147
156
4.`README.md` — install command version
148
157
158
+
> **Note:** The `next` and `testnet` branches may pin different Aztec versions. Only update the config files relevant to the branch.
159
+
149
160
## ONBOARDING.md Maintenance
150
161
151
162
`ONBOARDING.md` is **generated** — do not edit it directly. Edit `docs/ONBOARDING.src.md` instead, then rebuild:
Copy file name to clipboardExpand all lines: README.md
+25-2Lines changed: 25 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,16 @@ You can find the **Pod Racing Game contract** in `./src/main.nr`. A simple integ
16
16
17
17
The Pod Racing contract is a two-player competitive game where players allocate points across 5 tracks over multiple rounds. The game demonstrates Aztec's private state capabilities - round choices remain private until players reveal their final scores.
18
18
19
-
## Devnet
19
+
## Devnet & Testnet
20
20
21
-
This repo connects to a locally running Aztec local network by default, but can be configured to connect to the devnet by specifying `AZTEC_ENV=devnet` in a `.env` file or by prefixing a command e.g. `AZTEC_ENV=devnet yarn deploy`.
21
+
This repo connects to a locally running Aztec local network by default, but can be configured to connect to remote networks:
22
+
23
+
-**Devnet**: `AZTEC_ENV=devnet` — development network on the `next` branch
24
+
-**Testnet**: `AZTEC_ENV=testnet` — test network on the `testnet` branch
25
+
26
+
Set the variable in a `.env` file or prefix a command, e.g. `AZTEC_ENV=devnet yarn deploy`.
27
+
28
+
> **Branch model:** Devnet code lives on the `next` branch. Testnet code lives on the `testnet` branch. Each branch may run a different Aztec version.
22
29
23
30
<divalign="center">
24
31
@@ -55,6 +62,7 @@ This project uses JSON configuration files to manage environment-specific settin
55
62
56
63
-`config/local-network.json` - Configuration for local network development
57
64
-`config/devnet.json` - Configuration for devnet deployment
65
+
-`config/testnet.json` - Configuration for testnet deployment
58
66
59
67
The system automatically loads the appropriate configuration file based on the `AZTEC_ENV` environment variable. If `AZTEC_ENV` is not set, it defaults to `local-network`.
The `::devnet` suffix automatically sets `AZTEC_ENV=devnet`, loading configuration from `config/devnet.json`.
91
99
100
+
### Running on Testnet
101
+
102
+
Similarly, all scripts support a `::testnet` suffix:
103
+
104
+
```bash
105
+
yarn deploy::testnet # Deploy to testnet
106
+
yarn test::testnet # Run tests on testnet
107
+
yarn deploy-account::testnet # Deploy account to testnet
108
+
yarn interaction-existing-contract::testnet # Interact with testnet contracts
109
+
```
110
+
111
+
The `::testnet` suffix sets `AZTEC_ENV=testnet`, loading configuration from `config/testnet.json`.
112
+
113
+
> **Note:** Testnet code should be developed and merged into the `testnet` branch, not `next`. The `testnet` branch may use a different Aztec version than the `next` (devnet) branch.
0 commit comments