Account Abstraction breaks indexers. Traditional indexers like The Graph or Covalent are built for Externally Owned Account (EOA) transactions, which are simple, atomic state changes. AA introduces UserOperations, Paymasters, and Bundlers, creating multi-step intent-based execution flows that these systems cannot natively query.
account-abstraction-fixing-crypto-ux
Blog
Why AA Demands a New Generation of Indexers and APIs
Account Abstraction breaks legacy indexing models. Querying state for smart accounts requires complex logic, creating a massive infrastructure gap and opportunity for new players like Goldsky and Airstack.
introduction
THE DATA GAP
Introduction
Account Abstraction's user-centric model breaks the transaction-centric data models of legacy indexers, creating a critical infrastructure gap.
The query model inverts. Legacy APIs ask 'what transactions did this address sign?'. For AA, the question is 'what user intents did this smart account fulfill?'. This requires tracking cross-contract dependencies between the EntryPoint, Bundler, and Paymaster within a single UserOperation.
Evidence: An ERC-4337 bundle on Polygon can involve a session key from Biconomy, gas sponsorship via a Paymaster like Stackup, and a token swap via UniswapX—a single user action that generates 5+ internal transactions. Existing indexers see noise; AA-native indexers see user intent.
key-trends
ACCOUNT ABSTRACTION'S DATA DEMANDS
The Data Gap: Why Legacy Indexers Fail
Legacy indexers, built for EOAs, cannot query the complex state and intent-driven interactions of smart accounts.
01
The Problem: EOA-Centric Data Models
Indexers like The Graph are optimized for msg.sender transactions, not smart account state. They fail to track:\n- UserOperation mempool status and lifecycle\n- Bundler & Paymaster dependencies\n- Session keys and their permissions
0%
AA Coverage
~500ms
Latency Spike
02
The Solution: Intent-Aware Indexing
New indexers must parse high-level intents, not just low-level logs. This requires tracking:\n- Cross-chain user journeys (e.g., UniswapX, Across)\n- Conditional transaction flows and their fulfillment\n- Aggregated gas sponsorship across Paymasters
10x
Query Complexity
Real-time
Intent State
03
The Problem: Static vs. Dynamic State
AA state is non-deterministic until bundling. Legacy APIs return stale data on:\n- Smart account balance (factoring in pending UserOperations)\n- Transaction simulation results with paymaster sponsorship\n- Fee market for bundler inclusion
5-10 blocks
State Lag
High
Revert Risk
04
The Solution: Real-Time Execution Graphs
Indexers must build live execution graphs connecting UserOperations, bundlers, and paymasters. This enables:\n- Predictive analytics for bundler selection\n- Atomic multi-op dependency resolution\n- Sub-second status updates for wallets
<1s
Status Latency
100%
Graph Coverage
05
The Problem: Missing Economic Layer
Legacy systems ignore the AA fee economy. Apps cannot query:\n- Paymaster profitability and sponsorship policies\n- Bundler competition and bid landscapes\n- Aggregate gas savings from batched ops
$0
Fee Visibility
N/A
Cost Optimization
06
The Solution: AA-Specific Query Language
New APIs require a query language for AA primitives, similar to how SQL abstracts databases. This allows for:\n- Intent-based search ("show all cross-chain swaps")\n- Economic queries ("most cost-effective paymaster")\n- Network health metrics (bundler decentralization score)
-70%
Dev Time
New Primitive
Query Standard
WHY AA DEMANDS NEW INFRASTRUCTURE
EOA vs. Smart Account: The Query Complexity Gap
Comparing the query patterns and data demands of traditional Externally Owned Accounts (EOAs) versus ERC-4337 Smart Accounts, illustrating the architectural shift required for indexers and RPC providers.
| Query Dimension | Legacy EOA | ERC-4337 Smart Account | Infrastructure Implication |
|---|---|---|---|
Primary Query Target | Single EOA Address | Multiple Contract Addresses (Factory, EntryPoint, Paymaster, Account) | Multi-entity graph traversal |
State Change Detection | Balance & nonce updates | UserOperation mempool, bundler actions, paymaster stake, account deployment | Event-driven monitoring across 4+ contracts |
Gas Sponsorship Tracking | None (user-pays) | Paymaster abstracted gas (session keys, subscriptions) | Real-time sponsorship logic & balance checks |
Transaction Atomicity | Single on-chain tx | UserOperation > Bundler > EntryPoint (multi-step, off-chain/on-chain) | Cross-layer state reconciliation |
Account Abstraction Features | None | Social recovery, batched txs, custom auth (e.g., WebAuthn) | Custom event schema indexing per wallet vendor |
RPC Call Complexity | eth_getBalance, eth_getTransactionCount | eth_estimateUserOperationGas, eth_getUserOperationByHash, debug_bundler_* | New method support, gas simulation overhead |
Latency Sensitivity | < 2 sec for tx broadcast | < 200 ms for UserOperation simulation & mempool acceptance | Sub-second simulation infra required |
Data Volume per UserOp | ~150 bytes (raw tx calldata) | ~500+ bytes (full UserOperation struct + signatures + paymaster data) | ~3.3x increase in data ingestion & storage |
deep-dive
THE DATA INFRASTRUCTURE SHIFT
The New Abstraction Layer: From State to Intent
Account Abstraction redefines user interaction, forcing indexers and APIs to evolve from tracking state to interpreting intent.
Account Abstraction redefines the query. Legacy indexers like The Graph track state changes from EOA transactions. AA's UserOperations (UserOps) and Paymaster sponsorship create a semantic gap between the user's declared intent and the final on-chain state.
Intent-based architectures demand new primitives. Systems like UniswapX and CowSwap separate intent expression from execution. Indexers must now parse signed intent messages, track fulfillment across Across or LayerZero, and verify outcomes—a fundamentally different data model.
The API surface becomes declarative. Developers no longer request 'transactions for address X'. They query for 'pending intents with status Y' or 'Paymaster gas sponsorship events'. This requires new indexing standards akin to ERC-4337 for the data layer.
Evidence: A single UniswapX order generates off-chain intents, on-chain settlements, and cross-chain fills—a multi-step state transition no single chain indexer can reconstruct. The new indexer stack must be intent-native.
protocol-spotlight
WHY AA DEMANDS A NEW GENERATION OF INDEXERS AND APIS
Building the New Stack: Emerging Players
Account Abstraction's shift to user-centric, session-based interactions breaks the fundamental assumptions of legacy blockchain data infrastructure.
01
The Problem: Legacy Indexers Are Blind to UserOps
Traditional indexers like The Graph are built for tracking contract events and wallet balances, not the intent-driven UserOperations at the core of AA. They cannot answer questions like 'What is the status of my batched transaction?' or 'Which paymaster sponsored this session?'
- Misses Key Data: UserOp mempool, bundler competition, and paymaster sponsorship flows are invisible.
- Latency Kills UX: Polling for receipt finality defeats the purpose of gas sponsorship and atomic batched actions.
0%
AA Coverage
~2s+
Status Latency
02
The Solution: UserOp-Centric Indexing (e.g., Stackup, Pimlico)
Emerging players are building indexers from the ground up for the ERC-4337 mempool, treating the UserOperation as the primary data entity. This enables real-time dashboards for bundlers and seamless APIs for wallets.
- Real-Time Mempool: Monitor pending UserOps, bundler inclusion, and paymaster policies with sub-500ms updates.
- Intent-Level Analytics: Track success rates, gas sponsorship costs, and bundler market share across chains.
100%
ERC-4337 Native
<500ms
Event Latency
03
The Problem: Wallets Can't Build on RPCs Alone
Generic JSON-RPC endpoints (Alchemy, Infura) expose low-level chain data, forcing every smart wallet developer to rebuild the same complex middleware for simulating UserOps, managing gas tokens, and tracking session keys.
- Reinventing the Wheel: Each team builds custom logic for paymaster estimation and batched transaction simulation.
- Fragmented State: Managing smart account state across multiple chains becomes a DevOps nightmare.
10k+
Dev Hours Wasted
High
Integration Risk
04
The Solution: AA-Specific APIs as a Service
Providers like Biconomy and Candide are abstracting the entire AA stack into unified APIs. Developers get a single endpoint for gasless transactions, sponsored gas, and batch simulations without managing bundlers or paymasters.
- Unified Abstraction: One API call handles gas estimation, sponsorship, and relay across any supported chain.
- Plug-and-Play Modules: Easily integrate session keys, social recovery, and fee logic without smart contract expertise.
1
API Endpoint
-70%
Dev Time
05
The Problem: Cross-Chain AA is a Data Black Box
A user's smart account activity is siloed per chain. There is no unified view of a cross-chain identity, its transaction history, or its aggregated gas sponsorship. This cripples portfolio apps, credit scoring, and cross-chain session management.
- No Portable Identity: Reputation, social graph, and transaction history don't follow the account across chains.
- Fragmented Liquidity: Paymasters and bundlers operate per-chain, forcing users to manage native gas tokens everywhere.
N/A
Cross-Chain View
10+
Gas Tokens Needed
06
The Solution: The Cross-Chain Smart Account Graph
The next frontier is indexing the smart account itself as a cross-chain entity. This requires stitching together data from AA indexers, intent-based bridges like LayerZero and Across, and generalized messaging layers.
- Unified Identity Graph: Map a single smart account's activity, assets, and reputation across all EVM and non-EVM chains.
- Aggregated Gas Economics: Enable cross-chain paymasters and provide analytics on total gas sponsored per user.
360°
Account View
1
Gas Currency
counter-argument
THE INFRASTRUCTURE GAP
The Bear Case: Is This Just a Niche Problem?
Account abstraction's core promise of user-centric design breaks the fundamental assumptions of existing blockchain data infrastructure.
The indexing problem is structural. Existing indexers like The Graph or Covalent are built for EOAs, tracking msg.sender. AA's modular signature validation and delegated transaction flow shatter this model, requiring a new abstraction layer to map user intents to on-chain actions.
This creates a data black box. Wallets like Safe or Biconomy generate complex, nested UserOperation calldata. Standard RPC endpoints from Alchemy or Infura cannot parse this to answer a simple question: 'What did this user do?'
The API surface explodes. Developers need queries for paymaster sponsorship status, signature aggregation proofs, and batch transaction dependencies. This is a different paradigm from simple balance or transfer lookups.
Evidence: A single Safe smart wallet recovery can involve 10+ signatures across 5 sessions. No current indexer tracks this as a single user-governed action, only as disparate contract calls.
takeaways
WHY AA DEMANDS NEW INFRASTRUCTURE
TL;DR for Builders and Investors
Account Abstraction shifts execution logic from the protocol to the user, breaking the assumptions of today's indexers and APIs.
01
The Problem: Legacy Indexers Are Blind to UserOps
Traditional indexers like The Graph track contract events, but AA's core action—the UserOperation—lives in a mempool. This creates a critical data gap for wallets and dApps.
- Missed Intent: Cannot track pending transactions or simulate complex multi-step flows.
- Broken UX: Wallets can't show real-time status of sponsored or batched transactions.
- Security Blindspot: Hard to monitor for mempool-level attacks targeting paymasters or signature schemes.
0%
UserOp Coverage
~5s+
Status Lag
02
The Solution: Intent-Centric APIs
New APIs must surface the user's intent, not just on-chain state. This requires indexing both the mempool (UserOperations) and the chain (execution results).
- Real-Time Streams: Live feeds of pending UserOps for wallets like Safe and Biconomy.
- Cross-Chain Visibility: Track a user's intent across source and destination chains via bridges like LayerZero and Across.
- Simulation-As-A-Service: Pre-execution checks for bundlers to prevent failed ops and save gas.
~500ms
Intent Latency
100%
Flow Visibility
03
The New Business Model: Paymaster Analytics
Paymasters are the new yield-bearing primitive, sponsoring gas in exchange for fees. Their risk management demands new data products.
- Default Risk: Monitor ERC-20 token balances and volatility for gas sponsorship.
- Usage Analytics: Track which dApps (e.g., UniswapX, CowSwap) drive the most sponsored volume.
- Profitability Dashboards: Real-time metrics on net gas costs vs. fee revenue, critical for protocols like Pimlico and Biconomy.
$10B+
Sponsored Gas TVL
-30%
Default Risk
04
The Architectural Shift: From State to Graph
AA doesn't just change a transaction; it creates a graph of dependencies between paymasters, factories, bundlers, and wallets. Indexers must map this.
- Relationship Mapping: Expose which smart accounts were created by which factories.
- Bundler Performance: Track reliability and latency of bundlers in networks like Stackup and Alchemy.
- Account Graph API: Enable queries like "show all sessions granted by this smart account," unlocking new dApp models.
10x
Data Relationships
<1s
Graph Query Speed
ENQUIRY
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.
NDA Protected
Confidentiality24h Response
Time to ValueDirectly to Engineering Team
No Sales Fluff10+
Protocols Shipped
$20M+
TVL Overall