bullpen hyperliquid watch fundings

Last updated: May 29, 2026

Watch real-time funding updates for an address

Usage

bullpen hyperliquid watch fundings [OPTIONS]

Live Help

Watch real-time funding updates for an address

Usage: bullpen hyperliquid watch fundings [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]

      --allow-duplicate
          Allow a duplicate listener for this stream/scope

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

      --updates <UPDATES>
          Exit after printing this many payload messages

      --timeout <DURATION>
          Exit if this duration elapses before the requested updates arrive (e.g. 2s, 500ms)

      --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 hyperliquid watch fundings --help
      Show options for this command without signing, submitting, or changing state.

Example Commands

bullpen hyperliquid watch fundings [OPTIONS]
bullpen hyperliquid watch fundings --help
bullpen hyperliquid watch fundings --output json

JSON Output

Contract: JSON Output Contract.

Streaming output emits one JSON document per event line. Each event follows the shared contract, including SIGPIPE-safe pipe behavior.

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
channel	string	no	Hyperliquid websocket channel name
data	object/array	no	Raw channel payload; shape varies by stream

Example

bullpen hyperliquid watch fundings --output json

{
  "channel": "allMids",
  "data": {
    "BTC": "109500.0",
    "ETH": "3890.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.