Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Contracts don't have verification functionality #20

Open
alkopnin opened this issue Sep 16, 2018 · 0 comments
Open

Contracts don't have verification functionality #20

alkopnin opened this issue Sep 16, 2018 · 0 comments
Assignees
@seniorjoinu
Labels
critical enhancement New feature or request good first issue Good for newcomers

Comments

@alkopnin
Copy link
Contributor

A change of state should be connected with command and contract. The contract checks the transaction correctness based on input/output and attached commands.

Description

There are 3 states: IndySchema, IndyCredentialDefinition, IndyCredential and 4 commands: Create, Upgrade, Consume and Revoke exist in cordentity.

Need to implement proper contracts and verification logic for each state and related command.

Expected Behavior

Currently the contracts don't really exist.

They should check such data as transactional signatures, credential definition limits, matching the attributes from schema to credential definition, list of revealed attributes, etc.
@alkopnin alkopnin added enhancement New feature or request good first issue Good for newcomers critical labels Sep 16, 2018
@seniorjoinu seniorjoinu self-assigned this Oct 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@seniorjoinu seniorjoinu

Labels
critical enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alkopnin @seniorjoinu