bullpen funds preview-deposit¶
Last updated: July 13, 2026
Validate a token/chain/recipient deposit intent without moving funds
Usage¶
Live Help¶
Validate a token/chain/recipient deposit intent without moving funds
Usage: bullpen funds preview-deposit [OPTIONS] --token <TOKEN> --chain <CHAIN> --to <0xADDRESS>
Options:
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--token <TOKEN>
Token you intend to send
[possible values: usdc, usdc-e, pusd, usdt]
--chain <CHAIN>
Source chain you intend to send from
[possible values: polygon, arbitrum, ethereum, base, optimism]
--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.
--to <0xADDRESS>
Recipient address you intend to send to
--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 an Arbitrum USDC deposit intent for a placeholder recipient
bullpen funds preview-deposit --token usdc --chain arbitrum --to 0x1111111111111111111111111111111111111111
# Export the same deposit preview as JSON
bullpen funds preview-deposit --token usdc --chain arbitrum --to 0x1111111111111111111111111111111111111111 --output json
Example Commands¶
bullpen funds preview-deposit --token usdc --chain arbitrum --to 0x1111111111111111111111111111111111111111
bullpen funds preview-deposit --token usdc --chain arbitrum --to 0x1111111111111111111111111111111111111111 --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.