Try   HackMD

EIP-1559 Resources 🔥

Various write ups, simulations, documentation, and more related to EIP-1559.

Explainers & Analyses

General Overview

UX

Security

Economics

1559 Pre-History

Community

Mining

1559 Simulations

Last changed by 
 
Tim Beiko
3
20
41764

Read more

censorship.wtf

NYC Prague Istanbul Speaker Email Topic3:00 9:00 11:00 Tina Zhen (Istanbul Host) tina@flashbots.net Istanbul Stage Opening + Chapter 0: Bird’s Eye View of the Problem Space3:05 9:05 11:05 Juan Benet juan@protocol.ai Preventing Digital Totalitarianism3:25 9:25 11:25 Vitalik Buterin v@buterin.com Hardening the Ethereum Ecosystem Across the Stack3:45 9:45 11:45 Vitalik Buterin & Juan Benet v@buterin.com, juan@protocol.ai Mutual Q&A4:00 10:00 12:00 Sreeram Kannan sreeram@eigenlabs.org Increasing the Observability of Attestor Censorship4:20 10:20 12:20 Costanza Gallo costanza@ethswarm.org Censorship From 0 to 604:40 10:40 12:40 Tim Beiko (Prague Host) tim@ethereum.org Prague Stage Opening + Chapter 1: Deconstructing the Ethereum L1 CR Problem4:45 10:45 12:45 Danno Ferrin dannoferrin@gmail.com Mind Your Business: State Proofs and Transaction Verification5:05 11:05 13:05 Alon Muroch alon@blox.io Improving Censorship Resistance Using DVT5:25 11:25 13:25 Nixo nixorokish@pm.me Are Solo Stakers Valuable for Censorship Resistance?5:45 11:45 13:45 Sebastian Bürgel sebastian.buergel@hoprnet.org The Dark Endgame of CL, EL & Application Layers Without IP-level Privacy6:05 12:05 14:05 Toni Wahrstätter info@toniwahrstaetter.com Exploring Censorship Across The PBS Stack6:25 12:25 14:25 Sajida Zouarhi Observability and Censorship in Ethereum6:40 12:40 14:40 Tim Beiko (Prague Host) tim@ethereum.org Chapter 2: Exploring Alternatives in Application Infrastructure6:45 12:45 14:45 Henri Binsztok henri@okcontract.io Alternate Frontends: Why and How7:05 13:05 15:05 Yoav Weiss yoav@ethereum.org Account abstraction is easy… unless you care about censorship resistance7:25 13:25 15:25 Garrett MacDonald g@rre.tt Alternate Data Transport Layers7:45 13:45 15:45 Tina Zhen (Istanbul Host) tina@flashbots.net Chapter 3: Surveying the Approaches from L2 Perspectives7:50 13:50 15:50 Nashqueue N/A Exploring Attacks in the Modular Rollup World8:10 14:10 16:10 Santiago Palladino santiago@aztecprotocol.com Deep Dive into Private State and Execution of Smart Contract8:30 14:30 16:30 Omar Espejel espejel@starknet.org Starknet’s Approach to Sequencer Censorship8:50 14:50 16:50 Ed Felten ed@offchainlabs.com Improving Deadline Protocols via Censorship Detection9:10 15:10 17:10 Tina Zhen (Istanbul Host) tina@flashbots.net Chapter 4: Weaving Theories into Practice9:15 15:15 17:15 Mallesh Pai An Economic Definition for Censorship Resistance9:35 15:35 17:35 Justin Drake justin@ethereum.org Weak Censorship Resistance9:55 15:55 17:55 Venkatesh Rao vgururao@gmail.com Beyond Exit and Voice

Dec 20, 2023
AllCoreDevs Updates

Updates about Ethereum core protocol development.

Dec 12, 2023
Protocol Guild Architecture

Some disclaimers: not a solidity dev, probably very inefficient/exploitable/etc. Very rough mental model! Architecture Let's start with a rough diagram: I imagine the guild having the following components: Receipients list: a mapping of all eligible receipient addresses, along with their weights/points/etc. We should assume this list and weights can change over time. Epochs: a "time bucket" to better subdivide grant streams and to use as a reference point for list updates. This could maybe be done "each block", but feels even more inefficient. Also, perhpas these epochs store some metadata about whether tokens for a specific recipient have been claimed in this epoch. Streams: a donation to the guild. Streams need to specify which epoch to start at, as well as a duration/vesting period. A number of token is sent alongside the stream, and every epoch makes available stream total / duration tokens, until the current epoch > start epoch + duration. It may be possible to have tokens pre-vest partially by having start epoch be earlier than the current epoch.

Oct 8, 2022
Besu Execution Client Incentive Program

[toc] Overview The Ethereum Foundation is launching an Execution Layer Client Incentive Program (ELCIP). This program will provide execution-layer client teams with locked ETH in the form of live validators to be released according to certain milestones, including post-merge performance and progress towards enabling withdrawals from the beacon chain. Program Goals & Eligibility The program aims to provide long-term support and incentives for teams towards maintaining reliable clients and a healthy network overall. For client teams to be eligible, they should already be contributing to the general development of Ethereum and intend to support the upcoming transition to proof of stake. Throughout the program, teams will need to maintain certain levels of performance to be eligible for the rewards. More on this below.

Sep 15, 2021
Read more from Tim Beiko
Published on HackMD