The Ethereum ecosystem is undergoing a quiet revolution in account management and transaction flexibility, driven by two pivotal Ethereum Improvement Proposals: EIP-3074 and EIP-7702. These proposals aim to bridge the gap between traditional externally owned accounts (EOAs) and the advanced functionality of smart contract wallets—without requiring users to abandon their familiar wallet setups.
While both EIPs target account abstraction, they take different technical paths. Understanding their mechanics, trade-offs, and real-world implications is essential for developers, wallet providers, and forward-thinking dApp builders.
What Is EIP-3074?
EIP-3074 was introduced as a method to enhance EOAs by allowing them to delegate transaction execution to smart contracts. It proposed two new EVM opcodes: AUTH and AUTHCALL. These would let a user sign a message authorizing a designated "invoker" contract to act on their behalf.
This mechanism enables:
- Gasless transactions, where a dApp or service sponsors gas fees.
- Transaction batching, allowing multiple actions in one signature.
- Delegated permissions, such as granting time-limited spending rights.
Despite these benefits, EIP-3074 faced significant challenges:
- New EVM opcodes increase protocol complexity and maintenance burden.
- Security risks arise from reliance on centralized invoker contracts—compromising one could affect thousands of users.
- Upgrade limitations make long-term adaptability difficult.
These concerns sparked the search for a more elegant, future-proof solution.
What Is EIP-7702?
Enter EIP-7702, authored by Vitalik Buterin in May 2024. This newer proposal achieves similar goals as EIP-3074—but without modifying the EVM.
Instead of introducing new opcodes, EIP-7702 introduces a new transaction type that allows an EOA to temporarily behave like a smart contract by injecting executable code for a single transaction. After execution, the account reverts to its original state—no residual code remains.
Key advantages:
- No new opcodes—preserves EVM simplicity and avoids technical debt.
- Per-transaction modularity: Each transaction can carry unique logic (e.g., trading, bridging, session control).
- Stateless operation: No persistent changes to the account, reducing long-term risk.
- Compatibility: Works seamlessly with existing infrastructure and ERC-4337-based account abstraction systems.
👉 Discover how next-gen wallet features are reshaping user experience on Ethereum.
Core Problems Solved by EIP-3074 and EIP-7702
EOAs, while secure and widely used, lack programmability. They can't natively support:
- Batched transactions
- Gas sponsorship
- Delegated controls
- Token-based gas payments
Both EIPs aim to solve this by enabling EOAs to temporarily access smart contract-like behavior. This means users can enjoy advanced features without migrating to new wallet types—a major UX win.
EIP-3074 does so via contract delegation, while EIP-7702 uses temporary code injection. Both align with the broader vision of native account abstraction, bringing Ethereum closer to fully programmable, user-centric accounts.
Implications Across the Ecosystem
For End Users
Users gain access to:
- Single-click transaction flows combining approvals and actions.
- Gas paid in tokens (e.g., stablecoins), not just ETH.
- Spending limits delegated to services or friends.
- Smart behavior without new wallets—existing addresses become "upgradable."
However, risks remain:
- Phishing attacks could trick users into authorizing malicious code.
- Transparency in wallet interfaces is critical—users must clearly see when delegation occurs.
Wallets like Trust Wallet and Ambire have already implemented early support for EIP-7702, showcasing its practical potential.
For Wallet Providers
Wallets must now:
- Support new transaction types (for EIP-7702).
- Safely generate and sign delegation payloads.
- Clearly communicate temporary code execution to users.
The shift enables wallets to offer “smart wallet” features natively—without forcing users to adopt complex contract accounts. Most major wallets are expected to roll out opt-in support ahead of mainnet activation.
👉 See how leading wallets are integrating smart account capabilities today.
For dApps and Smart Contracts
Developers must account for:
msg.senderpotentially being an EOA with injected logic.- Potential breaks in
tx.originchecks during nested calls. - New patterns for meta-transactions and sponsored flows.
Security audits now need to assess:
- Authorization flows
- Delegate code integrity
- Edge cases in multi-step transactions
Despite complexity, these changes unlock powerful design patterns—like bundling user actions into sponsored transactions or enabling session keys for decentralized platforms.
EIP-3074 vs EIP-7702: A Comparative Overview
| Aspect | EIP-3074 | EIP-7702 |
|---|---|---|
| Mechanism | Uses new opcodes (AUTH, AUTHCALL) | Uses new transaction type with temporary code |
| EVM Changes | Requires new opcodes | No new opcodes |
| Persistence | One-time delegation per tx | Code persists until explicitly revoked |
| Security Model | Depends on trusted invoker contracts | User carries logic; no central point of failure |
| Flexibility | Limited by invoker logic | Fully customizable per transaction |
| Status (Mid-2025) | Withdrawn | In "Last Call", scheduled for Pectra |
💡 Key Insight: EIP-7702 effectively supersedes EIP-3074. Core developers agree it delivers the same benefits with better security, lower complexity, and no EVM bloat.
FAQ: Your Questions Answered
Q: Is EIP-3074 still active?
A: No. As of mid-2025, EIP-3074 has been officially withdrawn from consideration for mainnet inclusion.
Q: When will EIP-7702 go live?
A: It is scheduled for activation during the Pectra upgrade on May 7, 2025, pending final client coordination.
Q: Do I need a new wallet for EIP-7702?
A: Not necessarily. Existing EOAs can use EIP-7702 features if your wallet supports the new transaction type.
Q: Can I pay gas in USDC with EIP-7702?
A: Yes—wallets like Trust Wallet already demonstrate this capability using token-wrapping logic within the temporary contract code.
Q: Is EIP-7702 secure?
A: It’s considered safer than EIP-3074 because it avoids centralized invokers. However, users must remain vigilant against phishing and malicious code injection.
Q: Does this replace ERC-4337?
A: No. EIP-7702 complements ERC-4337 by bringing similar capabilities to native EOAs, whereas ERC-4337 focuses on full smart account infrastructure.
Status and Timeline (Mid-2025)
✅ EIP-3074 – Withdrawn
Proposed in 2020, it gained traction but faced strong opposition over security and complexity concerns. By mid-2025, it was formally withdrawn from the roadmap.
✅ EIP-7702 – On Track for Pectra
Introduced in May 2024, rapidly refined, and now in "Last Call" status. It’s confirmed for inclusion in the Pectra upgrade (May 7, 2025)—a combination of Prague (execution layer) and Electra (consensus layer) upgrades.
Client teams (Geth, Nethermind, etc.) have implemented Pectra features on devnets. Test suites are active, and major wallets are preparing support.
👉 Stay ahead of Ethereum’s protocol upgrades with real-time insights.
Final Thoughts
EIP-3074 and EIP-7702 represent critical steps toward native account abstraction on Ethereum. While both sought to empower EOAs with smart contract functionality, EIP-7702 emerges as the superior path forward—offering flexibility, security, and backward compatibility without bloating the protocol.
With mainnet activation expected in mid-2025, developers and product teams have a narrow window to prepare. Integrating early means not just adapting—but leading in the next era of user-centric blockchain experiences.
The line between EOAs and smart contracts is blurring. Soon, every wallet could be a smart wallet—without changing a single key.
Core Keywords: EIP-3074, EIP-7702, account abstraction, Ethereum Improvement Proposals, smart wallets, gas sponsorship, transaction batching, EOAs.