Skip to content

fix: remove standalone archiver and PXE start modes#22479

Draft
AztecBot wants to merge 3 commits intonextfrom
claudebox/remove-standalone-archiver-pxe
Draft

fix: remove standalone archiver and PXE start modes#22479
AztecBot wants to merge 3 commits intonextfrom
claudebox/remove-standalone-archiver-pxe

Conversation

@AztecBot
Copy link
Copy Markdown
Collaborator

@AztecBot AztecBot commented Apr 10, 2026

Summary

  • Removed the standalone aztec start --archiver code path -- the archiver is always embedded in the node, so using --archiver alone now exits with a helpful error message (same pattern as --sequencer)
  • Added a handler for aztec start --pxe that similarly errors out instead of silently falling through to "No module specified to start"
  • Deleted the dead start_archiver.ts file
  • Updated --archiver and --pxe flag descriptions in CLI options and docs to clarify they configure components within a node (use with --node)

The --archiver.* and --pxe.* configuration sub-options remain available for configuring these components when running a full node via --node.

Context

  • --archiver as a standalone mode was removed conceptually but the code path and docs were never cleaned up
  • --pxe was defined in commander options but never had a handler, causing a confusing "No module specified" error
  • Setup guides (running-a-node.md, sequencer-setup.md, running-a-prover.md) correctly use --archiver as a component flag alongside --node and are unaffected

fixes: #22293

@AztecBot AztecBot added ci-draft Run CI on draft PRs. claudebox Owned by claudebox. it can push to this PR. labels Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-draft Run CI on draft PRs. claudebox Owned by claudebox. it can push to this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

aztec start --pxe: flag is defined but has no handler ("No module specified to start")

2 participants