Skip to main content
Version: dev

Day-2 essentials

Time: ~5 minutes. Your sequencer is running. Here's what to know for ongoing operations.

Useful commands​

All commands below run from inside the ~/aztec-sequencer/ directory you created in Configure environment.

# View logs
docker compose logs -f aztec-sequencer

# Restart the node
docker compose restart aztec-sequencer

# Stop the node
docker compose down

# Update to latest version
docker compose pull && docker compose up -d

# Check disk usage (run inside ~/aztec-sequencer/)
du -sh ./data

Claim rewards​

Two paths:

  • Aztec staking dashboard — aggregates pending rewards across every sequencer you operate, claims in one wallet flow. Easiest for most operators.
  • CLI claim — see the upstream Claiming Rewards guide for the full reference (pending-rewards check, claimSequencerRewards cast send, keystore-file and hardware-wallet variants, gas-limit troubleshooting).
Claiming may be gated

Both paths revert with Rollup__RewardsNotClaimable (0xe8b9b951) until governance enables claiming on the Rollup you targeted (isRewardsClaimable() == true). On testnet that gate is currently closed; on mainnet it's open. If you hit the error, your rewards are still accruing but not yet withdrawable.

Monitoring​

Aztec exports metrics via OpenTelemetry. The full monitoring stack:

  • OpenTelemetry Collector receives metrics from the node via OTLP.
  • Prometheus stores time-series metrics.
  • Grafana renders dashboards and alerts.

Key metrics to watch:

  • Attestation rate (target: 99%+)
  • Block proposals
  • Committee participation
  • Peer count
  • Disk usage
Lightweight alternative

Don't want to set up the full OTEL stack? pittpv/aztec-monitoring-script is a community tool that monitors your node and sends alerts to Telegram.

See the full monitoring setup guide when you're ready for the proper stack.

Upgrades​

When a new version is released:

# Pull new image and restart
docker compose pull && docker compose up -d

# Verify version
docker compose logs aztec-sequencer | head -20
Watch for upgrade announcements

Follow Discord and the changelog for upgrade announcements. Some upgrades require action within a specific timeframe.

Slashing awareness​

Aztec uses a Tally Model with 6 offense types. Short outages from connectivity issues are not penalized harshly. Persistent double-signing or liveness failures accumulate penalty points and eventually trigger slashing. See the slashing and offenses reference for the exact thresholds and offense definitions.

You finished the Playbook​

Your sequencer is live. The Tally Model is gentle on transient outages, so don't panic over a single missed attestation. Focus on keeping the publisher funded, the L1 endpoints reliable, and the container restarting on its own. The rest is automation.