Shout-out to everyone who makes FCR possible: > @fradamt OG chad, one of the inventors of FCR, helped with implementation, and formally verified it > @robsaltini EF Consensus team lead, first author on the FCR paper, did tons of spec tests and helped with implementation > @mkalinin2 Teku core dev. Wrote the FCR paper, helped a ton with breakout rooms and fixing implementations > @luca_zanolini helped design FCR and revise the paper to make it more understandable. > @adiasg helped lay the grounds way back when. > Chengyi Zhang also helped with creating FCR > @barnabemonnot for setting up a cluster that prioritizes seeing upgrades fully through and bringing them to market > @joshrudolf for prioritizing UX and helping with GTM > @corcoranwill for leading implementation coordination and making sure FCR gets shipped > @samcmAU for creating the simulations showing 0 fast-confirmed blocks would have been reorged in the past year which moves the needle for potential FCR users > @jtraglia for leading security which is super necessary with a new and relatively complicated algorithm > @MushowUK for getting FCR into the bug bounty, helping increase confidence in FCR implementation > @decentrek for pushing towards production readiness, ensuring security, and help with GTM > @nloureiro for shipping the website super quickly which helps tremendously in GTM > @binji_x for helping everyone including everyone in this thread understand the true impact of FCR > Etan for leading implementation in Nimbus > @nazarhussain for leading implementation in Lodestar > @dapplion for leading implementation in Lighthouse and pushing for a fast tag > @terencechain for leading and giving extra priority to an implementation in Pyrsm And probably a ton of others I’m missing here. It takes a village.