`bullpen doctor wallet`¶

Last updated: July 13, 2026

Compare local wallet cache vs server registry vs on-chain bytecode for every owner EOA.

Usage¶

bullpen doctor wallet [OPTIONS]

Live Help¶

Compare local wallet cache vs server registry vs on-chain bytecode for every owner EOA.

Read-only diagnostic. Prints disagreements with concrete remediation hints. Use this when `bullpen wallet list` shows unexpected results or after a wallet-disappear report.

Usage: bullpen doctor wallet [OPTIONS]

Options:
      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --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:
  # Compare local wallet cache, server registry, and on-chain bytecode
  bullpen doctor wallet

  # Export wallet diagnostic evidence as JSON
  bullpen doctor wallet --output json

Example Commands¶

bullpen doctor wallet
bullpen doctor wallet --output json

JSON Output¶

Contract: JSON Output Contract.

Successful output is a single JSON document. The shape below is representative for this command family; commands may add fields without breaking the shared contract.

Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.

Top-level Keys¶

key	type	nullable	notes
`schema_version`	integer	no	Wallet diagnostic schema version; currently `2`
`status`	string	no	Diagnostic status, such as `ok`, `disagreement`, or `cached_auth_unavailable`
`message`	string	yes	Support-safe explanation when authenticated checks cannot run
`total_owners`	integer	no	Number of owner EOAs included in the diagnostic
`entries`	array	no	Per-owner wallet reconciliation rows when auth is available
`safety`	object	no	Booleans proving the diagnostic did not refresh auth, create signers, or mutate wallet cache
`safety.token_refresh`	boolean	no	Always `false` for cached-auth-unavailable output
`safety.signer_creation`	boolean	no	Always `false` for cached-auth-unavailable output
`safety.wallet_cache_mutation`	boolean	no	Always `false` for cached-auth-unavailable output

Example¶

bullpen doctor wallet --output json

{
  "entries": [],
  "message": "doctor wallet could not run authenticated wallet registry checks because no usable cached access token is available. This support-safe diagnostic did not refresh auth, build signers, or write wallet cache. Run `bullpen doctor auth --refresh --output json` first; run `bullpen login` only if auth diagnostics report that login is required, or use Bullpen support data for offline deposit diagnostics.",
  "safety": {
    "signer_creation": false,
    "token_refresh": false,
    "wallet_cache_mutation": false
  },
  "schema_version": 2,
  "status": "cached_auth_unavailable",
  "total_owners": 0
}

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.

bullpen doctor wallet¶