Add Aztec L2 sequencer network support

[bussyjd]

Goal

Enable deployment of Aztec sequencers through obolup, allowing operators to run Aztec L2 infrastructure alongside their Ethereum validators using the existing Obol Stack.

Problem

Currently, operators who want to run an Aztec sequencer need to:

• Manually set up separate infrastructure
• Configure L1 endpoints independently
• Manage keys and monitoring separately from their Obol setup

Solution

Integrate Aztec sequencer deployment into obolup with automatic L1 connectivity and unified monitoring.

Requirements

1. Aztec Sequencer Configuration

Based on Aztec docs, we need:

Hardware Requirements:

• 2 core / 4 vCPU
• 16 GB RAM
• 1TB NVMe SSD
• P2P port forwarding (40400)

Key Components:

• Validator keys (attester, publisher)
• L1 RPC connection (execution + consensus)
• P2P networking configuration
• Data persistence volumes

2. Implementation Approach

Add flag to obolup

obolup --network aztec

Testing

1. Deploy on testnet with existing Sepolia stack
2. Verify L1 connectivity
3. Check P2P peer discovery
4. Confirm block production
5. Validate monitoring metrics

Success Criteria

• Aztec sequencer deploys with single obolup command
• Automatically uses existing L1 RPC endpoints
• Keys are securely managed
• Metrics visible in Grafana
• P2P networking functional
• Documentation complete

Open Questions

1. Should we support multiple sequencers per stack?
2. How to handle key rotation?
3. Should prover nodes be included in scope?

References

• https://docs.aztec.network/the_aztec_network/guides/run_nodes/how_to_run_sequencer
• PR Test integration of an aztec l2 full-node #19 (WIP implementation)