bullpen polymarket sweep-signer-eoa¶
Last updated: July 13, 2026
Sweep USDC held directly on a signer EOA into your active Polymarket wallet.
Usage¶
Live Help¶
Sweep USDC held directly on a signer EOA into your active Polymarket wallet.
Use this when native USDC, USDC.e, or pUSD was sent to your owner signer address instead of your Polymarket Safe/Proxy or Deposit Wallet. The command probes the signer EOA and transfers any nonzero balances to the active Polymarket wallet with direct EOA-signed ERC-20 transfers.
Direct EOA transfers require the signer EOA to hold POL/MATIC for gas.
Usage: bullpen polymarket sweep-signer-eoa [OPTIONS]
Options:
--from <ADDRESS>
Source signer EOA (0x-prefixed owner address). Defaults to the active signer EOA
--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.
--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:
# Open the signer-EOA sweep confirmation flow
bullpen polymarket sweep-signer-eoa
# Probe and sweep from a specific owner signer EOA
bullpen polymarket sweep-signer-eoa --from 0xYourOwnerEOA
# Execute after reviewing detected balances and gas requirements
bullpen polymarket sweep-signer-eoa --yes
NOTES:
There is no separate --preview flag. The command authenticates, resolves the
server-selected destination, probes signer-EOA balances and gas, prints the
sweep summary, and then prompts before direct EOA-signed transfers.
Example Commands¶
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.