HashnStore: Q1 2020 Update

You are viewing an older update. There is a newer update available.
Previous Update: HashnStore: Q1 2020 Update

You can read our Q1 2020 Update below.


Before starting our update, the HashnStore’s team hope that you are safe during this pandemic period.

Here is our Update for Q1 2020.

ECE Courses S1 2020

We have given an introduction course of 15 hrs to 3 groups of 30 students each these last months. The course was split between a theoretical part (6 hrs) and a practical part (9 hrs). During this practical session, we have used Factom technology for 2 groups and Ethereum for 1 group. For the students using Factom we have introduced the use of FAT. We have concluded last week this course with a test.

Overall, this first teaching experience of the blockchain technology and more specifically Factom has been very positive. We have already been solicited to teach once more next year and to think about extending our courses. This will (could?) be a good opportunity to test in real life the FAT technology and to help create pedagogical material to promote it.

Moreover, this course has been given (for the Ethereum) with our research partner in the energy field EIFER.

To be noticed, we managed to conclude our courses in spite of the covid19 crisis which has strongly impacted France for 2 months now.

FAT test contribution

In order to prepare this practical part, Frédéric has been testing several features of FAT. He has been regularly in contact with the FAT team. Together, they have been able to stress FATD quite extensively. As a result, some minor flaws have been found and fixes were quickly pushed. We are still looking forward to work with the extensive contract publishing API available in the CLI. A special thank for Adam who did a very good job, almost entirely on its own.

Academic contacts

As mentioned in our previous update, we started discussing with a researcher from a French reasearch institute working on Verifiable Credential to look after a potential collaboration. They have been working on the topic for several years. A second meeting with the whole group of researcher and with Valentin from Factomatic should have been held beginning of March but we got no news from them recently. The covid19 pandemic has certainly not helped here. We are going to try to contact them again after the end of the lockdown in May.

HashnStore project: Validity

We have started presenting our solution and got very good feedback especially from one potential customer. We hold three meetings with them and started to adapt our solution to their needs. Unfortunately, the recent crisis changed their priority and has stopped the project for now. They are still interested to brainstorm with us later this year.

Lawyer collaboration

We are still in contact with a (top) lawyer specialized in blockchain technology and GDPR. We currently maintain this relationship in the context of our project Validity. We are ready to leverage this contact for the Factom ecosystem if needed.


We are now at an efficiency of 30% since mid of October 2019. We plan to maintain at this level for the next months.
We would like to remind that while the token was much higher in value and while many parties decreased their efficiency during these days, we maintained our efficiency at 50% from our onboarding till October 2019. Now that the impact of an efficiency decrease is much less important in dollar terms and as we observe some interest for our solution, we do consider this is the best move for ourselves and the protocol with a limited impact.

Infrastructure Contributions

HashnStore continues to be responsive on Mainnet in case of alerts or updates and continues to dedicate 4 nodes. HashnStore dedicates 3 Nodes to the Tesnet and also 1 FATD node.

Standing system

We have put in place an internal procedure to assess every 2 months the standing of each ANO. We publish here our score grid. We base our scores on 4 different categories: Operations, Governance, Efficiency and Contribution (outside grant work). Each category has a weight of 25 points. You need 40 to get our support.


Could you comment on what sets out validity compared to the DID(-auth), VC and signing work that is being created open-source. Last time I understood the lowering of efficiency was primarily to finance the proprietary work for Validity. I am trying to ascertain what it is that makes it stand out compared to the identity server, authentication integrations, VC storage and verification portals for signature checks including VCs, open-badges and Factom signing standards, not to even mention other parties that have created and funded proprietary solutions like these outside of the protocol?
You are viewing an older update. There is a newer update available.