bullpen hyperliquid deposit¶
Last updated: May 29, 2026
Deposit USDC from Arbitrum into Hyperliquid Spot.
Usage¶
Live Help¶
Deposit USDC from Arbitrum into Hyperliquid Spot.
Bridges native USDC from your Bullpen-managed Arbitrum wallet into Hyperliquid Spot for perps trading. Requires native USDC on Arbitrum (not USDC.e). Hyperliquid minimum deposit: $5.
Usage: bullpen hyperliquid deposit [OPTIONS] --amount <AMOUNT>
Options:
--from <FROM>
Source chain to bridge from. Currently only `arbitrum` is supported
[default: arbitrum]
--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]
--amount <AMOUNT>
USD amount to bridge (e.g. `5.00`). Must be ≥ $5 (Hyperliquid minimum)
--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.
-y, --yes
Skip confirmation prompt. Required for non-interactive use; this command moves real funds and `BULLPEN_NON_INTERACTIVE` does NOT imply consent
--dry-run
Show the planned transaction without submitting. Useful for sanity checks before paying gas
--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 deposit --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen hyperliquid deposit [OPTIONS] --amount <AMOUNT>
bullpen hyperliquid deposit --help
bullpen hyperliquid 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.