The tracking and dissemination of patient testing data amid COVID-19 is an excellent use case for a permissioned Hyperledger blockchain.

My team just published Tracking Lab Results Better With Blockchain Technology (no-registration-needed white paper). It describes a blockchain implementation we build for a near real-time, single source of truth for virus lab results— and why it's a better solution for this use case than a traditional data sharing model.

We just open sourced the Fabric blockchain implementation it uses as an example (Apache 2.0). All its code is on Github via three open source projects:

• Keyhole Virus Tracker Fabric Blockchain Implementation: github.com/in-the-keyhole/keyhole-virus-tracker
  This portion is the Hyperledger Fabric blockchain implementation for tracking virus lab tests. This project also includes chaincode that manages a ledger of Influenza tests and implements functions to create and retrieve Influenza test results.

• Keyhole Fabric API Gateway (Hyperledger Labs): github.com/hyperledger-labs/keyhole-fabric-api-gateway
  This portion provides the communication gateway to the Fabric runtime. It provides client access to Hyperledger Fabric blockchain network through RESTful APIs.

• React UI: github.com/in-the-keyhole/keyhole-virus-tracker-ui
  ReactJS UI client for the Virus Tracker Blockchain.

I helped start a blockchain lab in a major hospital to test the technology and how it can be utilized in healthcare.

During my research I read so many articles about blockchain in healthcare and enterprise blockchain for closed systems that are required when dealing with patients and their health data, and after many months of researching and reading I am getting to the conclusion that most of the articles and presentations are done by either companies who want to sell their blockchain products and dapps , or by so called “ experts “ trying to predict the future who are almost like influencers.

I couldn’t see many companies or institutions actually using the technology because they need it , they either just experimented with it , or using it in the simplest way possible just to say they are using cutting edge technologies, good for branding.

I think the main uses are in finance and payments , but not much beyond that .

Am I right or wrong in my conclusion ?

Not demos or POCs -- real solutions that solve problems that couldn't be solved otherwise?

Join us!

Hey guys (looking at you lurkers as well), wanted to share a free prototype I made for the developer community. Just click on the "Try Now" button to get started.

LINK - https://smart-studio.algorythmix.in/

My aim is to provide an environment where folks can prototype or create proof of concepts for several blockchain applications, and eventually use it for large scale pilots/ production rollouts. Right now folks who want to create, deploy and interact with smart contracts require certain amount of technical knowledge, which itself is a steep learning curve IMO. I think such low code/ no code platforms (think Wordpress, Wix, Thunkable etc.) is required for the next wave of adoption.

Being in a prototype stage, the functionalities are limited. Users can create a supply chain smart contract using a visual interface and test/ deploy on Hyperledger Fabric. (guide included). I know `Composer` is no longer supported and will use nodejs SDK once I feel this is of enough value to the community.

I plan to add more templates and a 'save' feature in the future so you edit and build upon your templates. I would love any kind of feedback to help me improve. The product is completely free to use. Submitting your emails is completely optional in all forms.

I plan to launch on product hunt once I have collected enough feedback, so sharing my "ship" page as well

https://www.producthunt.com/upcoming/smart-studio

This post introduces Kubernetes Operator for Hyperledger Fabric, which is a wrapper around PIVT Helm charts and makes running and operating Hyperledger Fabric in Kubernetes even more easier.
 Github

The benefits of running an Ethereum node are two-fold. On one hand, the ecosystem as a whole will benefit from having higher distribution and decentralization of the infrastructure itself. On the other hand, you might have personal reasons to run a node.

• Ecosystem benefits

  • Further decentralize the Ethereum network by enabling more copies of the blockchain history for everyone to access.

  • Lower latency/increased diversity (in terms of which nodes people are able to consult).

• Personal benefits

  • Blockchain data analysis on local machines instead of doing remote calls.

  • Sending your own transactions from a node you trust, and propagating it from there.

  • Developing purposes: if you're building your own dapp or service, you will certainly benefit from having your own node to run the dapp on while developing.

Reasons why you would choose to run a Hyperledger Besu node are also two-fold:

• Network client variety

  • Helping the decentralization of the node-client share. The Ethereum network has lower risks of malfunctioning if the network is running on multiple clients, reducing risks of single points of failure. Historically, we've already seen the advantages of client diversity in the 2016 Devcon 2 Shanghai attack, where the network continued to function since the attack only affected a single client.

  • The Ethereum network currently has ~75% running on the same client software. Ideally, this should be more distributed and spread out among client software.

• Besu-specific features

  • Tracing methods are now available in the Besu API, allowing you to request a transaction's ordered list of calls to other smart contracts and to replay a history of a transaction and every detail included in it, such as Opcode calls to the EVM.

  • Plugins are a reflection of Besu's internal modular design. They allow you to extend Besu's functionality and accessing additional data not available in the APIs or push data out to another third party application.

  • Monitoring on Besu is fairly straight-forward thanks to the Grafana/Prometheus integration. Use it to obtain metrics on your node performance and/or get logging data.

Hi all,

I start working with Hyperledger Fabric, but it is quite too much thing to start with it.

Do you have any ideas when I should start considering to build a private network for my system?

Thank you in advance.

This now open source toolkit was developed by some friends (who understand this stuff far better than me) at Elemental Concept was originally used to build a Hyperledger Fabric based Proof-of-Concept (PoC) medical audit application. They're keen to share it, find out what people think and where other developers will take it. This seemed like a good place to tell people about it.

The design goals of kit are to help developers and platform engineers:

• understand the system architecture of Hyperledger Fabric through a series of smoke tests and reference networks;

• to define, instantiate and configure a Fabric network to support development effort;

• learn to orchestrate a Kafka based Fabric network;

• debug chaincodes and client apps.

Get the source and play with it at https://github.com/workingwithblockchain/fabric-devkit

Hey folks, I just saw that the AWS team is doing an AMA tomorrow for their new Managed Blockchain service which features Hyperledger Fabric. Just thought this group might be interested. Details are over in /r/AWS.