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
Once we have enough confidence in RLN performance after benchmarking, RLN validation should be enabled by default for relay nodes and deployed to relevant fleets (i.e. fleets that serve RLN-protected shards). For example, once autosharding dogfooding has started, RLN relay could be enabled in the same fleets allowing RLN dogfooding to start as soon as the first members start publishing. Membership contract could at this stage still be deployed only to a testnet. Membership mechanisms are tracked as separate tasks. This task is dependent on a suitable membership contract being deployed and configured on validators.
Priority: Critical for launch
The text was updated successfully, but these errors were encountered:
Once we have enough confidence in RLN performance after benchmarking, RLN validation should be enabled by default for relay nodes and deployed to relevant fleets (i.e. fleets that serve RLN-protected shards). For example, once autosharding dogfooding has started, RLN relay could be enabled in the same fleets allowing RLN dogfooding to start as soon as the first members start publishing. Membership contract could at this stage still be deployed only to a testnet. Membership mechanisms are tracked as separate tasks. This task is dependent on a suitable membership contract being deployed and configured on validators.
Priority: Critical for launch
The text was updated successfully, but these errors were encountered: