bullpen polymarket redeem-status

Last updated: August 26, 2026

Inspect a previous redeem operation without resubmitting it

Usage

bullpen polymarket redeem-status [OPTIONS] <OPERATION_ID>

Live Help

Inspect a previous redeem operation without resubmitting it

Usage: bullpen polymarket redeem-status [OPTIONS] <OPERATION_ID>

Arguments:
  <OPERATION_ID>
          Full operation ID, raw tx hash, or exact trace ID printed by a previous redeem

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

      --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:
  # Inspect a stored redeem operation
  bullpen polymarket redeem-status redeem-v1-tx-0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890

  # Export the same reconciliation state as JSON
  bullpen polymarket redeem-status trace-123 --output json

Example Commands

bullpen polymarket redeem-status redeem-v1-tx-0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890
bullpen polymarket redeem-status trace-123 --output json
bullpen polymarket redeem-status redeem-v1-tx-0xabc123 --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
operation_id	string	no	Stable redeem operation ID recorded after submit
transaction_state	string	no	Settlement transaction state: confirmed, reverted, or pending_unknown
value_state	string	no	Value classification such as confirmed_positive_payout, confirmed_zero_payout, wrong_wallet_settlement, pending_unknown, or contradictory_evidence
resolution_owner	string	no	Owner of the next resolution step: user, bullpen_support, polymarket_indexing, polymarket_relayer, or unknown
next_action	string	no	Support-safe instruction for the current evidence state
safe_to_retry	boolean	no	Always false; this command never authorizes replaying a submitted redeem
record	object	no	Stored redeem record plus latest live evidence refresh
record.latest_refresh	object	yes	Latest receipt, balance, indexed portfolio, order credit, payout-event, and selected-wallet evidence

Example

Example JSON output

bullpen polymarket redeem-status redeem-v1-tx-0xabc123 --output json

{
  "operation_id": "redeem-v1-tx-0xabc123",
  "transaction_state": "confirmed",
  "value_state": "confirmed_positive_payout",
  "resolution_owner": "user",
  "next_action": "No retry is needed; settlement has durable wallet balance and corroborating evidence.",
  "safe_to_retry": false,
  "record": {
    "operation_id": "redeem-v1-tx-0xabc123",
    "wallet": {
      "owner_eoa": "0x1111111111111111111111111111111111111111",
      "payout_wallet": "0x2222222222222222222222222222222222222222",
      "selected_wallet": "0x2222222222222222222222222222222222222222",
      "selected_state": "selected"
    },
    "receipt": {
      "tx_hash": "0xabc123",
      "relayer_trace_id": "trace-123",
      "receipt_status": "confirmed"
    },
    "latest_refresh": {
      "tx_receipt": {
        "receipt_status": "confirmed"
      },
      "payout_wallet_collateral": {
        "value": "15.000000",
        "source": "polygon_rpc"
      },
      "indexed_portfolio_value": {
        "value": null,
        "error": {
          "code": "redeem_status.indexed_portfolio_probe_failed"
        }
      },
      "payout_event": {
        "present": true,
        "amount": "5.000000"
      },
      "selected_wallet": {
        "value": "0x2222222222222222222222222222222222222222"
      }
    }
  }
}

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.