fix: remove standalone archiver and PXE start modes#22479
Draft
fix: remove standalone archiver and PXE start modes#22479
Conversation
Maddiaa0
approved these changes
Apr 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
aztec start --archivercode path -- the archiver is always embedded in the node, so using--archiveralone now exits with a helpful error message (same pattern as--sequencer)aztec start --pxethat similarly errors out instead of silently falling through to "No module specified to start"start_archiver.tsfile--archiverand--pxeflag 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
--archiveras a standalone mode was removed conceptually but the code path and docs were never cleaned up--pxewas defined in commander options but never had a handler, causing a confusing "No module specified" errorrunning-a-node.md,sequencer-setup.md,running-a-prover.md) correctly use--archiveras a component flag alongside--nodeand are unaffectedfixes: #22293