For the complete documentation index, see llms.txt.
Skip to main content

Updates, alerts, rewards

Time: ~5 minutes. Your sequencer is running. Set up three things before you call it done: version upgrades, monitoring alerts, and reward claiming. The rest of this page is reference material to keep handy.

1. Stay current on 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

Some upgrades require action within a specific timeframe; a node left on an old version eventually stops attesting. Watch the channels in Where to stay informed below, especially Discord, where time-sensitive upgrade notices are posted first.

2. Set up monitoring and alerts​

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.

3. 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 Claiming Rewards guide for the full reference (pending-rewards check, claimSequencerRewards cast send, keystore-file and hardware-wallet variants, gas-limit troubleshooting).

Slashing awareness​

Slashing is tiered. Inactivity (failing to attest or propose when assigned) is slashed 2,000 AZTEC, and so is submitting a proposal with invalid attestations. Duplicate proposals and duplicate attestations are slashed 5,000 AZTEC. There is a 190,000 AZTEC ejection threshold below which the sequencer is ejected. See Slashing for the full offense set and thresholds.

Where to stay informed​

  • Discord — upgrade announcements and operator discussion. This is where version updates and time-sensitive notices are posted first.
  • Forum — longer-form proposals, governance, and operator announcements.
  • GitHub — source, issues, and releases.
  • Changelog — per-version operator-facing changes and migration notes.

You finished the guide​

Your sequencer is live. Focus on keeping the publisher funded, the L1 endpoints reliable, and keeping your node on the latest recommended version.