EIP-3074, a proposal for Ethereum's roadmap, aims to enhance smart accounts with features like AUTH and AUTHCALL. It addresses security risks, UX benefits, and potential complexities for developers. The proposal is expected to launch in the next Ethereum hard fork, enabling new EVM instructions and improving user experience.
With EIP-3074, the new wallet APIs defined in ERC-5792 are more important than ever! See demo from @0xlsr here https://t.co/tkewI3Bgf4 Can try this with the Smart Wallet beta SDK today https://t.co/V9ohmBoxu0
- EIP 3074 unlocks critical features and UX improvements for intents. - In 3074, wallets like metamask will approve and “white list” apps that are allowed to use 3074. - Metamask is owned by consensys and building their own intent protocol. - 3074’s authors are ex-consensys. 1/3 https://t.co/iM0EAw4pNh
Deep Dive into EIP 3074 🌐Big news! EIP 3074 is set to launch in the next Ethereum hard fork, introducing two new EVM instructions: AUTH and AUTHCALL. By using AUTH to authenticate via ECDSA signature, and AUTHCALL to allow transactions by authorized accounts, it ensures…
EIP-3074 summary: - Security risk overblown - UX pros (batching, sponsorship) are big IF wallets/dapps support them - Incoming DX nightmare handling EOAs/3074/4337 separately - 5003 should follow Success: 3074/AA DX converges Failure: more perma-complexity for devs Blog 👇
i was nerdsniped by @ETazou into implementing a POC for eip-3074 in @vyperlang. here is how eip-3074 *could* look in the language design 🙂. (so far, my personal take is it feels kind of like a native implementation of erc20 permit). https://t.co/NAFrlor8YA https://t.co/ptk7VVmuwb
How does EIP-3074 fit into the AA roadmap for Ethereum? How can it be utilized to push forward smart accounts? And what is missing from EIP-3074? https://t.co/x7TqEtwCKM