Skip to content
CLIUnofficial

privy key-quorums create

Register public authorization keys or existing quorums with an explicit threshold.

Usage

Section titled “Usage”
Terminal window
privy key-quorums create [options]

Options

Section titled “Options”
Option Description
--dry-run Validate and print the API request without network access or credentials.
--yes Confirm this mutation or export.
--body <json> JSON body, or - to read stdin.
--file <path> JSON body file, or - to read stdin.
--display-name <string> Quorum name.
--authorization-threshold <integer> Required approvals; cannot exceed the number of distinct supplied members.
--public-keys <json> Public P-256 authorization keys, base64-encoded SPKI DER. Never supply private keys.
--key-quorum-ids <json> Existing leaf key-quorum IDs in this app; at most five, nested one level deep.
--allow-production Explicitly allow this production mutation; also requires --yes.

Global options such as --app, --account and --profile also apply. See the command reference overview.

Examples

Section titled “Examples”
Terminal window
privy key-quorums create --file quorum.json --dry-run
privy key-quorums create --file quorum.json --yes

Behavior

Section titled “Behavior”
  • Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
  • Scope: app
  • Before it runs: Check app environment and nested quorum existence/depth.
  • Production apps: Requires --allow-production and --yes.
  • Verification: Exact-ID lookup and public member/threshold comparison.
  • Retries: None.
  • Caution: Public registration only. Retain your private keys securely; this operation does not generate or store them.
Section titled “Related guides”

Inspect the full contract locally with privy schema key-quorums create.

Privy CLI is an unofficial, community project by Samarth Saxena. Not affiliated with or endorsed by Privy. The Privy name and wordmark belong to Privy. It uses undocumented dashboard APIs that can change.