What this is

bundle-deploy is a small, dependency-light CLI for publishing an already-encoded bundle of bytes to a running Flux mesh miner, under a signed mesh name (.ark/.deadark/.fxn), plus a signed public-read marker so the result is readable by strangers without a fleet credential. It talks to an already-running miner's HTTP API over plain fetch — no GUN client, no libp2p, no IPFS daemon of its own.

The binaries below are Node's own Single Executable Application (SEA) feature: the real bundle-deploy source bundled into one file and injected into a copy of the Node runtime. They are genuine standalone executables — nothing to install, no Node on the target machine required.

Downloads

checksums.sha256.txt — verify your download with shasum -a 256 -c checksums.sha256.txt (macOS/Linux) before you run anything.

macOS: the Gatekeeper warning

This binary is ad-hoc signed, not notarized by Apple (notarization needs a paid Apple Developer account this project doesn't have). The first time you run it, macOS Gatekeeper will say it "cannot be verified" or is from an "unidentified developer." Two ways around it, once you've verified the checksum above:

xattr -d com.apple.quarantine bundle-deploy-macos-arm64

— or right-click the file in Finder, choose "Open," and confirm once at the prompt.

What you get

After downloading, make it executable and run it directly:

chmod +x bundle-deploy-macos-arm64
./bundle-deploy-macos-arm64 status

Basic usage:

bundle-deploy status
bundle-deploy prepare <file> --name <name.fxn> [--content-type <type>] [--owner-key <b64>]
bundle-deploy prepare <file> --name <name.fxn> --identity-file <path> [--publish]

With neither --status/--pin/--key, a running miner on this machine is auto-discovered. --identity-file is for operators/CI only — a browser-based admin signs through the library API instead, so a private key never has to touch disk.