How our Application Works?
- hyperledgerfabric
- 9 Oca 2020
- 4 dakikada okunur
· The customer orders.
· Our system detects the legal area which is suitable to be cut according to the number of pieces and tree type by chaincode.
· It sends transaction informations to peers.
· Trees are cut in control. (Endorsers check the accuracy of this information) or sends the order to cut down the trees, if any, to the subcontractor.
· Trees are cut, cutting information is sent to the system as transaction.
· (for instance, I cut trees like this features from this coordinates and this much)
· (This transaction is added to the incoming customer order then it will be hashed so that it cannot be changed.)
· They are loaded in vehicles and sent to factories.
· (When they arrived at the factory, a new transaction can be added to the system.
· Then a value added process of the tree takes place
· (For example, 125x500mm timber board is made of timber)
· This information is sent as a transaction and added to the same chain.
· For example, timber became furniture and offered for sale in IKEA
· The customer who takes the table reads the barcode by application and sees the whole processes of the tree.
· In addition, in all intermediate operations, peers can reach the entire production life cycle of the tree. Thus, if an illegal cut is made, it will be revealed because it will not match the transaction and batch that sent. In the same way, if there is a difference in the number of trees by OGM in intermittent inspections, it can be determined and sanction can be applied since the cutting quantities of companies are certain.
· In addition, companies who want to be a trustable peer of this system can guarantee that they make their production completely in line with the order and 100% legally. This system can be legalized by a state subsidiary, or it can be necessarily enforced by the involvement of large firms as peers.
Hyperledger Fabric is a permissioned blockchain network that get sets by the organizations that contain peers. All of the peers need to a digital certificate or autorthy check. Peers in an organization can send or receive transaction invocation requests from other peers inside the organization, and to them. Chaincode (similar with Smart Contract in block chain) signed digitally in peers causes to initiate transaction request. All the peers maintain their one ledger per channel that they are subscribed to. However, it is a difference between a block chain and Hyperledger Fabric which is Hyperledger Fabric blockchain network peers can have different roles.
First of all, peers can have the role as Endorser Peer which validates the transaction by checking certificate details and roles of the requester, and executes the chaincode and simulates the outcome of the transaction without updating the ledger. After controlling these informations, the Endorser may approve or disapprove the transaction.
Secondly, peers can have the role as Orderer Peer which is considered as the central communication channel, and responsible for minning. However, the mining process is not work as in Blockchain Networks. Additionally, peers can have the role as Commiter which is responsible for updates and broadcasting the updates to the other peers in the organization.
1- The Hyperledger Fabric Network Representations
For our Hyperledger Fabric based solution we define;
· Countries as Channels
· Regions of Provinces’ Directorates of Forestry as Organizations
· District’ Directorates of Forestry as Endorser Peers in Organizations
· Companies that serving in a Organization as Normal Peers
· General Directorate of Forestry, in Turkish Orman Genel Müdürlüğü(OGM) as Orderer Peer, and Endorser Peer as well
In the Figure 7, peers of the province Muğla organization can be seen. Additionally, ın Figure 8, example organizations in channels can be seen.
In our Application an example transaction (T1) can be sent through the channel. This transaction can should be either customer request or sub process entries such as logging info, or wood handling operations. An example transaction can be T1=<PeerID, ChaincodeID, TimeStamp, TreeType, TreeAge, TreeSize, Quantity, LocationID>.For requester peers LocationID can be irrelevant. Therefore, when endorser peers run a chain code PeerID is an important term to control to make connected operations in Chaincode.
Furthermore, some sub processes can be handling of material. For example, a company may produce 1250x2440mm wooden panels with 11mm thickness. This example’s transaction can be T2=< PeerID, ChaincodeID, TimeStamp, TreeType, ProductModel, ProductSize, Quantity, LocationID>. For this type of peers’ transaction can be controlled by endorser peers by running different type of a chaincode while following transaction’s ChaincodeID.
Whereupon, transactions checked by endorser peers by running a chaincode (similar to smart contract), if its acceptable they endorsed the transaction and send to commiter peer to decision.
Commiter peer collects endorsed transactions and check them if they are valid or not. Then, transactions sent to orderer peer to be minned and added to previous block. Orderer peer runs a consensus algorithm to mine the transaction.
All of the transactions added on previous block. Herewith, following an information into the production process is getting easy, and the information cannot be manipulated between operations. Additionally, each of the peer perform its own check to see if the data comes with the batch is same or not. Therefore, it is easy and less costly to detect any misuse in logging sector.
Furthermore, all the peers in our block chain network must have a Digital Certificate which contains their private keys to be used in encryption and public keys for decrypt the information into system. For that reason, the authority, in our case OGM, is responsible to this event.
All the transactions into the system encrypted by peer’s private key, and decrypted when it is needed like in the cases of endorsing operations and so on. Hereby, the data into the network cannot be manipulated between the peers.
Remarkable!