Account Abstraction
Smart-account infrastructure for configurable signing, sponsorship, recovery, permissions, and transaction-policy workflows on supported EVM deployments.
- What it is
- Smart-account component
- Current posture
- Available for supported deployments
- What varies
- Architecture, providers, operating scope, and commitments
Private-key handling is not an institutional authority model.
Products need to express who may act, through which signer, under which limits, with which recovery path, and who pays transaction fees. Account abstraction moves those decisions into configurable smart-account and service workflows.
Keep the core authoritative.
- Enterprise identity
- Signing and custody
- Product workflows
Change the capability at a controlled boundary.
Account Abstraction changes the boundary, not the institution’s authority.
Product-shaped authority
Represent configured users, teams, services, and agents through explicit signing and transaction policies.
Recoverable access
Design supported recovery, rotation, MFA, guardian, or administrative workflows for the custody model.
Controlled transaction experience
Apply sponsorship, limits, permissions, batching, and application rules with visible dependencies.
What Account Abstraction contributes. What still needs a decision.
Smart accounts
Deploy supported account contracts and document upgrade, administrator, and ownership behaviour.
Signing policy
Configure signer roles, thresholds, permissions, sessions, limits, and transaction rules.
Fee sponsorship
Define which transactions may be sponsored, by whom, under which policy and budget.
Recovery
Integrate supported recovery, rotation, guardian, MFA, or administrative processes.
Application integration
Connect supported wallets, custody systems, identity, bundlers, paymasters, and product workflows.
Operations
Scope monitoring, failures, upgrades, incidents, support, and service responsibilities.
Continue from Account Abstraction into the operating model.
Bring the requirement. Define the Account Abstraction boundary.
A focused workshop maps the target capability, existing systems, providers, controls, and deployment variables.