bullpen polymarket deploy-deposit-wallet¶
Last updated: May 29, 2026
Deploy and activate your Polymarket deposit wallet.
Usage¶
Live Help¶
Deploy and activate your Polymarket deposit wallet.
Some Polymarket accounts are required to use a deterministic deposit wallet instead of the legacy Safe/proxy wallet. If every buy or sell returns "maker address not allowed, please use the deposit wallet flow", run this command once to deploy the wallet and switch your account to the deposit-wallet path permanently.
This is a one-time setup. After it completes, all future buy/sell/redeem commands use the deposit-wallet flow automatically.
Usage: bullpen polymarket deploy-deposit-wallet [OPTIONS]
Options:
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--yes
Skip the confirmation prompt
--env <ENV>
Target environment to connect to (overrides config.toml)
[env: BULLPEN_ENV=]
[possible values: staging, production]
--config <CONFIG>
Path to a custom config.toml file (overrides $BULLPEN_CONFIG and the default location).
Explicit --config and BULLPEN_CONFIG paths fail closed: if the file is missing, the CLI exits validation instead of silently loading defaults. Credentials still resolve via BULLPEN_HOME, so set BULLPEN_HOME too when isolating a session.
--read-only
Enable read-only mode: blocks all mutating commands
--non-interactive
Suppress interactive prompts; does NOT imply --yes for money-moving commands
[env: BULLPEN_NON_INTERACTIVE=]
-h, --help
Print help (see a summary with '-h')
EXAMPLES:
bullpen polymarket deploy-deposit-wallet --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen polymarket deploy-deposit-wallet [OPTIONS]
bullpen polymarket deploy-deposit-wallet --help
bullpen polymarket deploy-deposit-wallet --output json
JSON Output¶
Contract: JSON Output Contract.
This command supports --output json, but this generated reference page intentionally does not include a synthetic success schema or example.
Use the live command in your target environment to inspect command-specific success fields. Error output follows the shared JSON output contract linked above.
Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.
Stability¶
Patch releases may add nullable or optional fields. Minor releases may add required fields or increment schema_version. Major releases may remove or rename fields.