devcon 7 / anti correlation penalties
- YouTube
- Details
Anti-Correlation Penalties
Duration: 00:09:35
Speaker: Toni Wahrstätter
Type: Lightning Talk
Expertise: Beginner
Event: Devcon
Date: Nov 2024
Anti-Correlation Penalties is a proposal to allow the penalties for missed attestations to vary over slots, based on the number of missed attestations in the respective slots. This is great for non-correlated parties such as solo stakers and improves decentralization, fault tolerance and diversity in the validator set.
- Related
Devcon
Talk
23:52
Ethereum for Dummies
Ethereum's CTO Dr. Gavin Wood presents "Ethereum for Dummies" or "So, now we've built it, WTF is it?"
Devcon
Workshop
55:44
Reading Ethereum's Tea Leaves with Xatu data
Demonstrate how we collect data from the Ethereum network and how it's used for upgrades, research, and analytics. We'll then run through some examples of how to use the tools and public datasets yourself.
Devcon
Talk
25:21
Native Account Abstraction in Pectra, rollups and beyond: combining EOF, EIP-7702 and RIP-7560
Account Abstraction has rightfully become one of the most discussed topics in the Ethereum ecosystem. The upcoming Pectra upgrade is set to be the first one to improve EOAs by including EIP-7702. But can EIP-7702 alone achieve "Account Abstraction"? We will discuss the challenges and benefits of EIP-7702, and break down the team's vision for achieving "complete" Native Account Abstraction with RIP-7560/EIP-7701 and how it differs from ERC-4337 + EIP-7702.
Devcon
Talk
22:54
Decentralizing access to Ethereum utilizing Ethereum's Portal Networks
Accessing Ethereum in a decentralized way has a high barrier to entry for reasons of cost (hardware), knowledge, or time. These problems cause users to rely on centralized providers. A few examples on how Ethereum's Portal Networks will tackle these centralizing forces - EIP 4444's + Portal History will allow nodes to maintain current day RPC, well saving 800GB of storage. - Portal State will allow wallets to use a decentralized backend instead of a centralized backend like Infura.
Devcon
Talk
38:18
Understanding the Ethereum Blockchain Protocol
Ethereum's Vitalik Buterin presents on the intricacies of the Ethereum Blockchain Protocol.
Devcon
Talk
24:53
Ethereum in 25 Minutes, Version MMXVII
So what are all of the different moving parts of the Ethereum blockchain? What are uncles, how do contracts call other contracts, who runs them? What is the role of proof of work and proof of stake, and what exactly is gas? What will EIP86 do for you? Vitalik Buterin provides a 25-minute technical overview of the ethereum blockchain, start to finish, and explain many of these concepts in detail.
![Keynote: [title redacted] preview](https://img.youtube.com/vi/lRqnFrqpq4k/maxresdefault.jpg)
Devcon
Talk
26:22
Keynote: [title redacted]
[description redacted]
Devcon
Talk
26:47
Exploring the Future of Account Abstraction
Discover the journey of Ethereum's Account Abstraction (AA) from inception to its current state, challenges tackled by ERC-4337, and future roadmap: modular native AA approach for L2 and L1, and EOA improvement (EIP-7702).
Devcon
Breakout
19:31
Yul, eWasm, Solidity: Progress and Future Plans
Over the last months, the Yul language has matured and proved its flexibility. The Solidity team has implemented an optimizer and an eWasm dialect and is now full steam working on rewriting the Solidity code generator to produce Yul code to replace sequences of EVM instructions.The Yul optimizer now matches the old EVM optimizer and already surpasses it with features like function inlining and cross-function optimization. This is also the main reason why the new code generator can be written in a super-modular way. Furthermore, it can equally operate on EVM- and eWasm-flavoured Yul code, which is important to cope with the 256- to 64-bit translation.Through this, the Solidity compiler can now output eWasm code, which makes efficient use of 64 bit types. Furthermore, the new code generator includes automated overflow checks everywhere, again something that would have destroyed the old optimizer. Future work:We plan to use a more intricate formal system to remove redundant operations and checks based on range-relations between variables. The introduction of memory area types will help optimizing memory allocation. Finally, a super-optimizer could prove useful, since it is worth spending extra time on compilation to save gas.
Devcon
Talk
25:40
Finding rough consensus on issuance
lido and ef researchers agree on far more than people think. this talk is an attempt to synthesize and explain my take on the big picture as simply as possible with plenty of humour.