IT-SDK-Hyperledger-Fabric-Dev

Resources Allowed for Certification

Hyperledger Fabric

• https://hyperledger-fabric.readthedocs.io/en/release-2.2/ (Documentation)
• https://hyperledger-fabric.readthedocs.io/en/release-2.2/command_ref.html (Command Reference)
• https://hyperledger.github.io/fabric-chaincode-node/release-2.2/api/index.html (Fabric-Contract API)
• https://hyperledger.github.io/fabric-sdk-node/release-2.2/index.html (Fabric-Application API)
• https://wiki.hyperledger.org/display/fabric/Hyperledger+Fabric (WIKI)

Node.js / JavaScript

• https://nodejs.org/docs/latest-v12.x/api/ (Node.js)
• https://developer.mozilla.org/en-US/docs/Web/JavaScript (MDN)

Components

• Info: Actor/Participants are peers, users, orderers.
• Info: Every actor/participants has an identity certificate.
• CA (Certificate authorities): Issue identities by generating public and private key forming key-pair that can be used to prove an identity.
• MSP (Memberahip Service Provider): contains a list of permissioned identities (public keys).
• Channel:
• Smart-Contract: defines business logic
• Chaincode: A Smart-Contract packaged in a Chaincode then deployed to blockchain-network.
• Blockchain-Network:
• Orderer:

Begriffe

• Leger: Record all state transitions, result of chaincode invocations "transactions".One Leger per Channel. Ledger consists of (world state/blockchain)
• blockchain: is the main part of the ledger. is immutable (unchangeable) und stores the full history of assets modifications.
• World-State: is a database that represent the current values of ledger states.
• Chaincode:
• Client Application: interact with blockchain network on behalf of useres.
• Wallet: contains a sset of user identities to connects to a channel
• Gateway: manges the network interactions on behalf of application.

Chaincode Deployment

• Package the chaincode.
• Install the chaincode package.
• Approval the chaincode definition.
• Commit the chaincode defintion to a channel.

Chaincode Upgrade

• Repackage the new chaincode.
• Install the new chaincode package.
• Approval the new chaincode definition.
• Commit the new chaincode defintion to a channel.

Commands

peer lifecycle chaincode package $PACKAGE_NAME.tar.gz --path $PATH_SOURCECODE --lang $LANG --label $LABEL
peer lifecycle chaincode install $PACKAGE_NAME.tat.gz
peer lifecycle chaincode queryinstalled
peer lifecycle chaincode approveformyorg --orderer $ORDERER --channelID $CHANNEL_ID --name $CHAINCOD_NAME --version 1.0 --package-id $PACKAGE_ID --sequence 1
peer lifecycle chaincode checkcommitreadiness --channelID $CHANNEL_ID --name $CHAINCOD_NAME --version 1.0 --sequence 1 --output json
peer lifecycle chaincode commit --orderer $ORDERER --channelID $CHANNEL_ID --name $CHAINCODE_NAME --version 1.0 --sequence 1 --peerAddresses $PEER_ADDRESSE
peer lifecycle chaincode querycommitted --channelID $CHANNEL_ID --name $CHAINCODE_NAME
peer chaincode invoke/query --orderer $ORDERER --channelID $CHANNEL_ID --name $CHAINCODE_NAME --ctor $MASSAGE

Functions

ctx.stub.getState(key);
ctx.stub.deleteState(key);
ctx.stub.putState(key,value);
ctx.stub.getStateByRange(keyFrom, keyTo);
-------------------------------------------
ctx.stub.createCompositeKey(objType, [key]);
ctx.stub.splitCompositeKey(key);
ctx.stub.getStateByPartialCompositeKey(objType, []);
--------------------------------------------
ctx.stub.getQueryResult(queryString);
ctx.stub.getHistoryForKey(compositeKey);