PolicyMint

Autonomous trading agents have historically chosen between two failure modes: execute freely with no guardrails (high-performance, high-risk), or sit behind policy engines that never actually trade (safe but inert). This gap is quantifiable — H1 2025 crypto theft alone reached $3.01 billion. PolicyMint closes both sides of the problem: it trades actively while proving every risk decision on-chain through the ERC-8004 Validation Registry, making institutional-grade safe execution achievable for the first time. How the Policy Engine Works Before every trade execution, PolicyMint runs a mandatory pre-flight evaluation against three core policy rules: Spend Cap — Per-transaction USD limit capped at ≤ $450 to stay below the RiskRouter's $500 hard ceiling Venue Allowlist — Only whitelisted trading venues (e.g., kraken-spot, uniswap-v3) are permitted to receive orders Daily Loss Budget — Cumulative drawdown tracked in real time; agent halts when the daily loss threshold (≤ 4% of capital) is breached Every trade intent is structured as an EIP-712 typed-data payload, cryptographically signed with the agent wallet, and bound to Ethereum Sepolia (chainId 11155111) via EIP-155. If the policy engine returns allow, the signed intent becomes the execution proof submitted to the ERC-8004 RiskRouter. If the engine returns block, the Kraken CLI call never fires and a human-readable block reason is logged.