Ethereum wallets may soon undergo a transformative upgrade. With the proposed changes from EIP-3074, externally owned accounts (EOAs) will gain the ability to send batch transactions, schedule delayed transactions, process out-of-order transactions, and more—without requiring ETH balances.
How EIP-3074 Works: AUTH and AUTHCALL Opcodes
Developed by @lightclients, @\_SamWilsn\_, and @adietrichs, EIP-3074 introduces two new Ethereum opcodes:
AUTH: Validates a signature from an EOA against an off-chain message.AUTHCALL: Executes a call while setting themsg.senderto the EOA's address (verified viaAUTH).
This enables a relay system where:
- Users sign messages containing their intended actions.
- Relayers submit these signatures + call data to an Invoker Contract.
- The invoker uses
AUTHto verify signatures, thenAUTHCALLto execute transactions on behalf of the user.
👉 Discover how this compares to meta-transactions
Key Advantages Over Meta-Transactions
| Feature | Meta-Transactions | EIP-3074 |
|---|---|---|
| Contract Support | Requires explicit integration | Works with any contract |
| Gas Abstraction | Complex fee delegation | Native ETH-less transactions |
| Flexibility | Limited by design | Customizable via commit_hash |
Trustless Design Principles
EIP-3074 achieves decentralization through carefully structured signatures. Users sign: keccak(0x03 ++ invoker_address ++ commit_hash)
Critical Components:
- Type Byte (0x03): Prevents signature conflicts with other standards (EIP-1559, EIP-2930).
- Invoker Address: Binds execution to a specific contract, allowing users to choose trusted invokers.
- Commit Hash: Enables advanced rules (expiration, nonces, multi-call bundles).
Example: Batch Transactions
By hashing multiple calls into a single commit_hash, invokers can:
- Verify all parameters (nonces, expiration blocks)
- Execute authenticated calls sequentially
- Maintain security without requiring per-transaction signatures
Potential Use Cases
- Gas Sponsorship: Apps can pay fees for users via relayers.
- Transaction Scheduling: Set future-dated executions using expiration parameters.
- Multi-Operation Bundles: Swap tokens + deposit to DeFi in one signature.
👉 Explore advanced invoker implementations
FAQ
Q: Is EIP-3074 live on Ethereum mainnet?
A: Not yet—it's currently in proposal stage with prototype implementations available.
Q: How does this differ from smart contract wallets?
A: EIP-3074 works with existing EOAs, while SC wallets require migration. Both can coexist.
Q: What security audits are needed?
A: Invoker contracts require rigorous auditing like major DeFi projects due to their privileged role.
Q: Can invokers steal funds?
A: No—they can only execute calls the user explicitly signed for via commit_hash constraints.
For the complete technical specification, refer to the EIP-3074 official documentation. The go-ethereum prototype is available here.
This content adheres to Ethereum Community Network's mission to provide accurate, trustless educational resources for the Chinese Ethereum ecosystem.