Contracts don't have verification functionality #20
Description
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.