bullpen polymarket wallet-audit¶
Last updated: May 29, 2026
Detect split-brain / assets-in-both state across all owner EOAs.
Usage¶
Live Help¶
Detect split-brain / assets-in-both state across all owner EOAs.
Enumerates every owner EOA in your Turnkey suborg, queries the server for the per-owner Polymarket wallet selection, probes on-chain balances on the Safe / Deposit Wallet / signer-EOA, and reports any assets that are stranded on a non-selected wallet. Read-only — never submits transactions.
Usage: bullpen polymarket wallet-audit [OPTIONS]
Options:
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--owner <ADDRESS>
Restrict the audit to a single owner EOA (0x-prefixed address). Defaults to all owner EOAs in the suborg
--env <ENV>
Target environment to connect to (overrides config.toml)
[env: BULLPEN_ENV=]
[possible values: staging, production]
--refresh
Force a fresh server query, bypassing any cached wallet selection
--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.
--include-clob-credit
Also fetch off-chain CLOB credit.
Off by default for support-safe diagnostics. Enabling this may build per-wallet Turnkey signers and authenticate with Polymarket CLOB.
--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 wallet-audit --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen polymarket wallet-audit [OPTIONS]
bullpen polymarket wallet-audit --help
bullpen polymarket wallet-audit --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.