CLI Commands

Achronyme CLI command reference.

Global Flags

These flags apply to all subcommands:

init — Create a new project

Scaffolds a new Achronyme project with achronyme.toml, source directory, and .gitignore.

ach init my-circuit
ach init my-app --template vm

Arguments

Flags

Templates

• circuit — A standalone circuit with public/witness declarations and assert_eq
• vm — A general-purpose program with print()
• prove — A mixed program with an inline prove {} block

Generated structure

my-circuit/
├── achronyme.toml
├── src/
│   └── main.ach
└── .gitignore

See Project Configuration for the achronyme.toml reference.

verify — Verify detached Groth16 artifacts

Verification is independent of project configuration and does not create a proving key. The curve is required so the CLI never infers a cryptographic format from untrusted input:

ach verify \
  --proof proof.json \
  --public public.json \
  --vkey verification_key.json \
  --curve bn254 \
  --format json

Supported curves are bn254 and bls12-381. Invalid, malformed, mismatched, or tampered artifacts return a non-zero exit status.

Missing or unreadable artifacts are operational errors, not invalid proofs. --error-format json selects JSON output for detached verification when verify --format is omitted. An explicit verify --format text or verify --format json takes precedence.

trusted-setup — Package an externally verified key

ach trusted-setup package creates an immutable trusted-key store from an already verified BN254 Groth16 ceremony. It requires the exact R1CS, final and pre-beacon zkeys, phase-1 artifact and digest, every contributor ID and hash, and the committed public-beacon evidence.

ach trusted-setup package --help

This command does not run a ceremony or invent missing evidence. Operators should follow the versioned trusted-setup workflow in the core repository.

run — Execute a program

Runs an Achronyme source file (.ach) or compiled binary (.achb).

ach run script.ach
ach run script.achb
ach run                # uses [project].entry from achronyme.toml

If <path> is omitted, the CLI resolves the entry file from [project].entry in achronyme.toml.

Flags

Examples

ach run hello.ach
ach run hello.ach --prove-backend plonkish
ach run hello.ach --max-heap 256M --gc-stats
ach run                              # from project with achronyme.toml

circuit — Compile a ZK circuit

Compiles an Achronyme circuit source file into R1CS/Plonkish constraints and generates a witness.

ach circuit circuit.ach --inputs "x=42,y=7"
ach circuit --inputs "x=42,y=7"    # uses entry from achronyme.toml

See Circuit Options for all available flags.

circom — Compile a .circom file

Compiles a Circom 2.x source file through the Achronyme frontend, producing the same .r1cs/.wtns artefacts as circuit and optionally a Groth16 proof. Use this to run circomlib templates (or your own .circom projects) without leaving the Achronyme toolchain.

ach circom poseidon.circom --inputs "in=42"
ach circom merkle.circom --inputs "root=0x...,leaf=42" --prove --solidity Verifier.sol
ach circom -l vendor/circomlib/circuits sha256.circom --inputs-file inputs.toml

Flags

Library resolution

include lookup walks --lib directories first, then [circom].libs from the project manifest, then the file’s own directory. See Importing Templates for the full resolution model.

compile — Compile to bytecode

Compiles an Achronyme source file into a binary (.achb) that can be run with ach run.

ach compile script.ach --output script.achb
ach compile --output script.achb   # uses entry from achronyme.toml

Flags

aot — Compile a native executable

Compile Achronyme source or an .achb image through LLVM and link it against the packaged Achronyme AOT runtime:

ach aot src/main.ach --output build/app
ach aot program.achb --output build/app --clang clang-21

--runtime <path> overrides discovery of libakron_aot_runtime.a. AOT requires Clang 21 and LLVM 21.

The standalone executable starts with filesystem and network authority denied. Runtime grants and limits are selected when the binary runs, not embedded from the ach aot command:

AKRON_ALLOW_READ=/srv/app/data \
AKRON_MAX_TASKS=32 \
AKRON_INSTRUCTION_BUDGET=1000000 \
./build/app

AKRON_ALLOW_READ and AKRON_ALLOW_WRITE accept platform path lists. AKRON_ALLOW_CONNECT and AKRON_ALLOW_LISTEN accept comma-separated numeric addresses. Heap and GC controls use AKRON_MAX_HEAP and AKRON_STRESS_GC. Every structured-runtime limit also has an uppercase AKRON_ equivalent, from AKRON_MAX_TASKS and AKRON_MAX_RESOURCES through AKRON_BLOCKING_QUEUE_CAPACITY.

disassemble — Show bytecode

Disassembles an Achronyme source file or binary, showing the bytecode instructions.

ach disassemble script.ach
ach disassemble                    # uses entry from achronyme.toml

inspect — Open the circuit inspector

Compiles a circuit (or a named prove {} block) and serves a local HTTP page that visualises the IR DAG, witness values, and constraint stats. The Astro+D3 inspector UI lives in the achronyme-inspector repo and ships embedded for offline use.

ach inspect circuit.ach --inputs "x=42"
ach inspect script.ach --prove main_block --inputs "secret=7"
ach inspect --bind 127.0.0.1 --port 3000

Flags