state-availability - Snake Charmers

Sign in Subscribe

state-availability

A collection of 4 posts

Wanted: Monkey Trainer. Pedestal Builders need not apply.

I recently wrote a few [https://snakecharmers.ethereum.org/the-winding-road-to-functional-light-clients/] blog [https://snakecharmers.ethereum.org/the-winding-road-to-functional-light-clients-part-2/] posts [https://snakecharmers.ethereum.org/the-winding-road-to-functional-light-clients-part-3/] describing what was needed for us to have truly functional light clients. If you haven't read those, you should go do that now. I'll wait... I also gave

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