Platform capabilities

ENI6MA exposes three surfaces that work together: the Registry (public API), the Ledger (nonce lifecycle and replay prevention), and the circuit binary (CLI). Developers integrate with three API calls: challenge, ceremony, validate. Below is an overview of all major CLI commands and where each capability lives; deep-dives are linked for each area.

Full CLI command list and implications

The circuit binary supports the following command groups. Commands can be run locally (binary on your machine) or via the Registry POST .../cli/{command}. Developers should understand: what each command does, whether it is used locally or via the Registry proxy, and implications for replay, rate limits, audit, and revocation.

CLI command categories: Proof/session, Ledger, Message/blockchain, Verifier/client, Hybrid A2A, with commands and implications.
Category	Commands	What to document / implications
Proof / session	`pool, challenge, validate-response, validate-proof, validate-proof-payload, interactive, nonce-interactive, synthesize, simulator`	Purpose, when used (local vs Registry proxy), implication for integration (replay, rate limit).
Ledger	`ledger/status, ledger/tx, ledger/mine, ledger-service`	Read/append ledger; implication for audit and sovereign mode.
Message / blockchain	`enigma-hash, sign-msg, verify-msg, opret-encrypt, opret-decrypt, ethereum-address, sign-ethereum-tx, verify-ethereum-tx`	Enigma-ECDSA bridge; implications for custody and APIs.
Verifier / client	`verifier, client`	Roles in proof flows (challenge generation vs proof submission).
Hybrid (A2A)	`respond-interactive, agent init, discover, respond, oscillate`	Agent-to-agent and sovereign; when to use hybrid vs standard.