Security — 9 bots

Wallet, signing, RPC, contract-address safety

Security bots are cross-cutting guards that wrap every wallet interaction, signing request, RPC call, and contract address lookup. They run before and around the Execution layer — validating EIP-712 domains, previewing signature contents, managing RPC failover, and guarding wallet permissions. Security bots can reject or pause signing but cannot propose trades.

Pipeline position: Cross-cutting — wraps all signing and contract calls · This family does NOT propose or execute trades; only guards signing and wallet operations

Total bots

Frozen

Demo-wired

Production-live

Spotlight bots

ContractAddressGuard

sec.contractaddressguard

ContractAddressGuard refuses to allow a signature or on-chain submission against any contract address that is not present on the committed CLOB V2 all

SessionKeyManager

sec.sessionkeymanager

Issue, scope, and expire short-lived session keys so strategies can sign without re-prompting on every order.

WalletPermissionGuard

sec.walletpermissionguard

Enforce that each strategy can only call the wallet methods the user has explicitly granted, scoped per session.

All Security bots

Bot	Class	Authority	Status	Readiness	Purpose
AllowanceMonitor sec.allowancemonitor	Guardrail	Reject, Pause	planned	Spec started	Track ERC-20 allowances per token and contract; alert and shrink to a tight ceiling on idle.
ChainStateVerifier sec.chainstateverifier	Guardrail	Reject, Pause	planned	Spec started	Cross-check every order’s chain-derived inputs (nonce, balance, allowance) against multiple sources before signing.
ContractAddressGuard sec.contractaddressguard	Guardrail	Reject, Pause	planned	Ready to build	ContractAddressGuard refuses to allow a signature or on-chain submission against any contract address that is not present on the committed CLOB V2 all
KeyRotationReminder sec.keyrotationreminder	Guardrail	Reject, Pause	planned	Spec started	Nag the user to rotate signing keys on a schedule; prevent key reuse across environments.
RPCFailoverManager sec.rpcfailovermanager	Guardrail	Reject, Pause	planned	Spec started	Probe RPC providers continuously and fail over before a stale endpoint poisons our chain view.
SessionKeyManager sec.sessionkeymanager	Guardrail	Reject, Pause	planned	Spec started	Issue, scope, and expire short-lived session keys so strategies can sign without re-prompting on every order.
SignaturePreviewer sec.signaturepreviewer	Guardrail	Reject, Pause	planned	Spec started	Render a plain-English summary of every EIP-712 signature before the wallet shows the modal.
WalletFundingGuard sec.wallet_funding_guard	Guardrail	Reject	planned	Spec ready	Rejects any OrderIntent whose required pUSD collateral cannot be covered by the funded balance of the assigned wallet, including a configurable buffer
WalletPermissionGuard sec.walletpermissionguard	Guardrail	Reject, Pause	planned	Spec started	Enforce that each strategy can only call the wallet methods the user has explicitly granted, scoped per session.

Why this matters

Understanding which family a bot belongs to is the first step to understanding what it can and cannot do. Security bots does NOT propose or execute trades; only guards signing and wallet operations — this boundary is enforced in code and visible in every bot's authority chips.

Polytraders Operator UX Mock · INTERNAL · demo-wired ≠ production-live · the plan · reason codes · shadow-mode pipeline