You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first one explains FFG/Casper & inactivity leak, the second one expands on the first one with a focus on execution layer diversity and the risks involved, the last one on consensus.
The last one is especially important as today, it is not recognized that there is a systemic risk with using >33% on the consensus side, it extrapolates from a bug that happened on Goerli at the dawn of the network (described by Prysm core devs here: https://x.com/potuz_eth/status/1768418899111113125). I think it would help to shape a bit differently some parts of the UX:
red color for anything > 33% on the consensus side, green < 33%
red color for anything > 66% on the execution side, yellow between > 33% and 66%, green < 33%
Happy to help driving in this direction if it makes sense to you :)
The text was updated successfully, but these errors were encountered:
We wrote a series of research/articles on client diversity which could have a place here:
The first one explains FFG/Casper & inactivity leak, the second one expands on the first one with a focus on execution layer diversity and the risks involved, the last one on consensus.
The last one is especially important as today, it is not recognized that there is a systemic risk with using >33% on the consensus side, it extrapolates from a bug that happened on Goerli at the dawn of the network (described by Prysm core devs here: https://x.com/potuz_eth/status/1768418899111113125). I think it would help to shape a bit differently some parts of the UX:
Happy to help driving in this direction if it makes sense to you :)
The text was updated successfully, but these errors were encountered: