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 11, 2022. It is now read-only.
We can change the protocol ID from paritytch to dot for now.
I'm hesitant to make the protocol ID configurable more or less unrestricted right now. For example, by introducing a protocol_id parameter to beefy_peers_set_config(). If the protocol_id argument gets screwed up or is a duplicate or is just wrong, some pretty bad mayhem may be the result.
If we do have an authoritative list of current, canonical protocol IDs, a concrete protocol_id argument could be checked against that list, of course. This would at least provide some safety measure.
Ideally, once we have a more generic, configurable BEEFY, the protocol_id should become part of the set of accepted (and properly restricted) configuration values.
The reasons outlined in Change the name of the GrandPa notifications protocol are valid for
BEEFY
as well.Hence, the
BEEFY
notification protocol name should be changed in accordance with theGRANDPA
notification protocol name.The text was updated successfully, but these errors were encountered: