Consensus Networks Q4 2019 Report

You are viewing an older update. There is a newer update available.
Previous Update: Consensus Networks Q4 2019 Report

It has been great to see all of the developments made on PegNet and other projects throughout the ecosystem within the last few months and some congratulations are in order for everyone across the community who has been contributing to these efforts. As 2019 comes to a close, we are more excited than ever about the 2020 prospects for Factom as these efforts continue to grow and evolve. While primarily functioning as an infrastructure ANO, we wish to also assist in making technical contributions to the protocol and efforts to grow the Factom community. Outlined below is a progress update on the contributions we pledged to Factom as an ANO and other efforts we have taken on using Factom over the last quarter. We have funded everything to date out of our own pockets and are proud to be contributing to the growth of the network.

We have maintained 100% uptime on all of our servers since being elected into the active set. We are currently operating two mainnet servers across two different data centers with backups and two testnet servers.

HealthLink (Healthcare SBIR):
As we mentioned in our last update, through a Phase I SBIR through the National Institutes of Health (NIH) we have been building out a population health data sharing platform utilizing Factom as a backend ‘source of truth’. We are still awaiting the results of our Phase II submission, which has slowed down some of the technical development of the product. Phase II is a two-year grant with significant funding for completing R&D for a V1 product and commencing commercialization so we have been focusing on finding and solidifying commercial partnerships in the enterprise healthcare space to pilot our technology and help with distribution while we wait for the NIH to get back to us. We plan to continue commercializing this product regardless of Phase II outcome. However, given the magnitude of funds available should we be awarded the grant we are just trying to allocate our resources appropriately and make sure we optimize our development timeline and product roadmap. We promise to share updates with you all as we are able, and are excited to be advancing this project and Factom alongside the NIH and the possibility of bringing the protocol into health systems across the U.S.

Scribe (Factom/Twitter):
With our technical load from the HealthLink project reduced we were able to focus more effort on this project and are excited to announce that we have successfully developed a dockerized MVP of the product! In its current form there is one docker image to run a native web application where you can input a twitter handle and twitterid for an account and another to run the daemon that will begin asynchronously processing the ~2000 most recent tweets for the account and writing them to Factom and spin up a Stream listener that then tracks the account and writes any tweet an account posts from that point on to the Factom Blockchain. In its current form it can track as many accounts as you wish and it will asynchronously process requests for all of them and each account is written to its own chain. While still very much a work in progress, we are excited about the possibilities that something like this could have given recent tweets from Jack Dorsey ( ) & Balaji Srinivasan ( ). We are still trying to identify what the final commercial use case for something like this, so any suggestions/input from the community is welcomed! If you want to play around with the current version or hack on it yourself the GitHub repo is here:


In addition to our progress on our proposed ANO contributions we have made several other contributions to growing the Factom community in several other ways and identified other projections which we will explore using the protocol for. Again, these efforts have been entirely self-funded to date and we are excited about contributing to Factom.

We joined the Orax mining pool and have been running miners for PegNet on our data center infrastructure. We currently have 6 CPUs dedicated to PegNet and are excited about the future prospects of the protocol! We will look to continually support the Pegnet effort by contributing miners and other help where we can and are eager to see how this project continues to grow in 2020.

In December we were awarded an SBIR Phase I Grant through the Air Force AFWERX program to investigate using blockchain for managing software chains of custody. Our proposal for the grant was also predicated on technologies we had developed through our Phase I grant for the NIH, which uses Factom for secure data sharing. While the Phase I of this grant is intended primarily for finding an Air Force customer and identifying their needs, we believe this could be a well suited use case for Factom and are excited about the possibility of being able to use the protocol to secure DoD software chains of custody!

During our work on the Healthcare SBIR project we are using Factom for, we found it necessary to port the factomd library into the asyncio library for python to accomplish some of the compute tasks necessary to finish the software. We are currently in the process of finishing up documenting this library and will be open-sourcing it to the community! We hope that this will help make it easier for others in the community and elsewhere to asynchronously interact with the Factom blockchain to create more robust applications and increase adoption by developers for use in other web applications.
Thank you for your update, the work with Healthlink and Scribe is impressive.

I would be interested to better understand your work on DoD software chains of custody and wonder what other similar applications there may be.

What are you doing to explore the applicability of your Healthlink Project in other countries?
Hi Mike, thanks for your reply!

In terms of chains of custody, the real use case we're pursuing is what people call DevSecOps or basically methods of securing the software development process to prevent tampering and control access while allowing an agile process to continue - something the DoD is very keen on. Happy to talk in more detail on this if you'd like.

We haven't had the opportunity to explore applicability of HealthLink (now HealthNetTM)outside of the United States yet due to our own time constraints but we would definitely be interested in learning the landscape and pursuing opportunities there. We're currently looking for one or two solid test use cases to demo what we've built, which I think will help make this tech more understandable to the greater medical community. Any ideas or collaboration efforts would be greatly appreciated!
Hi Nate,

Thank you for the information. The DevSecOps sounds interesting and I suspect there other areas where the prevention of tampering with software development would be very valuable (the Nuclear industry for example).

As for HealthNetTM I think there may well be applications in the UK, I'll PM you to discuss.
You are viewing an older update. There is a newer update available.