bullpen funds diagnose-deposit

Last updated: May 29, 2026

Diagnose a missing or wrong-chain deposit without moving funds

Usage

bullpen funds diagnose-deposit [OPTIONS]

Live Help

Diagnose a missing or wrong-chain deposit without moving funds

Usage: bullpen funds diagnose-deposit [OPTIONS]

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

          [possible values: table, json]

      --tx <TX>
          Deposit transaction hash. Requires --chain for support-grade context

      --chain <CHAIN>
          Source chain used for the deposit

          [possible values: polygon, arbitrum, ethereum]

      --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.

      --token <TOKEN>
          Token sent in the deposit

          [possible values: usdc, usdc-e, pusd, usdt]

      --address <ADDRESS>
          Recipient address that received the deposit

      --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 funds diagnose-deposit --help
      Show options for this command without signing, submitting, or changing state.

Example Commands

bullpen funds diagnose-deposit [OPTIONS]
bullpen funds diagnose-deposit --help
bullpen funds diagnose-deposit --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.