bullpen hyperliquid scale

Last updated: May 29, 2026

Place a multi-level Hyperliquid limit ladder in one signed action

Usage

bullpen hyperliquid scale [OPTIONS] --side <SIDE> --start <START> --end <END> --levels <LEVELS> <COIN>

Live Help

Place a multi-level Hyperliquid limit ladder in one signed action

Usage: bullpen hyperliquid scale [OPTIONS] --side <SIDE> --start <START> --end <END> --levels <LEVELS> <COIN>

Arguments:
  <COIN>
          Coin/market (e.g. "ETH", "BTC")

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

      --side <SIDE>
          Direction of the ladder

          Possible values:
          - long:  Build a buy ladder that opens or increases a long
          - short: Build a sell ladder that opens or increases a short

      --env <ENV>
          Target environment to connect to (overrides config.toml)

          [env: BULLPEN_ENV=]
          [possible values: staging, production]

      --notional <NOTIONAL>
          Total USD notional to distribute across the ladder

      --base-size <BASE_SIZE>
          Total base-token size to distribute across the ladder

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

      --start <START>
          First limit price in the ladder

      --end <END>
          Final limit price in the ladder

      --levels <LEVELS>
          Number of limit levels to place

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

      --skew <SKEW>
          Linear size skew from start to end. 1.0 is uniform; values below 1 taper down

          [default: 1]

      --reduce-only
          Mark every level reduce-only

      --tif <TIF>
          Time-in-force for every scale level

          Possible values:
          - gtc: Good-till-cancelled: rests on the book until explicitly cancelled
          - ioc: Immediate-or-cancel: fills what it can immediately and cancels the rest
          - alo: Add-liquidity-only: post-only, rejects if it would cross the spread

          [default: gtc]

      --leverage <LEVERAGE>
          Leverage to set before placing a non-reduce-only ladder

      --subaccount <SUBACCOUNT>
          Target a Hyperliquid subaccount. Hyperliquid still signs with the authenticated primary account

      --vault <VAULT>
          Target a Hyperliquid vault. Hyperliquid still signs with the authenticated primary account

  -y, --yes
          Skip confirmation prompt

      --preview
          Show the planned ladder without signing or submitting

  -h, --help
          Print help (see a summary with '-h')

EXAMPLES:
  bullpen hyperliquid scale --help
      Show options for this command without signing, submitting, or changing state.

Example Commands

bullpen hyperliquid scale [OPTIONS] --side <SIDE> --start <START> --end <END> --levels <LEVELS> <COIN>
bullpen hyperliquid scale --help
bullpen hyperliquid scale --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.