During this quarter Luciap Technology Inc. fulfilled all the mandatory tasks that fall to Factom Authority Node Operators:
- We have participated in every vote that involved ANOs. We have also weighted our technical vision in several governance discussions.
- We have been continuously running our fleet of mainnet and testnet servers with high availability. We are generally among the very first to update to the newest factomd versions due to our involvement in the Core and code deploy committee.
Luciap is operating at 50% efficiency (unchanged since election) and here is the list of extra activities we have been performing during this quarter which we believe justify our efficiency:
- We have been providing technical support for factom.js to a company looking to integrate Factom in their wallet application.
- We released the npm package joi-factom, an extension for JOI, a popular object schema validation library. It allows to validate Factoid addresses, Entry Credit addresses and digital identity keys.
- During the first grant round of 2019 we released a small web app that helped standing parties rank the grants and facilitate good judgment.
- We published a brand new version of our experimental tool factom-storage (which allows to store whole files on Factom). We revamped the underlying design based on the knowledge we gathered during the last year working on the on-chain voting and FAT protocols.
- We made a new PR to factom-walletd to add a small feature. Not much other “core” contribution recently, but we now have some great new core developers (from grants) working full time on that!
- Additional developer time has been invested in one library and one dev tool that will be announced when finalized (nothing secret, as usual this is open-source, the work is already visible on github).
- Core and code deploy committee: as part of our continuous involvement we often act as the guinea pig for new releases both on testnet and mainnet. We also perform load testing on the testnet. And finally we participate in all internal discussions on bugs, improvements and next releases.
- We joined the on-chain governance working group meant to pave the way for a more transparent and inclusive governance (e.g involving FCT holders).
- We also joined as tech enthusiasts two technical discussion groups meant to discuss and develop new capabilities and usage on Factom.
- We updated our factom-vote library to allow the support of Ledger S when voting on MyFactomWallet. This is an additional feature that was not pledged in the grant.
- The on-chain voting grant has been officially delivered. Please read the report from our grant sponsor.
- A massive amount of our time during this Q1 2019 was spent on the Factom Asset Tokens project (FAT). At present this is the #1 project we are investing time in. As a FAT Editor we are involved in the design of the various aspects of the protocol. And as developers we are focused on building the FAT wallet: a new wallet supporting all the fungible and non-fungible FAT tokens together with the regular Factoids and Entry Credits. It will also allow you to manage your Factom digital identities. We are really impatient to present an early version to the community! We will most likely talk at length of the FAT wallet in the near future. The FAT protocol is steadily maturing and very promising.
- Since the last update the Factom Asset Tokens (FAT) project got awarded a grant by the community. This is currently the main project we are working on and it is taking up most of our time and effort. We are focusing on the development of a desktop wallet that will support all FAT tokens in one place, help you manage your digital identities and more. As all the work is open-source the development can be followed here. We are also participating in all technical discussions and FAT specifications improvements (FATIP).
- We have published our first technical and educational article on Factom. It describes a handful of common design patterns (and anti-patterns) to use on Factom. This is drawn from our experience of developing Factom libraries and working on the on-chain voting protocol and the FAT protocol. We are very happy with the reception it got and will produce more in the future.
- We have been finalizing version 1.0 of factom.js. A Release Candidate version is already available for download and we now have a full online documentation. The official 1.0 release should happen within the next few weeks and will be the results of months of refinements and feedback from users.
- We worked on a factomd issue. This is worth a look to see a good example of community cooperation: the feature request was made by an ANO member, we proposed to take on the task and Factom Inc. employees answered to our questions to facilitate the implementation. The feature will be available in the next release of factomd. Speaking of contributions to Factom software, if you haven’t seen Factom Inc. November technical update, all the “community contribution” mentions here were made by Luciap Technology 😉
- We published a version 0.2 of the factom-identity-cli. This brought UI improvements and some warnings about some common issues that can happen when using the tool (clock synchronization).
- We have been doing support for the ongoing on-chain grant. We have tweaked our JS voting library to help the integration in the MyFactomWallet UI.
- Core and code deployment committee: we reviewed the initial proposal of the Factom Improvement Protocol (FIP) produced by Niels Klomp.
We wish you all a great holiday season and we are looking forward for another prolific year of Factom development! See you in 2019!
We started this month of June by putting together an initial grant proposal: on-chain voting protocol. This grant is meant to develop a fundamental component of the Factom decentralized governance as this on-chain protocol will be used for voting subsequent grants, guide elections, amendements of the governance document, etc. It’s also worth noting that this grant is a partnership between 4 entities: the Factoid Authority, Factomatic, MyFactomWallet and Luciap. This grant proposal was submitted to the community and approved without vote against it. The actual payment of grants will happen sometimes in July. Meanwhile we have already started some planning/coordination discussions with the other teams involved in this project. The development for this grant is going to be a big part of what we are going to work on in July.
We released a straightforward web UI where anyone can see details of the identities of the authority set: https://luciap.ca/#/authority-set(if you’ve already seen it you can still have a look and see the new ANOs on-boarded the last few days) This includes in particular the efficiency of each Authority Node Operator together with their payout addresses (past and present). The goal is obviously transparency and with this info it’s fairly easy to analysis if ANOs are sticking to their campaign promises. We did our own analysis of the payout addresses of all ANOs and found that 8/11 haven’t even touched a single FCT. With this data in hands it should be fairly easy to debunk the myth that ANOs are dumping on the market ;).
Factom.js reached version 0.2.3. We got couple of new projects that started relying on it and we are very happy about that.
We extracted the core logic of our tool factom-identity-cli into a standalone NPM package factom-identity-lib which makes it reusable by any other application that would want to deal with Factom identities. This is the package used by our authority set web page for instance. On the way we also fixed a bug that was rounding incorrectly efficiency updates…
Finally, we keep exploring the possibilities of Factom. We reached out to a young French company, NinjaLab, which specialize in cryptographic hardware security (and recently participated in the Ledger CTF) to get their point of view on the potential convergence of blockchain and cryptographic hardware. They were receptive to Factom (they liked the dLoc project) and we’ll try to devise a possible crypto hardware research grant to submit once the grants are open to the public.
LUCIAP was selected among the first 21 Authority Node Operators (ANOs) on April 28th. We set up our mainnet infrastructure over the first two weeks and two of our nodes were onboarded in the authority set on May 19th. In common agreement with other ANOs we all started setting our efficiencies and coinbase addresses on May 29th. So May 2018 was the month it all started for LUCIAP.
Following our selection, we also had some administrative work to get us started. We were fortunate to find a lawyer versed in cryptocurrency and practicing in Canada, where we are located. But honestly all of this is not tremendously interesting 😊
We developed the tool that was used by Authority Node Operators to set their efficiency and coinbase address. Those are steps necessary for the ANOs to receive their compensation in FCT. Factom Inc. untrusted us with this task so it alleviated some of the work they had to do during the M3 launch. We integrated an offline mode in this tool that allows users to set their efficiency and coinbase address in the most secure environment (so that the private keys of their identities can’t leak).
We extended our factom-testnet-monitoring tool to allow to compute aggregated metrics about Factom blockchain. That was some work related to our involvement in the Testnet monitoring working group. This was requested by the Testnet Admin to add metrics to his monthly report. Please note that the tool and script can actually be run against mainnet blockchain…
We were involved in multiple (mostly technical) discussions on the Factomize forum:
LUCIAP Factom identities
LUCIAP Factom identities of our authority nodes are:
As of today, the efficiency of both nodes is set to 50% in accordance with our campaigning document. Also, our two FCT payout addresses are: FA3F2aHx5hjmFpx1ySZeJgZHCzp1apg5rFfkvkgiKkq83Zrc95qv and FA2JS2Qdn5X2xYiM3xuu9hEJQEMBsVrCQsD7iSFR3kS6TvZvJyAu. All of this is publicly auditable directly in Factom blockchain.