This proposal sketches out how Working Groups might work within the Ethereum Improvement Proposal ecosystem.
2/21/2024These things need to be implemented before the core spec code can be frozen: Issues in https://github.com/ethereum/execution-specs/milestone/14 [x] London [ ] The Merge [x] Opcode Refac [ ] Documentation Rendering [ ] https://github.com/ethereum/execution-specs/issues/590 [x] https://github.com/ethereum/execution-specs/issues/591
11/11/2022Discussion link https://ethereum-magicians.org/t/core-eips-in-an-executable-spec-world/8640 Contents [toc] Context Today, Core EIPs are used to specify changes affecting the execution layer (EL) which need to be activated through coordinated network upgrades (a.k.a. soft/hard forks). Core EIPs currently serve two purposes: explaining the motivation/rationale/security implications of the change and formally specifying it. While the former is very useful, and helps the Ethereum community understand and debate changes, the latter isn't ideal for a few reasons:
3/23/2022This is the second of two posts describing account abstraction. You can find the first post here. Special thanks to @adietrichs and the rest of the Quilt team for review, content, and editing! More Account Abstraction? If you haven't yet, read EIP-2938 Account Abstraction Explained for some background on account abstraction (AA) and how EIP-2938 implements it. To quickly summarize it here, EIP-2938 implements just enough AA to support single-tenant applications, with minimal consensus changes and some new transaction propagation rules. While the EIP lays the groundwork for AA and does provide a compelling solution for single-tenant use cases, like smart contract wallets, several use cases are not satisfied and require new features to be fully realized. Features Beyond EIP-2938
10/26/2020or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up