Weekly Dev Update #32
Hey Y’all,
Another week, another update here at Loki.
Loki Core
Merge new code from Monero into Loki (
https://github.com/loki-project/loki/pull/401
)
Infinite Staking Part 1 is being iterated and code reviewed on. Discussion available here: (
https://github.com/loki-project/loki/pull/387
)
Integration Testing Framework is updated in preparation for Infinite Staking tests. Making the system more robust, switching to semaphores to synchronise multiple daemons and wallets. (
https://github.com/loki-project/loki/pull/312
)
Infinite Staking Part 2 including UX improvements is in development. (
https://github.com/Doy-lee/loki/tree/InfiniteStakingPart2
)
LLARP / Lokinet
If you’re lucky and join our Discord, you might also catch Jeff or Ryan, the developers of LLARP, live streaming as they code: https://www.twitch.tv/uguu25519, https://www.twitch.tv/neuroscr
We could really use your help. To be considered for inclusion in packaging distribution, we need people to star, watch and fork our Github repo. If you have a Github account, please consider helping us out.
Master branch changes
Fixed some typos in high-level documentation
Changes can be found at:
Staging branch changes
PR suggested changes
Loki Messenger
Use brand new Loki icons for the messenger and further rebranding (
https://github.com/loki-project/loki-messenger/pull/138
)
Messenger client sends and receives messages to specific swarms, now merged in (
https://github.com/loki-project/loki-messenger/pull/132
)
Additional unit testing for the Profile and Blocked Numbers modules (
https://github.com/loki-project/loki-messenger/pull/136
)
Fix bug where new conversations don’t show up until a normal message is sent (
https://github.com/loki-project/loki-messenger/pull/137
)
Developed high level design for how P2P messaging will be done and started implementation
General code housekeeping, like fixing linting issues and performing minor refactoring
Research work:
Created new repository for simulating different algorithms for the “arbitrary public key” to swarm id assignment, which will be performed by the Service Nodes. So far, the simulations have confirmed that compared to a 1-dimensional Euclidean distance, the Hamming distance offers the best uniformity in the amount of public keys assigned to swarms, but this comes with a larger amount of swarms affected when a swarm is added or deleted. Please note that this is a work in progress. (
https://github.com/sachaaaaa/loki-swarm-pubkey-test
)
Thanks,
Kee
You've got mail!
Sign up to our newsletter to keep up to date with everything Oxen.