Post #19892

Signature not verified

This entry might be using an old signature, or it was signed by a key that does not exist on the server.

The entry content as it exists in the database. This should be verified against the blockchain entry.
Consensus Networks: Consensus Networks Q3 Quarterly Report July-September 2019

We’re excited about the future of Factom and are continuing our push to help further develop and evangelize the protocol. While we are primarily an infrastructure ANO, we desire to make both technical contributions to the protocol and help grow the Factom community. Outlined below is the progress on the contributions we pledged to Factom as an ANO and other significant projects 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 this outstanding protocol.

In July/August we completed significant infrastructure deployments for supporting our ANO operations and have maintained 100% server uptime since then. (We did lose a docker container last week due to the ‘Pokemon’ bug).

Healthcare SBIR:
We have been keeping this under wraps as a surprise to the community, but are pleased to announce the successful completion of our Phase I SBIR through the National Institutes of Health (NIH) as well as the submission of our Phase II application. This effort took much of our time in August and September and we are excited to share some details, including that the platform is built utilizing Factom as a backend ‘source of truth’ for sharing patient data between hospitals and key stakeholders. Phase II is a two-year grant with significant funding and we will receive feedback in November on our application with a chance to reapply if not awarded. We will be releasing a whitepaper in the coming weeks with more details and technical specifications. We have had serious interest from healthcare enterprises and providers to continue the commercialization of this product and intend on doing so regardless of Phase II outcome. We will share updates with you all as we are able, and are excited to be advancing this project and Factom alongside the NIH. If successful, this project could bring Factom into health systems across the U.S and we are eager to be bringing this product to market.

Our focus on our NIH grant left us less time to work on our Twitter project however we were still able to complete a basic MVP that has a user interface with a basic form - list layout that allows you to insert a twitter handle and ID and begin writing tweets to Factom and tracking their account. This can be done for as many accounts as you wish to track. The Github repo and instructions for how to use the software can be found here. [[URL][/URL]] We’ve run into some trouble fully dockerizing it, however, it’s at a point where we can start to do some customer validation and will be focusing on the user experience over the next quarter and building out a consumer-facing portion. We will continue to update the community as we make more progress on this project and advance the consumer-facing portion. With the SBIR Application out of the way, we intend on making significant headway on this project over the next quarter and are eager to be bringing products to market using Factom.

SIMBA Chain integration:
We are continually moving forward in our talks with SIMBA Chain to add Factom to their platform. We haven’t officially agreed to the details, however, they’ve expressed significant interest in adding Factom to their standalone platform as well as their Smart Contract as a Service platform on Azure. Their platform will be a great addition to the Factom universe and will continue to make us more attractive for government applications. They are currently on Azure and their platform makes smart contract and decentralized application development much simpler through an easy to use drag and drop UI that then generates the corresponding code to integrate with your application. They have over 1000 developers on their platform currently and are expanding. We believe this presents an attractive opportunity to promote Factom to more developers and increase the number of applications using Factom, thus promoting adoption. We will continue to post updates as we move forward in our conversations with them.


In addition to our progress on our proposed ANO applications we have contributed to growing the Factom community in several other ways, both technical and otherwise. Again, these efforts have been entirely self-funded to date and we are excited about contributing to Factom.

We have aided in the Pegnet effort by running a miner on our physical infrastructure to ensure it is running at all times in a secure environment. We plan to continue running our Pegnet miner in this environment in the future and as the network continues to grow will increase our contributions here as needed by the community.

Marketing/Community Outreach:
Connor joined the FactomProtocol blog and has written two articles thus far. One pertains to the applicability of Factom in Regulated Industries and the other contrasts Factom from Hyperledger and expounds upon why Factom is a superior choice for enterprise. Connor plans on continuing contributing to the Factom Protocol Blog to promote spreading the word about the protocol and its value as an enterprise blockchain solution.

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.
This is the raw content, without BBCode parsing.