chore: Initial draft of testnet-runbook #10085
Conversation
Changes to circuit sizes
🧾 Summary (100% most significant diffs)
Full diff report 👇
|
|
|
||
| ## Releases | ||
|
|
||
| The engineering team's testnet responsibilities begin after code-freeze. Here are the primary tasks: |
There was a problem hiding this comment.
Worth mentioning maybe that the code freeze is for the branch that passes #9631 the previous week
|
|
||
| ## Deployment | ||
|
|
||
| After cutting a release, deploy a testnet (typically with 48 validators) using the new Docker containers. Verbose logging on Aztec nodes should be enabled by default using the following `ENV VARS`: |
There was a problem hiding this comment.
For the testnets we deploy, we should begin with a small number (i.e. 4 validators) to start with.
Then under Sanity Check, we can add 1-2 more validators (run by us) to test that nodes can sync the chain. After that we invite external validators to join
| - Block proving (Prover: `Processed 1 new L2 blocks`) | ||
| - Epoch proving (Prover: `Submitted proof for epoch`) | ||
|
|
||
| 3. Test external node connection and sync |
There was a problem hiding this comment.
How about we standardize when we do it? i.e. spotcheck for 3 epochs then add one external validator (that we run) to test it can sync.
| 3. BOOT_NODE_URL (Kubernetes: `kubectl get services -n <namespace> | (head -3; grep boot)`) | ||
| - boot-node-lb-tcp: `<EXTERNAL-IP>:40400` | ||
| - boot-node-lb-udp: `<EXTERNAL-IP>:40400` | ||
|
|
There was a problem hiding this comment.
At a certain epoch (i.e. 5) once the sanity check passes, Product / DevRel will coordinate with node operators who have already connected to the network using the information above.
Product / DevRel verify that node operators are seeing correct logs, then pass on validator addresses of those ready to engineering so that engineering can add them to the validator set. We do this until we add all 48 validators.
|
|
||
| ### Network Connection Info | ||
|
|
||
| After a successful sanity check, share the following network connection information in the `#team-alpha` slack channel and with the wider Aztec community: |
There was a problem hiding this comment.
Product / DevRel to share with the sequencer & prover discord channel.
Change log
This PR includes an initial draft of the Aztec testnet runbook.
fixes: #9839