bullpen hyperliquid withdraw¶
Last updated: May 29, 2026
Withdraw USDC from Hyperliquid to the authenticated signer wallet (requires hyperliquid_trading feature)
Usage¶
Live Help¶
Withdraw USDC from Hyperliquid to the authenticated signer wallet (requires hyperliquid_trading feature)
Usage: bullpen hyperliquid withdraw [OPTIONS] --amount <AMOUNT> [DESTINATION]
Arguments:
[DESTINATION]
Destination L1 address to preview. Live withdrawals currently use the authenticated signer wallet
Options:
--amount <AMOUNT>
USD amount to withdraw
--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]
-y, --yes
Skip confirmation prompt
--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 withdrawal without signing or submitting
--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 withdraw --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen hyperliquid withdraw [OPTIONS] --amount <AMOUNT> [DESTINATION]
bullpen hyperliquid withdraw --help
bullpen hyperliquid withdraw --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.