Aztec Project
Background
The Infrastructure team operates Aztec nodes for both Mainnet and Testnet. Aztec is a privacy-focused Layer 2 solution for Ethereum that enables private smart contract execution.
List of Services
- Aztec Validator Nodes - Validator nodes running Aztec protocol
- Aztec Publisher Nodes - Publisher nodes for transaction submission
Networks
- Mainnet - Production Aztec mainnet
- Testnet (Sepolia) - Aztec testnet environment
Deployment
Aztec infrastructure is deployed using Ansible playbooks located in:
infrastructure-general/ansible/general/playbooks/
Deployment Steps
-
Get the latest image tag:
- Aztec Node: Check with Aztec team for latest version
- Current mainnet:
2.1.8 - Current testnet:
2.1.5
-
Update image tag in inventory:
infrastructure-general/ansible/general/inventory/hosts-aztec.ini
-
Deploy using Ansible:
ansible-playbook playbooks/start-aztec-node.yml -l <hostname> -
Verify deployment and check metrics
Key Management
Aztec mainnet nodes require keystore files for:
- Ethereum attester keys
- BLS attester keys
- Publisher keys
Keystore files are managed via Ansible Vault and deployed to nodes during setup.
Monitoring
- Metrics: Collected via Prometheus with
project_name: "aztec"label - Alerts: ⚠️ Alert routing needs to be configured - Currently no Alertmanager route exists for
project_name: "aztec". Alerts will route to the null receiver until PagerDuty integration is added. - Logs: Collected via Promtail/Loki
Note: To enable PagerDuty alerting for Aztec, add a route in Alertmanager configuration (
infrastructure-general/ansible/general/playbooks/templates/alertmanager_rules.yml) and configure a PagerDuty integration key.
Configuration
Key configuration files:
- Inventory:
infrastructure-general/ansible/general/inventory/hosts-aztec.ini - Playbook:
infrastructure-general/ansible/general/playbooks/start-aztec-node.yml - Keystore template:
infrastructure-general/ansible/general/playbooks/templates/aztec-mainnet-keystore.json