polymarket-btc-up-down-trader — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited polymarket-btc-up-down-trader (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Trade Polymarket's BTC daily and weekly UP/DOWN markets with built-in exit discipline. Enters on Binance momentum signals, exits automatically before resolution tail risk bites.
🚨 Framework, not a production trading system. Read DISCLAIMER.md before connecting to a wallet with real funds.
Polymarket only. All trades execute on Polymarket with real USDC. Use --live for real trades; default is dry run.Not for fast (5m/15m) markets. Use polymarket-fast-loop for those. This skill targets daily and weekly BTC direction markets with hours-to-days of duration.⚠️ BTC UP/DOWN markets carry Polymarket's crypto taker fee. Effective rate is 3.5% at 50¢, up to ~6.6% on cheap shares. Makers pay 0% and earn a 20% rebate from collected taker fees. Factor this into your minimum edge threshold.
This skill includes a built-in oracle-engineering risk detector (simmer_sdk.risk.OracleEngineeringDetector). It is enabled by default for all short-dated markets (≤ 5 minutes to resolution).
The gate fires a RESOLUTION_TAMPER_RISK halt when both signals diverge within the final 5 minutes of the resolution window:
When the gate fires:
risk_flag=oracle_engineeringThis is a defensive halt only. Do not use it as a buy signal or to copy the attacker's position. See simmer_sdk/risk/oracle_engineering.py for the full detector implementation and shared-knowledge/entities/concepts/oracle-engineering.md for threat-model background.
Use this skill when the user wants to:
pip install simmer-sdkexport SIMMER_API_KEY="your-key-here"export WALLET_PRIVATE_KEY="0x..." python strategy.py --config# Dry run — see what would happen
python strategy.py
# Go live
python strategy.py --live
# Monitor-only (check exits without new entries)
python strategy.py --live --monitor
# Quiet mode for cron
python strategy.py --live --quietLinux crontab:
# Every 30 minutes
*/30 * * * * cd /path/to/skill && python strategy.py --live --quietOpenClaw native cron:
openclaw cron add \
--name "BTC Up-Down Trader" \
--cron "*/30 * * * *" \
--session isolated \
--message "Run BTC up-down trader: cd /path/to/skill && python strategy.py --live --quiet"All settings configurable via config.json, environment variables, or --set:
python strategy.py --set exit_before_resolution_hours=2.0
python strategy.py --set volume_spike_exit_multiplier=4.0
python strategy.py --set target_hit_capture_pct=0.75| Setting | Default | Env Var | Description |
|---|---|---|---|
exit_before_resolution_hours | 1.0 | SIMMER_BTCUD_EXIT_BEFORE_RESOLUTION_HOURS | Close position this many hours before scheduled resolution. Disable with 0. |
volume_spike_exit_multiplier | 3.0 | SIMMER_BTCUD_VOLUME_SPIKE_MULTIPLIER | Exit when 10-minute CLOB volume hits N× the rolling baseline. Disable with 0. |
target_hit_capture_pct | 0.85 | SIMMER_BTCUD_TARGET_HIT_CAPTURE_PCT | Exit when position has captured 85% of the theoretical max gain. Disable with 0. |
volume_baseline_windows | 6 | SIMMER_BTCUD_VOLUME_BASELINE_WINDOWS | Number of prior 10-minute windows used to compute volume baseline. |
Why these defaults? Exit behavior on short-dated prediction markets skews heavily toward early exits — the final hours before resolution compress remaining upside while tail risk (last-minute reversals, oracle variance) stays constant. The defaults are calibrated to exit early while capturing the bulk of the move. Empirical work on short-dated crypto UP/DOWN exit patterns informed the calibration; adjust based on your own backtest results.
| Setting | Default | Env Var | Description |
|---|---|---|---|
entry_threshold | 0.05 | SIMMER_BTCUD_ENTRY_THRESHOLD | Min discount from 50¢ toward the momentum-opposing side. Entry only fires when the market disagrees with momentum: UP signal requires YES < 0.50 (edge = 0.50 − YES); DOWN signal requires YES > 0.50 (edge = YES − 0.50). Skips when market already agrees with momentum. |
min_momentum_pct | 0.3 | SIMMER_BTCUD_MOMENTUM_THRESHOLD | Min BTC % move (30-min lookback) to trigger |
max_position | 10.0 | SIMMER_BTCUD_MAX_POSITION_USD | Max $ per trade |
daily_budget | 50.0 | SIMMER_BTCUD_DAILY_BUDGET_USD | Max total entry spend per UTC day |
lookback_minutes | 30 | SIMMER_BTCUD_LOOKBACK_MINUTES | Lookback window for BTC momentum signal |
min_hours_to_resolution | 4.0 | SIMMER_BTCUD_MIN_HOURS_TO_RESOLUTION | Skip entry if market resolves in fewer than N hours |
{
"exit_before_resolution_hours": 1.0,
"volume_spike_exit_multiplier": 3.0,
"target_hit_capture_pct": 0.85,
"entry_threshold": 0.05,
"min_momentum_pct": 0.3,
"max_position": 10.0,
"daily_budget": 50.0
}Each run cycle evaluates open positions against three triggers, in priority order:
time_cap — Time-based exitCloses position when the market is within exit_before_resolution_hours of resolution.
hours_to_resolution ≤ exit_before_resolution_hours → EXIT (time_cap)This is the hard floor. Holding to settlement adds tail risk (oracle variance, thin liquidity, last-minute manipulation) with little remaining upside on a near-resolved market.
target_hit — Profit capture exitCloses position when it has captured target_hit_capture_pct of the theoretical maximum gain.
YES positions: (current_price - entry_price) / (1.0 - entry_price) ≥ 0.85 → EXIT (target_hit)
NO positions: (entry_price - current_price) / entry_price ≥ 0.85 → EXIT (target_hit)Example: Bought YES at $0.40. Maximum gain = 1.0 - 0.40 = $0.60/share. At $0.91, captured = (0.91 - 0.40) / 0.60 = 85% → exit.
volume_spike — Smart-money volume exitCloses position when 10-minute CLOB volume exceeds volume_spike_exit_multiplier× the rolling baseline.
current_10m_volume / avg_baseline_volume ≥ 3.0 → EXIT (volume_spike)A sudden surge in volume near resolution typically signals that informed traders have positioned ahead of outcome certainty. Exiting into the spike captures the liquidity premium.
Every exit logs one of four reasons:
| Reason | Trigger |
|---|---|
time_cap | Hours to resolution ≤ exit_before_resolution_hours |
target_hit | Captured ≥ target_hit_capture_pct of max gain |
volume_spike | 10m volume ≥ volume_spike_exit_multiplier × baseline |
manual | User-initiated close via dashboard or SDK |
python strategy.py # Dry run (show positions + opportunities)
python strategy.py --live # Execute real trades
python strategy.py --monitor # Only run exit checks (no new entries)
python strategy.py --positions # Show open positions
python strategy.py --config # Show current config
python strategy.py --set KEY=VALUE # Update config
python strategy.py --quiet # Only output on trades/errorsAll trades are tagged source: "sdk:btcupdown". This keeps BTC UP/DOWN P&L separate from other strategies in your Simmer portfolio.
"No active BTC UP/DOWN markets found"
"Could not fetch BTC momentum"
lookback_minutes or wait."Momentum X% < minimum Y%"
min_momentum_pct if too conservative.Volume spike trigger not firing
volume_baseline_windows lower or increase volume_spike_exit_multiplier."External wallet requires a pre-signed order"
WALLET_PRIVATE_KEY is not set. Export the private key for your Polymarket wallet."Balance shows $0 but I have funds on Polygon"
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.