-
Notifications
You must be signed in to change notification settings - Fork 720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configurable protocol versions #830
Conversation
@mrBliss if you don't mind 'aeson' dependency in |
I'm not keen on doing this. Do they have to be instances here? Doesn't |
I thought so :);
It seems so - the |
Both are lists of supported 'NodeToClientVersion' and 'NodeToNodeVersion' respectively (defined in 'Ouoroboros.Consensus.Node.NetworkProtocolVersion'). The default values are all supported protocols as provided by 'HasNetworkProtocolVersion' class instanct.
They are commented out, since the default (use all supported versions) is the right choice now.
Removed NFData instances, since they are not needed anymore, and one cannont derive them.
266d29a
to
67a2aa1
Compare
stale PR, closing |
Re-opened - at some point this will be updated. |
Spoke with @coot who agreed to close this |
Issue
configuration.yaml file. The default option is to use all supported protocols.
Checklist
This PR contains all the work required to resolve the linked issue.
The work contained has sufficient documentation to describe what it does and how to do it.
The work has sufficient tests and/or testing (in ouroboros-network).
I have committed clear and descriptive commits. Be considerate as somebody else will have to read these.
I have added the appropriate labels to this PR.