Wallets & security
ERC-4337: programmable accounts without assuming one private key is enough
Bundlers, account validation and optional paymasters split a transaction flow into distinct responsibilities.
Research articles and reference entries are published in English. Navigation is available in seven languages.
People & projects
The operation path
ERC-4337 describes an account-abstraction design using user operations, bundlers and an EntryPoint contract. A smart account validates an operation according to its own rules rather than relying solely on the behaviour of a traditional externally owned account. An optional paymaster can participate in paying gas under specified conditions.
This makes features such as alternative authentication, batched actions and sponsored execution possible. The user still needs to understand the account's actual validation and recovery rules. Programmable access can be safer or weaker depending on those rules and who can change them.
Sponsorship is a dependency
A free transaction can depend on a sponsor accepting the request. A bundler can decline to include it. A recovery mechanism can have guardians, delays or administrative powers. These are concrete components to inspect, not reasons to assume every smart account has the same guarantees.
Compare EOA delegation, which uses a different mechanism, and signing intent. A product description should name the permissions and fallback routes that remain if the provider disappears or the sponsor stops paying.