Polymarket Elon Tweets
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a real-money trading bot that discloses its main purpose, but its risk/profit wording and safety-setting metadata are inconsistent enough that a user should review it carefully before live use.
Do not run with --live or enable cron until you understand that this strategy can lose money, verify the actual risk-control settings used by the script, and use only a dedicated low-balance wallet/API key you are comfortable exposing to this trading workflow.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A user could believe the strategy is structurally covered when it can still lose money if the projection is wrong.
The skill buys only the projected center bucket plus configurable neighbors; the actual tweet count can resolve outside that selected cluster, so the quoted wording can make the trade sound safer or more guaranteed than it is.
**One bucket pays $1** — When the event resolves, one of your buckets pays $1, covering costs
State clearly that live trades can lose the full stake when the winning bucket is outside the purchased range, and require explicit user acknowledgement before live trading.
A user may set trading limits in the ClawHub UI and believe exposure, trade count, exit, or slippage settings are enforced when the script may ignore or misinterpret them.
These executable risk-control env vars differ from clawhub.json tunables such as SIMMER_ELON_MAX_POSITION_USD, SIMMER_ELON_MAX_TRADES_PER_RUN, SIMMER_ELON_EXIT_THRESHOLD, and SIMMER_ELON_SLIPPAGE_BPS; bucket_spread also has a numeric range/default in metadata that does not match the script's integer bucket count.
"max_position_usd": {"env": "SIMMER_ELON_MAX_POSITION", "default": 5.00, "type": float}, ... "max_trades_per_run": {"env": "SIMMER_ELON_MAX_TRADES", "default": 6, "type": int}Align the ClawHub tunable env vars, units, defaults, and ranges with the script/config.json before using live trading.
Anyone or any code with these credentials may be able to access trading information or place/sign trades depending on the account setup.
The skill needs trading account access and possibly a wallet private key to sign live orders; this is expected for its purpose but is high-impact authority.
Ask for Simmer API key ... Store in environment as `SIMMER_API_KEY` ... Ask for wallet private key (required for live trading) ... Store in environment as `WALLET_PRIVATE_KEY`
Use a dedicated low-balance trading wallet/API key, avoid pasting private keys into chat, and rotate/revoke credentials if exposed.
A future or compromised dependency version could affect trade execution or credential handling.
The skill depends on an external SDK version range that may receive future updates; this is normal for an integration but relevant because the SDK handles trading and credentials.
"pip": ["simmer-sdk>=0.11.1"]
Pin and review the SDK version in controlled deployments, especially before providing wallet credentials.
If enabled, the bot may keep placing trades on a schedule with minimal output.
The skill discloses recurring quiet live operation as an option, while also saying scheduling is disabled by default.
Set up cron (disabled by default — user must enable scheduling) ... python elon_tweets.py --live --quiet
Only enable cron after dry runs, set conservative limits, and monitor positions and open orders.