Post #26560

fbdb0d7d8096b8ed28e227184f149bc05aa1ea90455755c9ab73fa5f047cfc7b
8aaf512bf59e9b67cdecc6f11dff88f02b514ef3a8fea80089a94ab5d43e44b8
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":1586126547,"post_data":{"edit_count":2,"last_edit_date":1586126522,"last_edit_user_id":10,"message_sha512":"f514170a3d5a66b9e9ede5314df131c6f075546c282ecad23fd4118fbedeb04976aee364ed099fffb6476efbe0e5c51a0bbbcd10800b00384c595d6a0d911c92","node_id":59,"post_date":1586118625,"thread_id":4235,"title_sha512":"e0baa670d37c3f501cc0e31335ce3feab892fa0a17a4365f336278b6b7a3dd87e48726515dac04a36d674cb33e12e51d0dbc1b92326587fde4ab6fd86a55b03a","user_id":10},"post_link":"https:\/\/factomize.com\/forums\/index.php?threads\/4235#post-26560"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
Q1 2020 Report
Hi everyone,

Please find below a list of Luciap activities during the first quarter of 2020:

[B]1. Review of Who (Factomize) complete rewrite of p2p module of factomd[/B]

I mentioned in the past that we were doing code reviews, but I realize that non-programmer may not fully realize the extend of that task. For a good review the reviewer needs to read all the code and understand every bits of it as much as if he wrote the code himself; then comment on many aspects of the code: general design, readability, understandability, potential bugs or optimization ideas etc. This is why code reviews are excellent at finding bugs, augmenting code readability and maintenability over time. Which is also why it takes much more time that people probably expect, and I just wanted to take the time to highlight that for once. This review was particularly long because it was an entire module, but it was very pleasant discussing and working through it with [USER=192]@Who[/USER]. Here's the full list of my beedback:
[LIST=1]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/3[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/4[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/5[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/6[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/7[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/8[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/9[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/pull/10[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/pull/14[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/15[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/16[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/17[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/18[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/19[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/20[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/22[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/pull/23[/URL] (comments)
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/24[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/pull/27[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/28[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/30[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/31[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/pull/32[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/issues/33[/URL]
[*][URL]https://github.com/WhoSoup/factom-p2p/pull/39[/URL] (comments)
[*][URL]https://github.com/WhoSoup/factom-p2p/pull/41[/URL] (comments)
[/LIST]
[B]2. PegNet core contributions[/B]

I reviewed PegNet code and reported 2 bugs: [URL]https://github.com/pegnet/pegnet/issues/352[/URL] and [URL]https://github.com/pegnet/pegnet/issues/353[/URL] (and fixed one of them). I was also the only one taking the time to review an external contributor work here: [URL]https://github.com/pegnet/LXRHash/pull/71[/URL].

[B]3. Published a new minor version of the FAT Wallet[/B]

[USER=102]@David Kuiper[/USER] brought to my attention that the FAT Wallet had a different key derivation scheme than MyFactomWallet when interacting with the Ledger device. While not fundamentally an issue for FAT Wallet users, it was still unfortunate and I agreed that having compatibility between our ecosystem tools (MFW and FAT Wallet) was important. I published a new version of the FAT Wallet that can produce compatible keys and that has already helped 2 users who can't use MFW on Windows. Note that we do not have any "FAT continuation grant" on-going and that work was happily done on ANO income. [URL]https://github.com/Factom-Asset-Tokens/wallet[/URL]..

[B]4. factom.js updates[/B]

[USER=11]@Alex[/USER] submitted some good improvements to some features of factom.js (FactomEventEmitter). I reviewed, merged and published those changes.
[LIST]
[*][URL]https://github.com/PaulBernier/factomjs/pull/19[/URL]
[*][URL]https://github.com/PaulBernier/factomjs/pull/18[/URL]
[*][URL]https://github.com/PaulBernier/factomjs/pull/17[/URL]
[/LIST]
I also edited the lib to support continuous testing of the testnet: [URL]https://github.com/PaulBernier/factomjs/issues/14[/URL]

[B]5. Participation in the core committee[/B]

I remain an active member of the core committee.

[B]6. Orax[/B]

We continue to operate and maintain Orax (at a loss), the biggest public PegNet mining pool with over 120 active users.
This is the raw content, without BBCode parsing.
Top