Post #19491

cc90fda2e2a36241b2f6ed54016f2977bf5a7ecc95c40dff42f0ca7367d7c7bd
a450cd4e855e500a13b784bb4baeefbdd71bbc739a4272d651140ac1909fdde4
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.

{"entry_date":1568484093,"post_data":{"edit_count":0,"last_edit_date":0,"last_edit_user_id":0,"message_sha512":"8f29574a1887aa896f2171bd9fe8ce2b2f6fdaf9c1fb6deaab1589d59de0aadc4d6da765864afeab4cc26ecd8bdea705f13569c75c775265ce83edbb4ad7c7ff","node_id":59,"post_date":1568482921,"thread_id":2380,"title_sha512":"5b3fea0f489a7a877f2990072e8497a13b45a69632ff8e6474a07dc0583899fc712b9f318571e054a80a80574c7a42ddbc93e9d6394ffd99b1dbc5982552c68a","user_id":11},"post_link":"https:\/\/factomize.com\/forums\/index.php?threads\/2380#post-19491"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
Q3 2019 Update
Factoshi continues to work hard on our primary mission, which is to provide outstanding infrastructure to the Factom network and to build a robust ecosystem that is competitive with high tier public blockchains.

[B][U]Infrastructure[/U][/B]

Factoshi's authority node infrastructure performed as expected during Q3. Server uptime was 100% and factomd uptime equaled that of the Factom network, which experienced a pause during August.

Since being on boarded in Spring 2018, Factoshi has been running its authority servers in line with the specification promised during the campaign. Until now, the specification for Factoshi's authority servers was 8 vCPU/32GB. That spec is far in excess of what factomd has ever used. Even during periods of high network load, factomd has not come close to using those resources; EPS bottlenecks are not currently caused by CPU or memory limitations on authority set nodes.

The unrelenting fall in the price of FCT has compelled a review of that specification due to the potential for cost saving. As a result, Factoshi is reducing authority server specification to 6 vCPU/16GB. This will still leave ample room for growth whilst providing Factoshi welcome reprieve during this period of extremely negative price action. Server performance will be monitored closely, though I consider this to be a low risk change.

[B][U]Factoshi.io[/U][/B]

PegNet metrics were added to Factoshi.io to mark the launch of PegNet in August. This worked was completed in concert with TFA, who contributed the code to support PegNet analytics on the backend. Traffic to the website has doubled since the launch of PegNet, and it is now regularly cited on social media and elsewhere.

Furthermore, the rest of the website received a facelift. Several outstanding bugs were fixed on both the front and back end. The style was also modified slightly to make the website appear more professional.

[B][U]PegNet[/U][/B]

Factoshi's contributions to PegNet fall into 3 rough categories:

1. [B]Porting and maintaining documentation. [/B]Work here includes creating and updating the wiki, in addition to helping to add the white paper to GitHub.

2. [B]PegNet Compose. [/B]Work was started on PegNet Compose, which will help people get started on mining more easily. Work on PegNet Compose was completed following the end of the quarter.

3. [B]Community support. [/B]I have been on standby on the PegNet Discord server to help newcomers troubleshoot issues getting set up.

[B][U]Accounting script[/U][/B]

Factoshi's accounting script received a major upgrade. You can read about that in our previous update.
This is the raw content, without BBCode parsing.
Top