`bullpen wallet rescan`¶

Last updated: July 13, 2026

Rescan Bullpen-managed signing keys, probe on-chain state, and cross-reference against the server wallet registry. Surfaces wallets that exist in your account or on-chain but are missing from the server registry

Usage¶

bullpen wallet rescan [OPTIONS]

Live Help¶

Rescan Bullpen-managed signing keys, probe on-chain state, and cross-reference against the server wallet registry. Surfaces wallets that exist in your account or on-chain but are missing from the server registry

Usage: bullpen wallet rescan [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:
  # Refresh wallet registry state from Bullpen-managed keys and on-chain probes; this changes account metadata
  bullpen wallet rescan

  # Export the rescan report as JSON
  bullpen wallet rescan --output json

Example Commands¶

bullpen wallet rescan
bullpen wallet rescan --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	Response schema version
`source`	string	no	Rescan source, such as `bullpen_refresh_turnkey`, `local_turnkey_fallback`, or `mixed`
`wallets`	array	no	Wallet registry rows and Turnkey/on-chain reconciliation details
`bullpen_refresh_error`	string	yes	Bullpen account-service refresh error when a local Turnkey fallback was used

Example¶

Example JSON output

bullpen wallet rescan --output json

{
  "schema_version": 1,
  "source": "bullpen_refresh_turnkey",
  "wallets": [
    {
      "owner": "0x1111111111111111111111111111111111111111",
      "safe_addr": "0x2222222222222222222222222222222222222222",
      "dw_addr": "0x3333333333333333333333333333333333333333",
      "safe_deployed": true,
      "dw_deployed": false,
      "server_lists_it": true,
      "missing_action": "OK",
      "user_id": "user-1",
      "server_wallet_ids": [
        "wallet-1"
      ],
      "turnkey_wallet_ids": [],
      "turnkey_sub_org_ids": []
    }
  ]
}

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 wallet rescan¶