IBM Lists 5 Blockchain Rules, Says Innovators Must Remain Committed To A Set Of Ideals

IBM Lists 5 Blockchain Rules, Says Innovators Must Remain Committed To A Set Of Ideals

IBM Lists 5 Blockchain Rules, Says Innovators Must Remain Committed To A Set Of Ideals

A publication on the IBM blog on May 13 has stated that if blockchain is to move beyond the technological fringe and into the mainstream, to underpin the nexus of a more trusting and transparent world, innovators must remain committed to a set of ideals.

However, the publication further states;

"At IBM, our work has been guided by this set of blockchain principles:

(1) Open is better

(2) Permissioned doesn’t mean private

(3) Governance is a team sport

(4) Common standards are common sense

(5) Privacy is paramount"

It is no more news that IBM has been working vigorously to commercialize the technology through its enterprise-grade version of Hyperledger Fabric, known as IBM Blockchain. Hyperledger Fabric currently empowers 1300 networks in the IBM blockchain cloud, 100 of which are live in production today.

The blog post further explained the five principles;

"(1) Open is better: To promote open innovation and ensure the overall quality of code, blockchain networks must foster diverse communities of open source contributors and organizations. These are even more powerful when part of an open governance model working together under free licensing models such as Apache2 and MIT. Wherever possible, developers should avoid proprietary technologies in favor of open source frameworks with defined approaches for sharing contributions. When done correctly, open development increases innovation, while hastening time to maturity and decreasing cost.

"Example: The Hyperledger Project, operated under The Linux Foundation, is a “greenhouse” for growing enterprise-grade blockchain software with strong and diverse code contributors, and liberal licensing. Hyperledger recently added 45 new members and three of its 12 projects are now active.

"(2) Permissioned doesn’t mean private: To support an enterprise-grade platform aligned with the regulatory and fiduciary responsibilities of its participants, enterprise blockchains must be designed around the principle of permissioned and trusted access. Though anonymous public blockchains afford a number of powerful capabilities, they are not suitable for most enterprises, particularly those in regulated industries. Most organizations need to know who they’re conducting business with and that no illegal activity is being transacted over the network. However, this is not to say that enterprise blockchains must be private; instead, they should be permissioned. They may be open to anyone willing to register and cryptographically validate their identity. Common identity standards can help streamline access across multiple blockchain networks using the same set of verified credentials.

"Example: Sovrin, a digital identity management network and Stellar, a decentralized global payment platform, are examples of public, yet permissioned blockchain networks. TradeLens, a supply chain management platform built atop Hyperledger Fabric, is another example of a permissioned blockchain that grants participants visibility into who their network peers are.

"(3) Governance is a team sport: To ensure that networks serve the needs of all participants and are managed in a manner reflective of each unique use case, and to prevent undue concentrations of influence, enterprise blockchains must embrace distributed and transparent governance. Enterprises should choose a platform that automatically provides a democratic structure hardwired into the network, with privacy and permissioning features built-in. Rules governing who can join and how, should be clearly stipulated, as well as guidelines on which participants can play key roles such as ledger operators. Trust anchors, who actually run nodes in the network and participate in validating transactions, should be distributed across multiple participants. As a general rule, a trusted governance model requires at least three designated trust anchors, but networks benefit from scaling the number of ledger holders. Governance frameworks should also take into account a network’s funding model, whether it is financed by membership fees, ledger operators, or something in between.

"Example: The Verified:Me identity network in Canada, convened by SecureKey Inc, has enlisted major Canadian banks to participate as trust anchors to host nodes and validate network transactions. SecureKey has created a governance model that involves ongoing checks and balances between its constituent working groups.

"(4) Common standards are common sense: To help future-proof networks, prevent vendor lock-in and foster a robust ecosystem of innovators, enterprise blockchains should be architected around common standards with interoperability in mind. Critically, this also entails interoperability of cloud platforms; vendors should meet participants where their data already is. While most blockchain networks presently exist in siloes, it is generally accepted that the technology is evolving to support a network of networks. The first step in promoting this interoperability is to make blockchains visible to one another through a registry, such as Hacera Unbounded. In addition, blockchain networks should define and publish their data models and policies for change. Wherever possible, these should be built on industry standards, or leverage APIs with permissioned access.

"Example: Decentralized Identity Foundation (DIF) has defined a set of specifications on how to identify organizations, people and digital assets (called DIDs) that enable entities to be identified across blockchain (and non-blockchain) networks. Collaboration between Hyperledger and the Enterprise Ethereum Alliance in areas like Burrow, a modular blockchain client, and the Token Taxonomy Initiative, an effort to standardize blockchain tokens, are fostering these linkages.

"(5) Privacy is paramount: To safeguard individual and corporate data on a platform that, by definition, distributes it widely across multiple nodes, participants on an enterprise blockchain should be empowered to control who can access their data and under what circumstances. Furthermore, while no single participant “owns” a blockchain network, the rights to the data that resides on it should always belong to the creator. Any APIs should extend the same permissioned access programmatically. Blockchain networks must also abide by privacy regulations such as GDPR. In most cases, that means any personal data should be kept off-chain.

"Example: IBM Food Trust, a blockchain network aimed at ensuring food safety, freshness and sustainability enables brands like Walmart, Carrefour and Driscoll’s to leverage shared data to enact various supply-chain efficiencies while safeguarding each member’s proprietary information."


Leave a comment

Login to comment