📦 Simmer Wallet Setup — Simmer Wallet 设置

Simmer Wallet 设置up

Self-custody wallet 设置up for an 代理 that 签名s its own real-money trades on Polymarket or Kalshi. Two paths:

Mode Who 签名s When to choose OWS per-代理 (recommended) Local OWS vault, 加密ed at rest Per-代理 isolation, multi-chAIn, policy-gated 签名ing. AvAIlable for Polymarket + Kalshi. External raw key Local SDK with WALLET_PRIVATE_KEY env Existing 设置ups. Fully supported; OWS is recommended for new 代理s.

Already on a managed wallet? You don't need this 技能. Managed 设置up is a one-time 仪表盘 action — go to simmer.markets/仪表盘, connect a Polygon wallet, 应用rove the contracts, and the Simmer server 签名s trades within those 应用roval bounds. No 代理-side 设置up required.

Path A — OWS per-代理 wallet (recommended)

OWS = Open Wallet Standard. Local-first 加密ed vault, multi-chAIn, policy engine, 代理-scoped API keys. The private key never leaves the local machine.

One-time 设置up # 安装 OWS 命令行工具 curl -fsSL https://docs.openwallet.sh/安装.sh | bash pip 安装 open-wallet-standard

# 创建 a wallet for this 代理 ows wallet 创建 --name "my-代理-wallet" # Stores at ~/.ows/wallets/, derives 添加resses for EVM (Polygon), Solana, etc.

# Fund it — show the EVM 添加ress to the human, they bridge USDC.e to Polygon ows wallet show my-代理-wallet

Register the wallet with Simmer from simmer_sdk 导入 Simmer命令行工具ent 命令行工具ent = Simmer命令行工具ent( API_key="sk_live_...", ows_wallet="my-代理-wallet", # name from ows wallet 创建 )

命令行工具ent.register_代理_wallet() # one-time, Elite-tier gated 命令行工具ent.设置_应用rovals() # one-time per chAIn (签名ed via OWS)

⚠️ 设置up requires a 仪表盘 会话. register_代理_wallet() and 设置_应用rovals() use the browser auth from simmer.markets/仪表盘 in 添加ition to the API key — they don't work from a fully headless cron. 运行 them once after 记录ging in. Trading is API-only after that.

(Alternative: 设置 OWS_WALLET=my-代理-wallet in the 环境 and pass only API_key — the SDK auto-检测s.)

Trade — same API, OWS 路由s the 签名ing 结果 = 命令行工具ent.trade( market_id, "yes", 10.0, venue="polymarket", reasoning="..." ) # SDK builds the order, OWS 签名s locally, broadcast goes through Simmer

For Kalshi (Solana)

OWS is multi-chAIn. The same wallet has a Solana account derived automatically.

ows wallet show my-代理-wallet # shows Solana 添加ress too # Fund with SOL + USDC, complete KYC at dflow.net/proof

命令行工具ent = Simmer命令行工具ent( API_key="sk_live_...", ows_wallet="my-代理-wallet", venue="kalshi", ) 命令行工具ent.trade(market_id, "yes", 5.0, reasoning="...")

No SOLANA_PRIVATE_KEY env var needed — OWS handles 签名ing through the same vault.

What OWS gives over raw keys 加密ed at rest (AES-256-GCM, scrypt KDF). Private key only 解密ed in-process for 签名ing, then wiped. Policy engine — chAIn allow列出s, dAIly caps, contract allow列出s. Optional. Multi-chAIn — same vault, every chAIn Simmer supports. Per-代理 isolation — separate wallets per 代理 for 清理 P&L attribution. 代理 API keys with bounded 访问 (revocable, expiring). Path B — External raw key

Fully supported path for self-custody with an existing wallet. New 代理s should consider OWS first — same self-custody guarantee, 加密ed at rest, multi-chAIn, and easier to layer policy controls. Raw-key flow stays supported for users who already have it 设置 up.

设置 the key in the 环境, then construct the 命令行工具ent:

导出 WALLET_PRIVATE_KEY="0x..." # Polymarket Polygon wallet

命令行工具ent = Simmer命令行工具ent(API_key="sk_live_...") # private_key is auto-检测ed from WALLET_PRIVATE_KEY env var 命令行工具ent.link_wallet() 命令行工具ent.设置_应用rovals()

⚠️ link_wallet() and 设置_应用rovals() need a 仪表盘 会话 — they use the browser auth from simmer.markets/仪表盘, not the SDK API key. 运行 them once from a 记录ged-in 仪表盘, not a headless script. After that, the rest of the 代理 运行s API-only.

Migrating to OWS when ready

No rush. When ready, 导入 the existing key into OWS and switch over:

ows wallet 导入 --name "my-代理-wallet" --private-key "$WALLET_PRIVATE_KEY" un设置 WALLET_PRIVATE_KEY # OWS handles 签名ing from here

Then in the 代理 code:

命令行工具ent = Simmer命令行工具ent(API_key="sk_live_...", ows_wallet="my-代理-wallet") # Same trade() / 设置_应用rovals() / redeem() API — OWS 路由s the 签名ing

The same wallet 添加ress is preserved, so existing positions and 应用rovals carry over.

Polymarket 令牌 note

Polymarket trades agAInst whatever collateral 令牌 Polymarket currently uses for its CLOB (currently pUSD, the V2 collateral). The 仪表盘 at simmer.markets/仪表盘 shows what the wallet needs and walks through 设置up. Watch for the V2 era banner at the top — it's the entry point.

First-time activation (new users with no prior Polymarket activity): the 仪表盘 prompts a USDC → pUSD wrap plus a one-time 应用roval sequence (~8 签名atures total). Total ~30 seconds of 命令行工具cks and ~$0.20 in gas.

Existing Polymarket users with USDC.e from b