controller-sessions

What problem does it solve?

Controller sessions and policies remove the need for repeated transaction approvals by configuring pre-approved session keys and granular policies, enabling seamless gasless or paymaster-backed transactions for end users and automated flows.

Core Features & Use Cases

• Policy Definitions: Define which contracts and entrypoints your app can call, including human-friendly names and descriptions for user approval flows.
• Spending Limits & Approvals: Configure token spending limits for approve-style methods, with support for max uint limits and USD price visibility when available.
• Signed Message Policies & Verified Sessions: Pre-approve typed message schemas and submit configs for verification to streamline trust and UX.
• Error Handling & UX Modes: Choose modal, notification, or silent error display modes and opt into error propagation for custom handling.
• Use Case: Mobile dApps and web games can create sessions at login that allow the frontend to execute frequent contract calls and signed messages without interrupting the user for each transaction.

Quick Start

Configure your SessionPolicies object with the required contracts, methods, and message schemas, then initialize Controller or SessionConnector with those policies so users can approve a session once and execute pre-approved transactions thereafter.