devcon 7 / decentralizing access to ethereum utilizing ethereums portal networks
Duration: 00:22:54
Speaker: Kolby Moroz Liebl
Type: Talk
Expertise: Beginner
Event: Devcon
Date: Nov 2024
Ethereum for Dummies
Ethereum's CTO Dr. Gavin Wood presents "Ethereum for Dummies" or "So, now we've built it, WTF is it?"
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.
Anti-Correlation Penalties
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.
Empowering Users: How Ethereum’s Low Node Requirements Promote True Decentralization Over Solana
Nine years after Ethereum's launch, you can still run a node at home on commodity hardware, even low-powered devices like $185 ARM64 boards. Why is this so important? Wouldn't Solana's approach, using more powerful hardware for higher speed and throughput, be better? We'll explore why home nodes matter for decentralization, credible neutrality, and global accessibility. We'll also compare node requirements vs the Nakamoto coefficient as metrics for measuring decentralization.
Understanding the Ethereum Blockchain Protocol
Ethereum's Vitalik Buterin presents on the intricacies of the Ethereum Blockchain Protocol.
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]
[description redacted]
How long non-finality could kill Ethereum
After the merge, Ethereum has a finality gadget to provide an economic assurance that transactions will never be reverted. When 2/3 of the validator set are online and agree, we finalize. Otherwise, we enter a period of non-finality which can be very long, up to a few weeks. Long non-finality has never happened in Ethereum's history and could trigger a cascade of failures that will kill liveness. How can we harden the network against this? How high are the stakes?
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).
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.