In the rapidly evolving Ethereum ecosystem, two groundbreaking proposals—EIP-3074 and EIP-7702—are reshaping how externally owned accounts (EOAs) interact with the network. These Ethereum Improvement Proposals (EIPs) pave the way for smart wallet behaviors, gasless transactions, and transaction batching, all while maintaining compatibility with existing EOAs.
This guide explores their mechanics, benefits, trade-offs, and future implications for developers, wallet providers, and end-users.
Understanding EIP-3074
EIP-3074 was designed to enhance EOAs by introducing two new EVM opcodes:
- AUTH: Allows users to authorize a contract (called an invoker) to act on their behalf.
- AUTHCALL: Enables the invoker to execute transactions using the user’s authorization.
Key Features:
✔ Gasless Transactions: Users can delegate gas payments to third parties.
✔ Batch Processing: Multiple actions bundled into a single signature.
✔ Delegated Permissions: Time-bound or scope-limited authorizations.
Limitations:
⚠ Security Risks: Invoker contracts become single points of failure.
⚠ EVM Complexity: Introduces new opcodes, increasing long-term maintenance.
👉 Learn how EIP-7702 improves upon these challenges
Exploring EIP-7702
Proposed by Vitalik Buterin, EIP-7702 offers a stateless alternative:
How It Works:
- Users attach executable smart contract code to a transaction.
- The code runs temporarily at the user’s EOA address.
- Post-transaction, the EOA reverts to its original state.
Advantages:
✔ No New Opcodes: Leverages existing transaction structures.
✔ Modular Logic: Each transaction can execute unique workflows.
✔ Reduced Risk: No persistent contract code or shared invoker dependencies.
Core Problems Solved
Both EIPs address EOA limitations:
- Programmability Gap: EOAs lack smart contract flexibility.
- UX Friction: Gas payments and multi-step approvals hinder adoption.
- Compatibility: Avoids migration to new contract-based accounts.
Use Cases:
- dApps: Sponsor user gas fees or batch transactions.
- Wallets: Enable token-based gas payments (e.g., stablecoins).
- DeFi: Streamline complex interactions (e.g., swaps + approvals).
EIP-3074 vs. EIP-7702: Key Differences
| Feature | EIP-3074 | EIP-7702 |
|-----------------------|-----------------------------------|-----------------------------------|
| Mechanism | New opcodes (AUTH/AUTHCALL) | Temporary code injection |
| Persistence | Per-transaction delegation | Single-transaction execution |
| Security Model | Trust in invoker contracts | Self-contained logic |
| Protocol Changes | EVM modifications | No new opcodes |
Verdict: EIP-7702 is the preferred path forward, superseding EIP-3074 in Ethereum’s Pectra upgrade.
Current Status and Timeline
- EIP-3074: Withdrawn (2025) due to security and complexity concerns.
- EIP-7702: Slated for Pectra upgrade (May 2025). Major wallets (e.g., Trust, Ambire) already support it.
FAQs
1. Can I use EIP-7702 with my existing EOA?
Yes! Your address temporarily adopts smart contract logic per transaction.
2. Does EIP-7702 require a new wallet?
No—existing wallets can integrate support via software updates.
3. Is EIP-3074 still relevant?
No. EIP-7702 achieves its goals more efficiently without opcode bloat.
👉 Discover how Ethereum’s Pectra upgrade impacts wallets
Conclusion
EIP-3074 and EIP-7702 mark pivotal steps toward full account abstraction, blending EOA simplicity with smart contract power. While EIP-3074 laid the groundwork, EIP-7702’s stateless, modular approach is set to redefine Ethereum’s UX in 2025.
For developers and projects, early adoption ensures competitive advantage—whether building wallets, dApps, or DeFi protocols. Stay ahead by aligning with these protocol shifts today.
Need expert guidance? Let’s discuss your Ethereum integration strategy.