There are tons of examples of competitors helping me a long the way, I can’t possibly list and thank them all, but here are some of them:
- @ilblackdragon and @AlexSkidanov: Awesome at being a sounding board and spotting the 'birthday problem' bug in the xor hasher. The hash is back, but now with lattice math 🤯!!!
- @dominic_w : Might not remember, but way back in super early 2018, he hopped onto a panel with me, putting me in the spotlight.
- @zmanian: The L1 founder therapist you call when everything's on fire and you need to freak out.
- @dankrad: He shed light on kzg commitments and their role in light client sampling, sparking some cool turbine upgrades. Our debate on light client security reshaped my thoughts on protecting L1 users.
- @VitalikButerin: A role model for L1 founders and a wizard at researching the next big thing months in advance.
- @toghrulmaharram, @colludingnode: In a parallel universe, I'd totally be your teammate.
Wishing these amazing folks and their communities stellar holidays and a fabulous new year! 🎉🥳🎊🎁🍾
@likebeckett Gotha. So a shared sequencer set is a group of nodes that each runs one or more rollapps and they coordinate among themselves to produce blocks for all rollapps synchronously?
@likebeckett Say, each rollapp can get 1000 tps with its own sequencer. Now you colocate two rollapps on a shared sequencer and each rollapp only gets 500 tps? If so, isn't this defeating the purpose of sharding in the first place? What am I missing here?