`bullpen hyperliquid subaccount transfer`¶

Last updated: July 13, 2026

Transfer USDC between the authenticated master account and its own subaccounts

Usage¶

bullpen hyperliquid subaccount transfer [OPTIONS] --from <FROM> --to <TO> --amount <AMOUNT>

Live Help¶

Transfer USDC between the authenticated master account and its own subaccounts

Usage: bullpen hyperliquid subaccount transfer [OPTIONS] --from <FROM> --to <TO> --amount <AMOUNT>

Options:
      --from <FROM>
          Source endpoint: `master` or one of the authenticated account's owned subaccount addresses

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

      --to <TO>
          Destination endpoint: `master` or one of the authenticated account's owned subaccount addresses

      --amount <AMOUNT>
          USDC amount to transfer

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

      --dry-run
          Show the planned transfer without signing or submitting

  -y, --yes
          Skip confirmation prompt

      --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:
  # Preview funding a Hyperliquid subaccount from the master account
  bullpen hyperliquid subaccount transfer --from master --to 0x2222222222222222222222222222222222222222 --amount 25 --dry-run

  # Preview USDC moving back from an owned subaccount to the master account
  bullpen hyperliquid subaccount transfer --from 0x2222222222222222222222222222222222222222 --to master --amount 25 --dry-run

  # Export the subaccount transfer dry-run as JSON
  bullpen hyperliquid subaccount transfer --from master --to 0x2222222222222222222222222222222222222222 --amount 25 --dry-run --output json

VALIDATION NOTE: The subaccount create/fund round-trip remains validation-gated;
  prefer existing-owned-subaccount funding validation when possible.

Example Commands¶

bullpen hyperliquid subaccount transfer --from master --to 0x2222222222222222222222222222222222222222 --amount 25 --dry-run
bullpen hyperliquid subaccount transfer --from 0x2222222222222222222222222222222222222222 --to master --amount 25 --dry-run
bullpen hyperliquid subaccount transfer --from master --to 0x2222222222222222222222222222222222222222 --amount 25 --dry-run --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	Mutation preview/report schema version when emitted
`kind`	string	yes	`hyperliquid_mutation_preview` for dry-run JSON
`action`	string	no	Always `subaccount-transfer`
`account`	string	no	Active Hyperliquid master account
`would_submit`	boolean	yes	False in dry-run output
`signature_requested`	boolean	yes	False in dry-run output
`exchange_request_submitted`	boolean	yes	False in dry-run output
`intent.transfer_source`	string	yes	`master` or owned source subaccount address
`intent.transfer_destination`	string	yes	`master` or owned destination subaccount address
`intent.transfer_token`	string	yes	Hyperliquid token string such as `USDC:<tokenId>`

Example¶

Example JSON output

bullpen hyperliquid subaccount transfer --from master --to 0x2222222222222222222222222222222222222222 --amount 25 --dry-run --output json

{
  "schema_version": 1,
  "kind": "hyperliquid_mutation_preview",
  "action": "subaccount-transfer",
  "account": "0x1111111111111111111111111111111111111111",
  "scope": "primary 0x1111111111111111111111111111111111111111",
  "coin": null,
  "would_submit": false,
  "signature_requested": false,
  "exchange_request_submitted": false,
  "summary": "Preview only - no signature requested and no Hyperliquid exchange request submitted. Planned transfer of 25 USDC from master to 0x2222222222222222222222222222222222222222.",
  "intent": {
    "action": "subaccount-transfer",
    "account": "0x1111111111111111111111111111111111111111",
    "amount_usd": 25.0,
    "subaccount_address": "0x2222222222222222222222222222222222222222",
    "transfer_source": "master",
    "transfer_destination": "0x2222222222222222222222222222222222222222",
    "transfer_token": "USDC:0x00000000000000000000000000000000",
    "reduce_only": false,
    "builder_fee_bps": 0.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.

bullpen hyperliquid subaccount transfer¶