privy integrations blockaid update
Configure blockaid. Production-app-only cross-app scanning configuration; also requires an enabled verified cookie domain or non-private ecosystem. No production conversion, billing change, domain, account approval or publishing is performed implicitly.
privy integrations blockaid update [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. |
--scanning-enabled <boolean> |
Enable transaction scanning for the cross-app wallet ecosystem. |
--ofac-screening-enabled <boolean> |
Enable OFAC screening. Does not perform a screening request now. |
--diff |
Read live state and show changes WITHOUT writing (requires login). |
--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”privy integrations blockaid update --body - --dry-runBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: app
- Verification: Allowlisted read-back; masked credentials are not exact-value proof; no external integration verification.
- Retries: No automatic write retries.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema integrations blockaid update.
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.