Weekly Dev Update #77

02 December 2019 —Admin

Hey Y’all,

This week we did a lot more work on Loki Messenger focusing on multi-device and profile images, getting everything ready for a quality-of-life upgrade for this week. We also forked the Loki core testnet with the latest Lokinet release candidate and Blink, gearing up for a planned release at the end of the year. We also squashed some final Lokinet bugs that were causing unexpected client disconnections.

Loki Core

Fix a number of failing core tests, Merge LNS tx burning changes, remove unused values from TX construction
https://github.com/loki-project/loki/pull/939
Reclassify staking transactions in show and export transfers
https://github.com/loki-project/loki/pull/932
Fork testnet to start using Blink for testing purposes
https://github.com/loki-project/loki/pull/941
Fix for Loki compile for older libc++
https://github.com/loki-project/loki/pull/938
Check blockchain init failure before `r` is overwritten
https://github.com/loki-project/loki/pull/937
Required code for Lokinet integration
https://github.com/loki-project/loki/pull/936
Blink fully reviewed and merged into the development branch, including mempool and tx burning changes
https://github.com/loki-project/loki/pull/935
Aggregate init service node info instead of setting members individually
https://github.com/loki-project/loki/pull/934

Lokinet

If you’re on our Discord you can catch Jeff, the lead developer of LLARP, live streaming as he codes at https://www.twitch.tv/uguu25519. He typically streams on Tuesday mornings, 9am – 12pm Eastern (US) time.

What went on last week with Lokinet:

This past week was one of the most intense weeks in memory for the Lokinet team. The team was focused on nailing down and fixing some final bugs in order to get 0.6.0 ready for a stable release. The late nights, extra coffee, and some forgoing of Thanksgiving turkey (most of the Lokinet team is based in the US) paid off, however: we finally nailed the remaining issues and are confident with the current state of the Lokinet release. We’re continuing to test it on both a private network and on the just-forked Loki testnet (see Loki Core notes), but so far performance has been steady and solid.

PR Activity:

The big stability PR: this PR builds from more than a dozen smaller branches and test code paths that debugged and fixed the remaining stability issues. It ended up being easier pulling this into a single large PR that included everything, rather than trying to clean up the multiple branches and PRs that resulting from the rapid development.
https://github.com/loki-project/loki-network/pull/935
Lokid integration: ping lokid periodically (which lokid requires to send uptime proofs) –
https://github.com/loki-project/loki-network/pull/933
Change the default build type when building the “master” branch to Release instead of Debug –
https://github.com/loki-project/loki-network/pull/930
Lokid integration: query lokid for SN keys on startup rather than needing to read lokid’s private key files directly –
https://github.com/loki-project/loki-network/pull/931
Lokinet private key management and backups (work in progress) –
https://github.com/loki-project/loki-network/pull/921
Fix a “zero hop bug” connectivity issue –
https://github.com/loki-project/loki-network/pull/926
Increase the default size of the logic thread queue (and make it configurable) –
https://github.com/loki-project/loki-network/pull/929