Skip to content
Blockchain Certification

JusticeChain: Using Blockchain ⛓️ to Defend 🇵🇹 Justice Knowledge


This function focus on the auditability of information devices at the community administration. On these units, end-customers complete actions that depart digital traces. These kinds of traces are recorded and stored in log files (or audit logs), which are analysed when essential.

JusticeChain proposes employing blockchain certification know-how to make the storage of access logs much more resilient although supporting this kind of a multi-stakeholder scenario, in which different entities have distinct entry legal rights to data. 

Why the will need for this pricey know-how? In the circumstance of the Portuguese Judicial technique, there are various stakeholders with diverse belief stages, that’s why justifying the utilization of a technology that decentralizes rely on.

The blockchain certification components have two components:

1) The log manager aims to make it possible for an details program to shop applicational logs, collected by an oracle. The oracle captures logs from an info program and redirects them to the JusticeChain consumer.

2) The audit supervisor lets approved entities (e.g., auditors) to retrieve the contents of the blockchain certification (i.e., audit logs, transaction heritage). It is accessible by auditors and network admins.

The only entities that can generate audit logs are Loggers (loggers can not update or delete them). Auditors and Network Admins can see the audit logs they are entitled to analyse, but can not make, delete or update them. The blockchain certification components are executed with NodeJS and the Hyperledger Composer API (shortly offered on my Github).

The blockchain certification parts are implemented with Hyperledger Composer. Hyperledger Composer is an abstraction created on leading of Hyperledger Cloth and would make the chaincode development a lot easier. 

The facts design embedded in the Composer definition is the pursuing:

The asset to shield, Log, can be of unique styles. A Logger creates Logs, and an Auditor can access logs, based on the permissions. Administrators from diverse stakeholders manage the Logger and Auditor entities in a dispersed way (i.e., control their attributes and permissions).

Chaincode published in Javascript implements the logic described over, and Composer entry control rules enforce the constraints about the –audit logs’ accessibility.

Regarding the blockchain certification solution, we have a consortium formed by four organisations (A, B, C, L), operating on channel C1. The network has an orderer O, which follows community configurations NC, and belongs to organisation L. There are two chaincodes put in on friends.

Chaincode S1 allows peer nodes to query audit logs, when chaincode S2 enables peers to create applicational logs. For that reason, only peer nodes that correspond to Loggers should have S2 installed. L-CA is the certificate authority, managed by the major organisation, L. A certificate authority concerns cryptographic identities for all participants on the network. Ultimately, the blockchain certification consumer factors are linked to the blockchain certification (through channel 1).

In the next post, much more specifics about the blockchain certification and blockchain certification customer elements will be offered and analysed, as very well as our analysis methodology (spoiler, working with Caliper).

Many thanks very significantly for looking through 🙏. You Rock 💪