ROSE-449: segregate coinbase spec requirements verification in check:spec #336
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
racbc
reviewed
Jul 12, 2022
racbc
reviewed
Jul 12, 2022
racbc
reviewed
Jul 12, 2022
irisZhangCB
approved these changes
Jul 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ROSE-449: segregate coinbase spec requirements verification in check:spec
Fixes # .
There is no way to tell whether a requirement is Coinbase spec. Also we lack a way to switch b/w running coinbase spec validation and minimum verification (specified in rosetta-api.org).
Solution
See PR for details.
Test Evidence