Homebrew
Install the Guard CLI with Homebrew and use the protected installer for mainnet services.
Homebrew installs the Guard CLI on macOS and Linux:
brew install zunderlabs/tap/zunder-guardzunder-guard --versionInstallation for this channel is unavailable until its signed publication is verified. Prepare your rules in the setup wizard.
Mainnet
Section titled “Mainnet”Use the verified machine-service installer, even if the CLI is already installed through Homebrew:
curl -fsSL https://zunderlabs.com/i | sh -s -- --network mainnetInstallation for this channel is unavailable until its signed publication is verified. Prepare your rules in the setup wizard.
This creates a separate managed installation: System Keychain and a system LaunchDaemon on macOS, or systemd encrypted credentials on Linux. Its executable, credential and state paths are protected independently of Homebrew. Never use sudo with a Cellar executable to provision mainnet, and do not point installation channel pending verification at the mainnet state directory.
Follow the printed account confirmation, equity cap, hidden key prompt, journal and explicit Start steps. Use the machine service’s printed commands for pairing, licence activation, upgrades and status; the Homebrew CLI’s default home refers to a different installation. macOS guide · Linux guide
brew upgrade zunder-guard upgrades the package-managed CLI. Upgrade a mainnet machine service through its verified installer and management instructions instead, preserving its configuration and journals.
Paper rehearsal
Section titled “Paper rehearsal”The Homebrew service runs paper mode only. Prepare its separate home before starting it:
ZUNDER_GUARD_HOME="$(brew --prefix)/var/zunder-guard" zunder-guard init --interactive --network paperbrew services start zunder-guardInstallation for this channel is unavailable until its signed publication is verified. Prepare your rules in the setup wizard.
Keep the same ZUNDER_GUARD_HOME when managing this paper installation. For a foreground testnet rehearsal, initialize a separate home for testnet and run with --network testnet; do not replace the paper service’s command with a mainnet command. Testnet setup explains its per-user key storage before saving the key.
Verify the package
Section titled “Verify the package”Homebrew checks the archive’s SHA-256 from the release formula. For independent verification, verify the matching signed release archive using Verify a release and compare its binary with the installed one:
zunder-guard --versionshasum -a 256 "$(command -v zunder-guard)"Stop the Homebrew service with installation channel pending verification. Uninstalling the package is separate from removing the machine mainnet service or deleting its retained journals.
This page as plain Markdown, for people and LLMs: /docs/deploy/packages.md