Simmer Wallet Setup

AdvisoryAudited by Static analysis on May 12, 2026.

Overview

No suspicious patterns detected.

Findings (0)

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.

What this means

If followed too broadly, an agent could gain the ability to approve spending and place real-money trades with less user review than expected.

Why it was flagged

The documented flow enables signing and broadcasting financial approvals and later API-only trades without showing approval limits, revocation steps, or an explicit human confirmation gate.

Skill content
`client.set_approvals()  # one-time per chain — signs locally via OWS, fully headless` ... `After both run once, all trading is API-only.`
Recommendation

Before running these calls, confirm exact approval scopes and amounts, use OWS policy caps and allowlists, and require explicit user confirmation for wallet registration, approvals, and trades.

What this means

A compromised installer or package could affect the local wallet environment and potentially access sensitive wallet material.

Why it was flagged

The wallet setup depends on downloading and executing remote installer/package code without a pinned version, checksum, or reviewed source in the provided artifacts.

Skill content
`curl -fsSL https://docs.openwallet.sh/install.sh | bash` ... `pip install 'simmer-sdk[ows]'`
Recommendation

Verify the OWS installer and Simmer SDK provenance, prefer pinned versions/checksums, and consider installing in a clean environment before funding the wallet.

What this means

Anyone or any process with these secrets may be able to access Simmer account functions or sign wallet actions.

Why it was flagged

The skill discloses that it uses a Simmer API key and may use a raw wallet private key; this is expected for a self-custody wallet setup but is highly sensitive authority.

Skill content
`primaryEnv: SIMMER_API_KEY` ... `WALLET_PRIVATE_KEY` ... `Polygon EVM private key. Set only if you chose Path B (external raw key).`
Recommendation

Prefer the OWS vault path over raw private keys, keep secrets out of chat/logs, use least-privilege API keys where available, and rotate/revoke keys if exposure is suspected.