PolyShark
PolyShark is the ERC-7715-powered autopilot that turns Polymarket mispricing into safe, low-latency yield
视频
描述
Architecture
PolyShark’s architecture flow starts from the user’s MetaMask Smart Account and pushes all trading authority into a dedicated session account that is constrained by ERC-7715 permissions. This account signs arbitrage transactions only within the bounds of a predefined spend limit and scope, ensuring that every on-chain action can be traced back to a cryptographically enforced permission rather than blind trust in off-chain code
Before vs After
The “before vs after” UX shift is driven by moving from per-transaction approvals to a single, human-readable permission grant that can be reused across thousands of trades. Traditional DeFi bots force users to spam-confirm transactions or hand over unlimited allowances, whereas PolyShark uses ERC-7715 to offer clear limits such as “10 USDC per day on Polymarket” and then automates everything else without additional popups
ERC-7715
The ERC-7715 permission lifecycle in PolyShark mirrors the standard flow of setting up a session account, requesting granular permissions, redeeming them through actual trades, monitoring usage, and finally revoking when desired. The dashboard surfaces this lifecycle in real time so users can see current allowance, remaining budget, and agent status, making abstract permission concepts tangible and understandable
Strategy
Strategy modes map the remaining budget to different risk profiles, allowing PolyShark to behave aggressively when most of the daily allowance is untouched and conservatively as the cap approaches. This budget-aware behavior turns permissions into a live input for the trading engine, so that the agent naturally throttles itself instead of abruptly failing when limits are hit
Safety
Safety architecture layers Envio latency checks, failure backoff, and permission fallbacks to ensure the agent prefers “do nothing” over acting on stale or incomplete information. If data becomes slow or permission queries fail, PolyShark assumes zero allowance and transitions into safe or halted states, aligning with best practices for high-throughput, real-time indexers like Envio HyperIndex