Documentation
¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type ValidatorOneValidSignature ¶
type ValidatorOneValidSignature struct {
}
ValidatorOneValidSignature implements the default transaction validation policy, which is to check the correctness of the read-write set and the endorsement signatures
func (*ValidatorOneValidSignature) Init ¶
func (vscc *ValidatorOneValidSignature) Init(stub shim.ChaincodeStubInterface) ([]byte, error)
Init is called once when the chaincode started the first time
func (*ValidatorOneValidSignature) Invoke ¶
func (vscc *ValidatorOneValidSignature) Invoke(stub shim.ChaincodeStubInterface) ([]byte, error)
Invoke is called to validate the specified block of transactions This validation system chaincode will check the read-write set validity and at least 1 correct endorsement. Later we can create more validation system chaincodes to provide more sophisticated policy processing such as enabling policy specification to be coded as a transaction of the chaincode and the client selecting which policy to use for validation using parameter function @return serialized Block of valid and invalid transactions indentified Note that Peer calls this function with 2 arguments, where args[0] is the function name and args[1] is the Envelope
func (*ValidatorOneValidSignature) Query ¶
func (vscc *ValidatorOneValidSignature) Query(stub shim.ChaincodeStubInterface) ([]byte, error)
Query is here to satisfy the Chaincode interface. We don't need it for this system chaincode
Source Files