Hyperledger 2.0 offers more options for implementing smart contracts and further decentralizes governance.
Parameter setting, installation, execution, update … The management of smart contracts evolves on Hyperledger Fabric with the switch to v2.0.
On the governance part:
- With previous versions, an organization could, on its own, define the parameters applicable to all other members of its channel.
This centralized model remains supported, but is now accompanied by a decentralized mechanism which makes it possible to condition the setting of a smart contract to the agreement of several organizations.
- In the same vein, we can now require that a minimum number of organizations approve updates to the smart contracts.
- No need to restructure or reinstall a smart contract in case of update of certain elements. As it happens :
1) Approval policies
2) “Collections”, intended to establish private channels for sharing data between members of a channel
- To simplify inspection, smart contracts are packaged as tar files.
- Traditionally on Hyperledger Fabric, each smart contract has a name and version number specified at installation.
V2.0 allows you to deploy multiple versions of the same smart contract on the same channel – or on several channels – with different names.
- Organizations that are members of the same channel can adapt a smart contract to their needs, as long as consensus on the resulting transactions is reached.
Smart contracts “As a service”
On the implementation part:
- Nodes no longer necessarily need to access a Docker daemon for the development and execution of smart contracts.
- The execution of smart contracts can be done in other environments than Docker containers *.
- It becomes possible to perform smart contracts as an external service, for example in a Kubernetes pod.
Hyperledger Fabric also introduces improvements in data sharing. Among others:
- Approval policies at the collection level (they take precedence over the policies defined in the smart contracts)
- An API to control the integrity of data exchanged with an organization that is a member of a channel but not a member of a collection
The process of updating to the latest version of Hyperledger Fabric now has a dedicated section in the project documentation.
* With v2.0, Docker images use Alpine Linux, a lightweight security-oriented distribution.
Logo © Hyperledger