PolyClawster

Trade on Polymarket prediction markets. Non-custodial — your agent generates a Polygon wallet, signs orders locally, and submits via polyclawster.com relay (...

What to check before installing: - Review scripts/setup.js (not fully shown) to ensure it does not exfiltrate the private key or upload secrets to polyclawster.com during registration. The README claims the private key never leaves your machine, but you must verify the code path that registers the agent. - Inspect ~/.polyclawster/config.json after setup to confirm privateKey and API secrets remain local and have safe permissions (chmod 600). - Run the skill in demo/dry-run mode first (auto.js --demo or --dry-run) and test with the $10 demo balance before risking real funds. - Review on‑chain approvals: approve.js sets infinite allowances (MaxUint256) and setApprovalForAll for several operator addresses (including a 'Neg Risk Adapter'); infinite approvals are common but increase risk if the approved contract is malicious — verify the spender addresses and audit/confirm Polymarket/adapter contracts yourself. - Verify polyclawster.com is a trustworthy relay (look up project, code repo, and operators). The relay sees signed orders and agent metadata; if you don't trust the relay you can still trade directly but may need to adapt the scripts. - Audit npm dependencies (ethers, @polymarket/clob-client and their transitive deps) or run in an isolated environment. Prefer running the code in a disposable VM or container while evaluating. - Because the agent can be scheduled to trade autonomously, restrict its runtime (limit cron/agent permissions, monitoring, loss limits) until you are comfortable with behavior. If you want, I can: (a) scan the omitted setup.js for suspicious behavior if you paste it, (b) list the specific on‑chain addresses the code approves so you can look them up, or (c) suggest safe steps to sandbox and test this skill.

Type: OpenClaw Skill Name: polyclawster Version: 1.5.0 The bundle implements a non-custodial Polymarket trading agent that generates and stores a Polygon private key locally in `~/.polyclawster/config.json`. While the scripts (`setup.js`, `trade.js`, `sell.js`) use local EIP-712 signing to ensure the private key is never transmitted, the architecture relies heavily on a third-party relay (`polyclawster.com`) for geo-bypass and trading signals (`auto.js`). Although the behavior is clearly aligned with the stated purpose and includes security best practices like `chmod 600` for the config file, the inherent risks of local plaintext key management and the dependency on an external relay for transaction execution qualify it as suspicious under the provided criteria.