Content
@
0 reply
0 recast
0 reaction
Roberto Bayardo 🎩
@bayardo.eth
Would love to hear your take on this @terencechain. https://x.com/danrobinson/status/1820506643739615624?t=AGEVGUP4HkONb6qxfl-1ow&s=19
1 reply
0 recast
3 reactions
terence
@terencechain
Without more than a high-level Ethereum research post or a 35-minute video, it's hard to judge how simple or difficult BRAID is. I'm typically in the "devil is in the details" camp. One thing BRAID simplifies over something like FOCIL is that it doesn't require introducing a third type of actor (inclusion list constructor). Without this additional actor and duty, your slot anatomy flows just the same as today, avoiding conflicts over how to split the 12-second slot time, which I discussed more here: https://ethresear.ch/t/inclusion-list-timing-constraints/20198 BRAID's complexity will revolve around fork choice, consensus changes, and dealing with DOS and free DA. It takes a more from-scratch approach, which is often cleaner but will require more research and engineering cycles to fully understand its full implications.
0 reply
0 recast
3 reactions
