Hyperledger Unveils Aries, a Suite Of Tools Facilitating Blockchain Interoperability

Hyperledger launched a series of “Hyperledger Aries” tools targeted at interoperability of distinct kinds of blockchain-based information. Hyperledger already operates the Hyperledger Indy identity endeavor underpinning Sovrin Network. In the future, Indy’s insistence will be on blockchain or backend side. But little is recorded on a blockchain for decentralized identities.

Almost all of the features lies around the customer end: communication between organisations and people, and how people handle their wallets.

This project is now running in Hyperledger Aries. Hyperledger Aries is a collection of tools that allegedly allow blockchain-based information exchange, support peer-to-peer (P2P) messaging, and enable dealings between distinct blockchains as well as other distributed ledger systems Hyperledger implemented the plan to provide software for P2P communication and promote interoperability.

The software comprises of a blockchain interface layer, cryptographic wallet, encrypted messaging scheme, application programming interface-like real world scenarios and other tools Hyperledger claims Aries isn’t a blockchain, not an app.

Instead, it offers necessary framework to creating apps. There’s also a stark reality that there won’t be one identification network, there will be numerous, and interoperable. Aries also tackles this. The Aries group, supported by Sovrin Network, has got in touch with decentralized identity projects based on Ethereum and W3C partakers to add to Aries ‘ code.

Hyperledger Aries intends to offer a wallet and an encrypted messaging mechanism for apps to interact with wallets. In addition, a Zero-Knowledge-Proof (ZKP) will also be available. A system to create and sign blockchain dealings and a Decentralized Key Management System (DKMS) will exist. And API-like use instances can be built depending on Aries features.

There are also plans for a memory layer to store photos, health documents, or other private data. There’s an assertion that Hyperledger Indy was divided into two, with Aries ‘ customer features being interoperable with non-Indy-based networks.

Straightforwardly, Indy has two types of features. Blockchain or server / backend side, and customer side, or what’s going on in applications. Blockchain has restricted features. It holds public decentralized identities (DIDs) of various organizations. Thus, individuals can guarantee that the documents were signed by these organisations.

Therefore, a Hyperledger Indy blockchain would consist of organization DIDs, formats for distinct information types such as passports or university qualifications, and a connection between the organisations and the formats they promote. There are also cancellation registers for expired and similar passports.

In February, Intel, a participant of the Hyperledger collaborative effort, introduced a commercial blockchain bundle based on the Hyperledger ecosystem engineered for companies wishing to deploy their own blockchains. Last December, Ursa project, a modular cryptography software library was endorsed by the Hyperledger Technical Steering Committee.

Ursa is intended to prevent wasteful effort on duplicate initiatives, improve safety by simplifying assessment and making it ‘ less probable for less skilled individuals to generate their own less safe applications.’

That same month, Hyperledger attracted 12 fresh participants, including Alibaba Cloud, a subsidiary of the e-commerce multinational; financial services institution Citigroup, Deutsche Telekom, one of Europe’s largest telecom firm; and we.trade, a blockchain based finance related platform.