Snake Charmers (Page 2)

Sign in Subscribe

A Developer's Guide to Ethereum, Pt. 2

[Last update: May 16, 2023] Welcome back! In the first installment of this series we covered a lot of ground while interacting with a simulated Ethereum network. At this point, you should have at least a fuzzy idea of how to answer these questions: * What's a blockchain and what’s

state-availability

The winding road to functional light clients - part 3

> You should read part 1 [https://snakecharmers.ethereum.org/the-winding-road-to-functional-light-clients/] and part 2 [https://snakecharmers.ethereum.org/the-winding-road-to-functional-light-clients-part-2/] first. Most wallet software depends on centralized providers like Infura. If we want things to be different, we need a new type of light client capable of running on low-resource devices. In

state-availability

The winding road to functional light clients - part 2

> You should read part 1 [https://snakecharmers.ethereum.org/the-winding-road-to-functional-light-clients/] first. It's 2021. Ethereum went live a little more than five years ago. There's currently no reliable lightweight way to interact with the protocol without using a centralized provider. Various research efforts have demonstrated that the functionality can be built

state-availability

The winding road to functional light clients - part 1

It was nearly five years ago that we set out to build Trinity, a new "light weight" client for the Ethereum network. Geth had recently shipped the first versions of the LES protocol and we had big dreams. As often happens with big dreams, they were quickly dashed against the

Alexandria Dev Update #4

Shortly before the Holiday break in December, we successfully spun up a test network of 20 nodes, hosting the first 1 million block headers. T TLDR: The network behaved as intended, with nodes creating and spreading advertisements via the gossip mechanism, mirroring content to fill their storage capacity and serving

Web3.py meets Eth 2.0

Among a dozen other initiatives, the Ethereum 2.0 teams have been working to standardize how developers can interact with beacon nodes. This effort is ongoing, but the latest specification can be found here [https://ethereum.github.io/eth2.0-APIs]. We're excited to announce that Web3.py [https://web3py.readthedocs.

Alexandria Dev Update #3

We are on track to have the core network functionality all working with the full header chain available on the network by the beginning of Q1 2021. The next 2-3 weeks will be spent hardening the client to improve stability and expanding our test network towards a network capable of

Alexandria Dev Update #2

Development continues at a quick pace. Currently, we are aiming to having a POC ready by the end of the year to host and serve the header chain. Content Transmission The last pull requests implementing the content transmission logic are being reviewed. This builds on the SSZ partial work from

Alexandria Dev Update #1

This is the first in what I hope to be a regularly cadenced quick update on the development of the Alexandria network. First, a quick introduction Alexandria is a new protocol under development for the Ethereum ecosystem. The goal is to provide a new peer-to-peer network that exposes the chain

A Developer's Guide to Ethereum, Pt. 1

[Last update: May 16, 2023] So, you’ve heard about this Ethereum thing and are ready to venture down the rabbit hole? This post will quickly cover some blockchain basics, then get you interacting with a simulated Ethereum node – reading block data, checking account balances, and sending transactions. Along the

Applying the "Five Whys" to the Client Diversity problem

The most recent All Core Devs call #90 [https://github.com/ethereum/pm/issues/189] was almost entirely spent discussion a single issue. I would highly recommend going and listening to the call yourself [https://www.youtube.com/watch?v=IZEcukn9J0Y]. On the call Alexey brought up the issue of