-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat(verified_contracts-values) - add verified_contracts
creation and runtime values constraints
#13
Conversation
b438373
to
ec1f649
Compare
ec1f649
to
657300e
Compare
657300e
to
22d04c7
Compare
verified_contracts
creation and runtime values constraintsverified_contracts
creation and runtime values constraints
verified_contracts
creation and runtime values constraintsverified_contracts
creation and runtime values constraints
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 comment, and about that, we do allow submitting contracts without creation match right? In my mind it was that we require a creation match but runtime match was optional. What I can see from the schema now, is it can be either runtime or creation.
Otherwise great tests again. Thank you
As far as I remember, we've agreed upon at least one match without any difference if it is creation or runtime one. For example, for contracts deployed in genesis there will be no creation matches, but runtime only |
…ding to json schema
…llProtection field
d5c4d8e
to
facb73a
Compare
Add a check that only allowed keys are used inside
verified_contracts.creation_values
andverified_contracts.runtime_values
. Allows for keys not to be present in the object.Adds internal constraints for the values according to json-schema (checks that values are valid hexes and have correct lengths)