bullpen hyperliquid activity

Last updated: July 13, 2026

Show Hyperliquid ledger activity, with unsupported Hyperunit source metadata in this release

Usage

bullpen hyperliquid activity [OPTIONS]

Live Help

Show Hyperliquid ledger activity, with unsupported Hyperunit source metadata in this release

Usage: bullpen hyperliquid activity [OPTIONS]

Options:
      --address <ADDRESS>
          Ethereum address to query. Defaults to the authenticated account

      --no-multi-wallet-warning
          Suppress the table-mode warning shown when multiple EVM wallet accounts exist

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

      --kind <KIND>
          Activity kind to include

          [default: all]
          [possible values: all, deposit, withdrawal, transfer, vault, hyperunit, reward, unknown]

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

      --source <SOURCE>
          Activity source to include

          [default: all]
          [possible values: all, hyperliquid, hyperunit]

      --start <START>
          Start of the activity window in Unix milliseconds. Defaults to 30 days ago

      --end <END>
          End of the activity window in Unix milliseconds. Defaults to the current time

      --limit <LIMIT>
          Maximum number of rows to display

          [default: 100]

      --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:
  # Show recent Hyperliquid ledger activity for an address
  bullpen hyperliquid activity --address 0x1111111111111111111111111111111111111111 --limit 20

  # Export deposit support data as JSON
  bullpen hyperliquid activity --address 0x1111111111111111111111111111111111111111 --kind deposit --output json

  # Query a specific activity window in Unix milliseconds
  bullpen hyperliquid activity --address 0x1111111111111111111111111111111111111111 --start 1700000000000 --end 1700086400000 --limit 50

SAFETY:
  This command is read-only. It queries Hyperliquid ledger history only and does not sign, submit /exchange actions, generate deposit addresses, or submit withdrawals.

OUTPUT:
  --kind vault includes vault ledger rows such as vaultDeposit, vaultCreate,
  vaultDistribution, vaultWithdraw, and vaultLeaderCommission. Table output
  includes a Context column; JSON preserves provider fields such as from, to,
  operation_id, status_detail, and support_summary when Hyperliquid returns them.

Example Commands

bullpen hyperliquid activity --address 0x1111111111111111111111111111111111111111 --limit 20
bullpen hyperliquid activity --address 0x1111111111111111111111111111111111111111 --kind deposit --output json
bullpen hyperliquid activity --address 0x1111111111111111111111111111111111111111 --start 1700000000000 --end 1700086400000 --limit 50

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.

In this release, Hyperliquid ledger rows are supported and Hyperunit operation rows are deferred. --source all reports Hyperunit as an unsupported partial source; --source hyperliquid skips Hyperunit; --source hyperunit returns a support-safe unsupported empty report without making a Hyperunit provider request.

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.