> ## Documentation Index
> Fetch the complete documentation index at: https://docs.biconomy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Beyond Account Abstraction: ERC-4337 vs. MEE

> Understand how MEE extends beyond ERC-4337's account abstraction to enable true cross-chain composability

<Info>
  ERC-4337 introduced account abstraction, significantly improving blockchain UX. However, as applications grow in complexity and users operate across multiple chains, developers have encountered limitations that Modular Execution Environments (MEE) are designed to solve.
</Info>

## Full ERC-4337 Parity

The Modular Execution Environment (MEE) stack has **all** the features that ERC-4337 has *and* retains the same industry-leading security profile while offering significantly more features, less latency and easier integration.

<CardGroup cols={2}>
  <Card title="ERC-4337 UserOps" icon="file-contract">
    MEE uses the same data model as ERC-4337
  </Card>

  <Card title="EIP-7702" icon="key">
    MEE can easily be set as the execution environment for an EIP-7702 enabled EOA
  </Card>

  <Card title="ERC-7579" icon="shield-check">
    MEE uses smart account validators which are compliant with the most widely used smart account standard
  </Card>

  <Card title="ERC-7710 / ERC-7715" icon="handshake">
    MEE can request execution through an ERC-7715 delegation and claim it on an ERC-7710 compliant contract
  </Card>
</CardGroup>

## Key Advantages of MEE Over ERC-4337

### True Composability

<Tabs>
  <Tab title="ERC-4337">
    Limited to static batching where all calldata must be known upfront. Transactions within a batch cannot use the results of previous steps.
  </Tab>

  <Tab title="MEE">
    Enables dynamic execution where each step can reference outputs from previous steps. This allows for conditional execution, runtime calculations, and complex transaction flows even on a single chain.
  </Tab>
</Tabs>

### Cross-Chain Orchestration

<Tabs>
  <Tab title="ERC-4337">
    Limited to single-chain operations. Cross-chain activities require multiple separate transactions with separate signatures.
  </Tab>

  <Tab title="MEE">
    Natively orchestrates operations across chains, handling dependencies and timing considerations automatically. A single signature can authorize a complex flow spanning multiple chains.
  </Tab>
</Tabs>

### Universal Gas Abstraction

<Tabs>
  <Tab title="ERC-4337">
    Supports paying gas in tokens on a single chain, but each chain's operations require separate gas management.
  </Tab>

  <Tab title="MEE">
    Allows paying for gas on any chain using tokens from any other supported chain. A single gas tank can fund operations across all chains.
  </Tab>
</Tabs>

### Transaction Scheduling and Automation

<Tabs>
  <Tab title="ERC-4337">
    No native support for scheduling or recurring transactions.
  </Tab>

  <Tab title="MEE">
    Supports scheduling transactions for future execution and setting up recurring execution patterns, enabling automation of complex workflows.
  </Tab>
</Tabs>

## Capability Comparison

| Capability                       | ERC-4337 | MEE |
| -------------------------------- | -------- | --- |
| **Transaction Execution**        |          |     |
| Simple batch transactions        | ✅        | ✅   |
| Dynamic composable transactions  | ❌        | ✅   |
| Output-to-input references       | ❌        | ✅   |
| Transaction scheduling           | ❌        | ✅   |
| Recurring transactions           | ❌        | ✅   |
| **Gas Management**               |          |     |
| Pay gas in tokens (single chain) | ✅        | ✅   |
| Pay gas in tokens (cross-chain)  | ❌        | ✅   |
| Unified gas sponsorship          | ❌        | ✅   |
| **Wallet Support**               |          |     |
| Smart contract wallets           | ✅        | ✅   |
| EOA wallets                      | ❌        | ✅   |
| **Multi-Chain Support**          |          |     |
| Single-chain operations          | ✅        | ✅   |
| Cross-chain orchestration        | ❌        | ✅   |
| Bridge completion detection      | ❌        | ✅   |
| Chain-agnostic development       | ❌        | ✅   |

<Note>
  \*ERC-4337 supports EOA wallets exclusively when paired with EIP-7702. MEE supports EOA wallets by default.
</Note>

## Use Cases Enabled by MEE

MEE enables new user experiences that would be impractical with ERC-4337:

<CardGroup cols={1}>
  <Card title="Cross-Chain DeFi Strategies" icon="arrows-rotate">
    Bridge assets to highest-yielding chains, swap to required assets, and deposit into protocols with a single signature.
  </Card>

  <Card title="Conditional Asset Management" icon="code-branch">
    Create execution flows based on price conditions, bridge completions, or yield opportunities across multiple chains.
  </Card>

  <Card title="Autonomous Agent Workflows" icon="robot">
    Authorize agents to execute strategies within user-defined boundaries without requiring multiple signatures.
  </Card>
</CardGroup>

## Conclusion

<Tip>
  ERC-4337 was a critical stepping stone for blockchain UX. MEE builds directly on this foundation, preserving all benefits while solving fundamental limitations in composability and cross-chain orchestration.
</Tip>

MEE isn't replacing ERC-4337—it's fulfilling its vision of making blockchain interactions seamless across the increasingly fragmented chain landscape, benefiting both developers and users with simpler, more powerful transaction capabilities - while retaining all of the features of the ERC-4337 stack.