Why a twelve Word Mnemonic is an Insecure Bitcoin Wallet Backup Rewind back to two thousand ten and the way Bitcoin wallets worked. Users had a wallet.dat file on their computer with their private keys on it. They could optionally add a password to encrypt it. They SHOULD back up the file in case they […]
Visualizing Blockchain Operations with Hyperledger Explorer
Register to view the contents
Why Explorer was incubated
The Hyperledger Project has steadily grown since its founding in December two thousand fifteen and now reaches more than one hundred thirty organizations. Its development community has incubated eight projects to date: Fabric, Sawtooth, Iroha, Burrow, Indy, Composer, Cello, and Explorer.
Today, we’ll concentrate on the latter one and its critical capability to permit users to see what’s happening on their Hyperledger blockchains.
According to its description by the Hyperledger project, Explorer is designed to create a user-friendly web application that can view, invoke, deploy, or query:
- transactions and associated data
- network information
- transaction families
- any other relevant information stored in the ledger
IBM, Intel, and DTCC (a clearing and settlement company in the financial services industry) were its initial contributors, as they had all developed explorer projects on their own. Rather than rival and waste time, they combined their efforts to create the Hyperledger Explorer incubation.
The three companies all arrived at the idea of creating an explorer more or less at the same time from a common need to see what was going on in the Hyperledger Fabric and Sawtooth frameworks. Developers needed to be able to find and view ledger information, and interact lightly with it. The concept is no different from the explorers found on Windows or Mac desktop systems. Flying blind is never the way to go.
As described in the DTCC proposal, Explorer comprises six major components.
Key components are as goes after:
A web server. Knot.js is proposed as a back-end framework for implementing server-side components. Express Knot.js serves a web application.
A web UI. With AngularJS, the front-end framework will be implemented. According to the proposal, Angular’s “features like data-binding and directives greatly help in developing reusable components and modular code.” Bootstrap is also used “for its rich UI and responsive features.”
Web sockets. This key API shoves information from the server to clients, and thus “reduces flow on clients and server.”
A database. Information about blocks, transactions, clever contracts, etc. is stored in this RethinkDB.
A security repository. “User identity and access management will be implemented using a federated security repository,” according to the proposal. “This will (serve as) a facade for security implementations from different blockchain platforms.”
Blockchain implementation. Each blockchain must have a separate component “to provide updates on transactions, blocks, knot logs, and clever contracts to the Explorer web server,” as the proposal goes. This can be done via web sockets.
The DTCC proposal also features numerous diagrams of how transactions, knots, brainy contracts, and other aspects of Explorer will work. Here is the process of getting transactions activity.
One can also take a look at transaction events activity flow.
In the DTCC proposal, there are also numerous diagrams on API workflows: chain info activity, blocks data model, knot logs activity, etc.
Unified enterprise-level visualization
Explorer thus adds an essential element to operations in the world of private enterprise blockchains and is meant to be a valuable instrument when blockchain’s immutable ledger needs to be accessed and examined.
Brian Behlendorf (Executive Director at Hyperledger) and Dan Middleton (Venture Technical Lead at Intel) voiced their enthusiasm for Explorer when it was very first announced.
“We are turning towards this idea that Hyperledger can be a home for a number of different projects with different concentrates, with different priorities, with different agendas, all collectively connected by this concept of blockchains, distributed ledgers, and brainy contracts.” —Brian Behlendorf, the Hyperledger Project
In the high-level Explorer proposal, the three companies “seek to consolidate the best of the various contributions into a single, collective UX/UI to visualize the state of the blockchain.” They’re working on a minimum viable product (MVP) to have pluggable API support for Fabric and Sawtooth. Initial release is yet to happen, but aims to be compatible with the emerging Fabric v1.0.
Anyone interested in digging into this project and becoming involved with it can check out its JIRA tracker, GitHub repo, or documentation.
Now, it’s up to the community to see how the project will play out, and if it accelerates blockchain adoption within enterprises through unified visualization.
Other Hyperledger incubations: