3.0 KiB
AIP-14: Account Abstraction: ERC-4337 with EIP-7702 Bridge, not Native AA
Preamble
| Field | Value |
|---|---|
| AIP | 14 |
| Title | Account Abstraction: ERC-4337 with EIP-7702 Bridge, not Native AA |
| Author | Aere Network Foundation |
| Type | Informational |
| Category | (none) |
| Status | Final |
| Created | 2026-07-19 |
| Requires | 6 |
| Supersedes | None |
| Superseded-By | None |
| Ratification | Foundation-ratified (pre-decentralization) |
Abstract
This AIP records the decision to deliver programmable accounts through ERC-4337 smart accounts with EIP-7702 as the migration bridge, rather than protocol-level native account abstraction. It backfills a decision already live on chain 2800. The normative stack is in AIP-6; this record captures the decision framing.
Motivation
Aere wants programmable accounts (recovery, passkey ownership, post-quantum ownership, gas sponsorship) without breaking EVM and externally-owned-account compatibility.
Specification
ERC-4337 (v0.7) smart accounts as the account-abstraction path, with EIP-7702 (live under the Pectra ruleset) as the migration bridge that lets existing externally-owned accounts delegate to smart-account code. EIP-3074 is not implemented.
Rationale
ERC-4337 needs no consensus change, is an established standard with an existing
bundler and tooling ecosystem, and delivers programmable accounts (including the
Falcon-owned post-quantum smart account AerePQCAccountFactory) without touching
the protocol, preserving exact EVM and Ethereum compatibility. EIP-7702 is the
chosen bridge precisely because it upgrades existing externally-owned accounts in
place without forcing a disruptive "everything is a contract" change.
Alternatives rejected. Native, protocol-level account abstraction up to an "all accounts are smart accounts by default" end state: it changes what an account fundamentally is, breaking existing tooling, contracts, and user keys. EIP-3074, an earlier proposal for empowering externally-owned accounts: it was superseded upstream by EIP-7702, which is the mechanism Aere carries.
Backwards Compatibility
Existing externally-owned accounts keep working unchanged. Migration via EIP-7702 is opt-in per account.
Security Considerations
The EntryPoints are Aere's own ERC-4337-compatible implementations: compatible in shape and interface but not byte-identical to Ethereum's canonical audited singleton. Integrators should treat them as Aere-specific and should not assume the upstream audit applies to them. These contracts have not had an external audit.
Gasless onboarding is subsidized (Foundation-funded, rate-limited), not free. A paymaster that runs out of funds stops sponsoring; onboarding degrades rather than fails silently.
Reference Implementation and On-Chain Deployment
The normative stack (accounts, factories, paymasters, EntryPoints) with addresses is in AIP-6. Chain ID 2800.
Errata
None.
Copyright
Released to the public domain (CC0). No rights reserved.