-
Notifications
You must be signed in to change notification settings - Fork 105
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
Alan - Spec alignment #1511
Alan - Spec alignment #1511
Conversation
5481828
to
93ee563
Compare
(Regarding the msgID attributes) No. We don't have DomainTypeProvider in spec and the CommitteeID is, actually, better as implemented in the node. Although they result the same, if one needs to change, it should be spec.
This is outside of the scope of spec. And it seems that it's being used in the node.
I've raised this issue before (this is the function that is never called, remember?). I agree we can change to DomainError and return the error. May I add that?
This difference already existed before. Since the problem is in spec, I preferred approving it here and creating the issue in spec. What do you think? |
yes please
+1 agreed on the rest |
Overview
This PR updates the approved changes between ssv and spec, for the spec-alignment script.
Also, it performs a single alignment change.