bullpen polymarket reregister-deposit-wallet¶
Last updated: May 29, 2026
Re-register an already-deployed deposit wallet with the Bullpen server.
Usage¶
Live Help¶
Re-register an already-deployed deposit wallet with the Bullpen server.
When the CLI deploys a deposit wallet via the relayer WALLET-CREATE path, it does not write to the server's wallet-status registry. This causes web and mobile apps to show $0 because they read `isDeployed: false` from the server even though the wallet is live on-chain.
Run this command after `deploy-deposit-wallet` if the web/mobile app still shows $0. Then log out and log back in on the affected app to refresh the cached status.
This command is safe to re-run — the server-side registration is idempotent.
Usage: bullpen polymarket reregister-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 reregister-deposit-wallet --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen polymarket reregister-deposit-wallet [OPTIONS]
bullpen polymarket reregister-deposit-wallet --help
bullpen polymarket reregister-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.