privy config smart-wallets update
Configure smart-wallets. Complete enabled smart-wallet configuration or enabled:false. Does not deploy wallets, contact a bundler, sign, transact or provision/fund sponsorship.
privy config smart-wallets 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. |
--enabled <boolean> |
Enable future smart-wallet creation, or disable it. Does not disable existing smart wallets or perform transactions. |
--smart-wallet-type <string> |
Provider for the complete enabled configuration. |
--smart-wallet-version <string> |
Coinbase requires explicit 1.1. Legacy vulnerable 1 is readable but refused for writes. Other providers use null/omit. |
--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 config smart-wallets 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 config smart-wallets 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.