Derek Chiang's blog

This article was originally published on X.

This article was originally published on X.

This article was originally published on X.

I’m working at Ethlabs, where we build great Ethereum technologies and help builders incorporate them in products.

This article was originally published on X.

Vitalik and Yoav kindly reviewed this post, but opinions are my own.

Update: Since this post was written, EIP-7702 has been proposed to replace EIP-3074.

(Thanks to Yoav Weiss and Dan Finlay for feedback and review.)

In our last blog post, we argued in favor of ERC-7579 over ERC-6900 as a standard for modular smart accounts.

(Update: we published a follow-up blog post.

Web3 UX today faces many challenges.

With the launch of ERC-4337, we are seeing tremendous excitement from Web3 developers to build the next generation of crypto wallets using account abstraction.

Unless you check new ERCs everyday (in which case, good for you), you probably haven’t noticed this new ERC known as ERC-6492, innocuously named “Signature Validation for Predeploy Contracts.”

At ZeroDev, it’s our job to help devs learn and adopt AA, so naturally we have come across a lot of questions, concerns, and objections.

Japanese translation by frasco Discuss on Hacker News.* Background In this blog post, I would like to describe an extension to the popular “functional options” pattern that has been described by people like Rob Pike and Dave Cheney.