Post #26395

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.
Q1 2020 Report
[B]1. Factoshi API[/B]

Work on the Factoshi stats API is well underway. It coincides with a large refactor of the Factoshi stats daemon to make it easier to add new stats to in the future (such as rich lists). An alpha version should be complete during Q2.

[B]2. Factom.js[/B]

I have made several PRs to Factom.js to fix bugs and improve typings:


[B]3. Governance[/B]

Factoshi continues to play an active role in governance. I brought forward an [URL='']informal poll[/URL] to discover ways to improve the efficiency of the Factom Protocol. I also tried to [URL='']implement one of those proposals[/URL] on behalf of ANOs, though the amendment failed at the ratification stage.

Other governance activity includes thorough review and editing of Doc 002 prior to the [URL='']amendment vote[/URL], and general participation and proactive engagement with various governance initiatives.

[B]4. Efficiency [/B]

At Factoshi's Q4 2019 update, I mentioned that Factoshi would only be engaging with server maintenance and bug fixing on in order to reduce costs. As the above development work demonstrates, that did not happen. Continuing to operate at 50% is not sustainable at these price levels. Consequently, Factoshi is dropping to 40% efficiency until a time that the price of FCT can show sustained recovery.
This is the raw content, without BBCode parsing.