Installation

Downloads

Get the binaries from the Orchard releases page. Each release lists its assets alongside SHA256SUMS. The 0.1.0 names are:

Linux builds are static musl binaries. Windows builds use the static CRT. macOS builds link system libraries dynamically; that is normal.

Verify a download

Download SHA256SUMS from the same release. Compare the line for your asset with your locally computed digest. A checksum detects a damaged or substituted file only when you trust the checksum's source.

# macOS; replace the filename with the asset you downloaded
shasum -a 256 or-0.1.0-macos-arm64
# Linux
sha256sum or-0.1.0-linux-amd64

On Windows, use PowerShell:

Get-FileHash .\or-0.1.0-windows-amd64.exe -Algorithm SHA256

Put or on PATH

After verification, rename the downloaded Unix binary to or, make it executable, and put it in a directory on your PATH. This example uses the Apple silicon asset; choose the Linux or Intel file when appropriate.

mkdir -p "$HOME/.local/bin"
install -m 755 ./or-0.1.0-macos-arm64 "$HOME/.local/bin/or"
export PATH="$HOME/.local/bin:$PATH"
or --version
or --help

Add the PATH line to your shell's startup file to keep it across sessions. On Windows, rename the file to or.exe, place it in a directory you control, add that directory to your user PATH, and open a new terminal.

macOS signing and the keychain

Bare binaries can use local files, local.device identities and pairing. They cannot access the Ourcana app's shared data-protection keychain. The app.keychain route needs a signed .app bundle with an embedded provisioning profile granting the shared keychain access group; signing a bare binary is not enough.

Releases also include or-0.1.0-macos-arm64.app.zip, or-0.1.0-macos-amd64.app.zip and or-0.1.0-macos-universal.app.zip. When a bundle is properly signed, keep it intact and run its executable inside Contents/MacOS/or. Do not copy that executable out and expect its keychain access to survive.

Build from source

You need a recent stable Rust toolchain. bab_rs is vendored as a git submodule, so clone with --recurse-submodules.

git clone --recurse-submodules https://code.heni.lol/Ourcana/orchard.git
cd orchard
cargo build --release
./target/release/or --help

A normal Cargo build does not grant macOS shared-keychain access. The source tree's packaging/build.sh documents the provisioned bundle route.