bullpen polymarket reregister-deposit-wallet¶
Last updated: August 26, 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 through the older gasless deployment 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. This confirms deployment registration only; it does not change which Polymarket wallet is selected for trading. Run `wallet-audit --refresh --include-order-credit --output json` and follow `summary.repair.next_command` only when it is present.
Re-run only after wallet-audit or Bullpen support confirms the same deployed wallet still needs registration; do not repeat after an unknown or external relayer rejection without reconciliation.
`--force-relayer-refresh` is a support-only compatibility override for older registration incidents. Do not use it after `POLYMARKET_RELAYER_WALLET_NOT_REGISTERED` unless Bullpen support gives that exact instruction; current builds classify that rejection as support-owned external state.
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]
--force-relayer-refresh
Support-only compatibility override. Do not use after an external wallet-registration rejection unless Bullpen support gives this exact command
--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:
# Open the registration repair confirmation flow
bullpen polymarket reregister-deposit-wallet
# Re-register after reviewing the confirmation prompt
bullpen polymarket reregister-deposit-wallet --yes
# Support-directed compatibility override only
bullpen polymarket reregister-deposit-wallet --force-relayer-refresh --yes
# Emit JSON for the confirmed registration repair
bullpen polymarket reregister-deposit-wallet --yes --output json
NOTES:
There is no separate --preview flag. The command authenticates, verifies the
Deposit Wallet deployment and registry state, prints the registration repair
plan, and then prompts before asking Bullpen to repair registration.
Example Commands¶
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.