chio proof

chio proof

Verify proof bundles and Transaction Passport artifacts.

chio proof [OPTIONS] <COMMAND>

• chio proof assemble Assemble Transaction Passport roots from evidence artifacts.
• chio proof collect Collect a verifier-backed proof bundle from proof artifacts.
• chio proof verify Verify a Transaction Passport proof bundle rooted at a passport JSON file.
• chio proof explain Explain a verifier claim from a proof bundle.
• chio proof fixture List and generate bundled proof fixtures.
• chio proof serve Serve a static Proof Room bundle.
• chio proof export Export a verified proof bundle as a tar archive.
• chio proof doctor Check proof evidence required for a proof scenario.

chio proof assemble

Assemble Transaction Passport roots from evidence artifacts.

chio proof assemble [OPTIONS] --artifact-dir <DIR> --verifier-policy <FILE> --passport-id <PASSPORT_ID> --issued-at <ISSUED_AT> --out <DIR>

• --artifact-dir <DIR> Directory containing evidence artifacts. Required.
• --verifier-policy <FILE> Verifier policy JSON to bind into the passport. Required.
• --passport-id <PASSPORT_ID> Transaction Passport id to write. Required.
• --issued-at <ISSUED_AT> Issued-at timestamp to write into deterministic roots. Required.
• --out <DIR> Directory where assembled roots will be written. Required.

chio proof collect

Collect a verifier-backed proof bundle from proof artifacts.

chio proof collect [OPTIONS] --kind <KIND> --artifact-dir <DIR> --out <DIR>

• --kind <KIND> Proof bundle kind to collect. Required. Values agent-web-envelope, buyer-package, disclosure-agent-web-envelope, evidence, ioa-web3, replay, transaction-passport, runtime-spine.
• --artifact-dir <DIR> Directory containing source proof artifacts. Required.
• --out <DIR> Directory where the collected proof bundle will be written. Required.

chio proof verify

Verify a Transaction Passport proof bundle rooted at a passport JSON file.

chio proof verify [OPTIONS] <PATH>...

• <PATH>... Transaction passports, proof bundle directories, or directories of bundles (such as negatives/), each verified and reported on its own line. A refusal is a result: it prints REFUSED with the verifier’s reason and exits 1, with no error envelope. Required.
• --require <REQUIRE> Require a verified proof claim family. Values commerce, delegation, denials, disclosure, enterprise, external-envelope, risk, runtime, runtime-parity, settlement, trust-market.
• --out <FILE> Write the verifier report to this JSON file.
• --trust <FILE> Trust file to verify against instead of the default (.chio/trust.toml in the project, then ~/.chio/trust.toml). A trust file beside the input is never read on its own. Reads CHIO_TRUST.
• --at <TIME> Evaluate freshness, expiry, and revocation epochs at this time (RFC 3339 or Unix seconds) instead of now.
• --expect <OUTCOME> Expected outcome for every input. Exit 0 when each input meets it, so a directory of negative fixtures passes when every one is refused. Values pass, refuse.

chio proof explain

Explain a verifier claim from a proof bundle.

chio proof explain [OPTIONS] --claim <CLAIM> <BUNDLE>

• <BUNDLE> Proof bundle directory, exported archive, or transaction-passport.json path. Required.
• --claim <CLAIM> Claim id to explain. Required.
• --trust <FILE> Trust file to verify against instead of the default (.chio/trust.toml in the project, then ~/.chio/trust.toml). A trust file beside the input is never read on its own. Reads CHIO_TRUST.
• --at <TIME> Evaluate freshness, expiry, and revocation epochs at this time (RFC 3339 or Unix seconds) instead of now.

chio proof fixture

List and generate bundled proof fixtures.

chio proof fixture [OPTIONS] <COMMAND>

• chio proof fixture list List built-in proof fixtures.
• chio proof fixture generate Generate a built-in proof fixture into a directory.

chio proof fixture list

List built-in proof fixtures.

chio proof fixture list [OPTIONS]

• --family <FAMILY> Show only one fixture family, such as swarm-authority or disclosure-lineage.
• --negatives Show only the fixtures the verifier must refuse.

chio proof fixture generate

Generate a built-in proof fixture into a directory.

chio proof fixture generate [OPTIONS] --out <DIR> <FIXTURE_ID>

• <FIXTURE_ID> Fixture id to generate. Required.
• --out <DIR> Output directory. Required.
• --with-negatives Also write the family’s negative fixtures under negatives/<name>/, each one a bundle the verifier must refuse.

chio proof serve

Serve a static Proof Room bundle.

chio proof serve [OPTIONS] <BUNDLE>

• <BUNDLE> Proof Room bundle directory. Required.
• --listen <LISTEN> Listen address for the static server. Default 127.0.0.1:0.
• --dry-run Validate and print the serving report without opening a server.
• --trust <FILE> Trust file to verify against instead of the default (.chio/trust.toml in the project, then ~/.chio/trust.toml). A trust file beside the input is never read on its own. Reads CHIO_TRUST.
• --open Open the Proof Room in the default browser once the bundle verifies.

chio proof export

Export a verified proof bundle as a tar archive.

chio proof export [OPTIONS] --out <FILE> <BUNDLE>

• <BUNDLE> Proof bundle directory. Required.
• --out <FILE> Output .tgz, .tar.gz, or .tar.zst file path. Required.
• --redact <REDACT> Redaction profile to apply before writing the archive. Values admin-full-evidence-v1, public.

chio proof doctor

Check proof evidence required for a proof scenario.

chio proof doctor [OPTIONS]

• --scenario <SCENARIO> Proof scenario to check. Values agent-web-interop, commerce-payments, disclosure-lineage, enterprise-export, proof-package, public-settlement, runtime-security, single-call-authority, swarm-authority, trust-market, workflow-preflight.
• --in <DIR> Check a directory you generated or collected instead of the fixtures built into the binary.
• --trust <FILE> Trust file to verify against instead of the default (.chio/trust.toml in the project, then ~/.chio/trust.toml). A trust file beside the input is never read on its own. Reads CHIO_TRUST.