October update

  • As part of our ongoing work for the on-chain voting grant:
    1. We finished the full implementation of the voting protocol in JavaScript. The library is open-source. It will be in particular integrated in MyFactomWallet voting UI.
    2. We created a CLI tool to create a vote, participate in a vote and retrieve the details and results of a vote. Currently in beta but fully functional.
    3. We reviewed MyFactomWallet website before it got released to the community.
  • We have been invited to join the ambitious Factom Asset Token project lead by DBGrow and in collaboration with Canonical Ledgers and LayerTech.

    “FAT is an open source tokenization protocol built on the Factom blockchain that is efficient, modular, composable, and extensible allowing developers to layer token functionality to meet their specific use case. FAT is built around a set of open source standards that establish a pure-data tokenization implementation directly within the efficient entry chain structure of the Factom blockchain.”

    Paul (@luap) became an Editor of the project and has started contributing to specifications together with other Editors. A grant to fund the work on this project has been submitted, please have a look and feel free to give your feedback in the forum thread.

  • We are really proud to say that we became the first non-Factom Inc. contributor to the Factom software! We are happy and grateful that Factom Inc managed to unlock the situation regarding external contributions. The code change in question is about adding CORS settings to factomd and is visible in this pull request. This new feature will be available as part of the next release of factomd.
  • In line with the above, we also jumped on the opportunity to propose a fix for a bug present in walletd. The contribution was accepted and merged, it will be part of the next release.

July 2018 update

  • On-chain voting system: the grant issuance has been postponed multiple times during the month of July. As we speak grants are supposed to be paid out on 6th August. Nonetheless Luciap already met few times during the month with the other parties of the project to plan for the work and iron the voting protocol specification. We designed an initial version that is satisfying enough to start the implementation but we are still looking for a peer review by Factom Inc. It’s particularly important as the voting has some deep connection with the standing party identities being developed by Inc. We expect Luciap to start the actual implementation of the core specification in JavaScript during the month of August.
  • Our lead developer Paul (ex-Amazonian) has been ramping up on the Golang programming language by taking online courses and reading books of reference. Most of the ecosystem of software created by Factom Inc. is in Golang and the end goal here is to be able to make direct contributions to the original tools and, hopefully, to also make code changes to the core software. As a first step Paul made some code changes ([1] [2]) to allow specification of CORS domains for a factomd node. Setting CORS would allow to make calls to a Factom node directly from a browser which open doors for some interesting experimentation with have in mind. We hope this is the first of many contributions to the Factom codebase!
  • Participation in the (newly revived and active) core and code deploy committee. With the recent series of stalls there is a lot of matter to discuss here.
  • We made some brush up work on factom-storage which is a tool to store entire files on Factom blockchain. After some optimizations to make the tool more robust we managed to store a 15Mb high resolution picture on the testnet at a cost of 14,778 EC (~$14.778). Downloading the file is as easy as `factom-storage download 3865669b99fb8453905b167c8ccf5033bed3570de4ac646cb54bd7072e964caf`!
  • Small continuous improvements to factom.js now in version 0.2.6.
  • We also have started to work on a project about integrating Factom with some AWS services (Amazon cloud services) as seamlessly as possible. More details to come in the following months…
  • Luciap has changed its legal structure to become a corporation of British Columbia, Canada. To reflect this change of legal entity we rotated our payout addresses which are now FA3ng8sPtUESh97yy6MzeLmT4Azqj8PVYyg6CLxYfQnS3QC3ytKL and FA2cQhPNrQZRjUpr4hpt3WeUSWaBJDyzBzLrpUhQzdiwnmV4ApBs. You can keep track of our old addresses using https://luciap.ca/#/authority-set (and notice that we still haven’t move any FCT from there).

June 2018 update

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.

May 2018 update – It all started

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 😊

Development work

We released a new major version 0.2 of factom.js, the JavaScript library of reference for Factom. This is an important milestone as this version comes with lot of improvements regarding stability, size footprint and performance. This is the first version we feel comfortable recommending people to use for their projects, but it should still be considered at a beta stage: lots of features and improvements are still in the pipeline. We welcome any feedback or recommendations. You can find a general changelog in this forum annoucement: https://factomize.com/forums/threads/factom-js.234/

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…

Discussions

We were involved in multiple (mostly technical) discussions on the Factomize forum:

LUCIAP Factom identities

LUCIAP Factom identities of our authority nodes are:

  • 888888aac90d34ba84830046be9bdbc0c12d39045ce8f3f6c95f0beca4636629
  • 88888852a0821dd227735c50c5016741de67786432b9644c5d695b5ce7e42e58

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.