package protos

Get desktop application:
View/edit binary Protocol Buffers messages

CDSData is data stored in the LSCC on instantiation of a CC for CDSPackage. This needs to be serialized for ChaincodeData hence the protobuf format

• bytes hash = 1

  hash of ChaincodeDeploymentSpec.code_package

• bytes metadatahash = 2

  hash of ChaincodeID.name + ChaincodeID.version

ChaincodeData defines the datastructure for chaincodes to be serialized by proto Type provides an additional check by directing to use a specific package after instantiation Data is Type specific (see CDSPackage and SignedCDSPackage)

• string name = 1

  Name of the chaincode

• string version = 2

  Version of the chaincode

• string escc = 3

  Escc for the chaincode instance

• string vscc = 4

  Vscc for the chaincode instance

• bytes data = 6

  Data data specific to the package

• bytes id = 7

  Id of the chaincode that's the unique fingerprint for the CC This is not currently used anywhere but serves as a good eyecatcher

Specify the deployment of a chaincode. TODO: Define `codePackage`.

• optional ChaincodeSpec chaincode_spec = 1

• bytes code_package = 3

ChaincodeID contains the path as specified by the deploy transaction that created it as well as the hashCode that is generated by the system for the path. From the user level (ie, CLI, REST API and so on) deploy transaction is expected to provide the path and other requests are expected to provide the hashCode. The other value will be ignored. Internally, the structure could contain both values. For instance, the hashCode will be set when first generated using the path

Used in: ChaincodeSpec

• string path = 1

  deploy transaction will use the path

• string name = 2

  all other requests will use the name (really a hashcode) generated by the deploy transaction

• string version = 3

  user friendly version name for the chaincode

Carries the chaincode function and its arguments. UnmarshalJSON in transaction.go converts the string-based REST/JSON input to the []byte-based current ChaincodeInput structure.

Used in: ChaincodeSpec

• repeated bytes args = 1

• map<string, bytes> decorations = 2

• bool is_init = 3

  is_init is used for the application to signal that an invocation is to be routed to the legacy 'Init' function for compatibility with chaincodes which handled Init in the old way. New applications should manage their initialized state themselves.

Carries the chaincode function and its arguments.

• optional ChaincodeSpec chaincode_spec = 1

Carries the chaincode specification. This is the actual metadata required for defining a chaincode.

Used in: ChaincodeDeploymentSpec, ChaincodeInvocationSpec

• ChaincodeSpec.Type type = 1

• optional ChaincodeID chaincode_id = 2

• optional ChaincodeInput input = 3

• int32 timeout = 4

Used in: ChaincodeSpec

• UNDEFINED = 0

• GOLANG = 1

• NODE = 2

• CAR = 3

• JAVA = 4

LifecycleEvent is used as the payload of the chaincode event emitted by LSCC

• string chaincode_name = 1