@farcaster

FIP Explainer: Onchain Config Registry for Snapchain #277 today, the list of validators that run farcaster's network lives in a config file that gets edited by hand. when a validator joins, leaves, or rotates its keys, someone updates that file and every operator coordinates privately to restart at the right moment. why does it matter? two reasons. the practical one is coordination, changing the validator set today means everyone updating a file and restarting in sync, and this makes most of that automatic. the other is that the membership history ends up on ethereum, public and permanent, so anyone can check who the validators were at any given point instead of trusting that the file they were handed is accurate. who does this affect? validator operators. read nodes already have this, so it's the same quality of life improvement coming to the validator side. if you just use farcaster nothing about your day-to-day changes, casts and follows and everything else work exactly the same. what about validators running today? nothing breaks and nothing needs to be reconfigured, it's on by default. consensus doesn't change either, blocks get proposed and finalized exactly the way they do now, this only changes where the membership list lives and how validators read it. https://github.com/farcasterxyz/protocol/discussions/277

0 reply

36 recasts

122 reactions