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
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
Analysis of sync-committee performance on Prater testnet. Each row is a specific deployment group (many small ones running by ef, then 4 ones of 17% each by client teams, and power users + smaller clients + more users + recent new deposits to grow for testing larger validator counts).
The height of each row is 32 pixels; one epoch. The x axis is epochs (left side is altair fork epoch, right side is most recent)
Red = missed sync committee participation.
Blue = good sync commitee participation.
Black = not elected in sync committee (512/233,046 chance per validator to be elected, smaller groups are not always running in sync committees), or validator didn't exist yet, or a block was missing.
Until recently nimbus had a bug, but it's been fixed and turned blue now (great work!). And we updated all EF nodes to catch up with latest client changes (thanks Parithosh!). The remaining red rows are Prater users who have yet to update, or are offline.
Consensus-layer Call 73 Agenda
prev: call 72
Meeting Date/Time: Thursday 2021/09/23 at 14:00 GMT
Meeting Duration 1.5 hours
Live stream
The text was updated successfully, but these errors were encountered: