Google plus

Fluid Edge Themes


  •   We are super excited to announce the next release for Loki, which will contain Bulletproofs, along with a few larger quality of life changes for Service Node staking.   Features include: Add Bulletproofs; Lower transaction fees in accordance with Bulletproofs; Add staking from the GUI wallet; Governance wallet payout changed from once per block to once per 5,040 blocks, this reduces blockchain bloat; IPV6 Support for Loki Daemon and Loki wallet CLI; Zawy difficulty adjustment algorithm patch; Service Node grace period added, Service Nodes that consecutively register within a time frame

  • Hey Y’all, Another weekly Dev Update for you to peruse. Just a note, we're moving Dev updates to Mondays instead of Fridays, so keep your eyes peeled each Monday. Loki Messenger Integrate the Service Node storage into Lokid Fix conversation list showing duplicated conversations when entering a known public key Fix validation of messenger public keys in search bar Merge upstream changes from Signal Add code to parse message TTL LLARP / Lokinet Released Lokinet 0.3.1: "Kuz Yolo" Minor DHT bug fix release We urge all Lokinet

  •   Over the course of this article I will analyse three key elements which all messenger applications must consider.   Metadata: Any information, aside from the actual message, which is transmitted and can be exposed to third parties. Encryption: How your messages are encoded to obfuscate their content. Scalability and Attacks: How well the messenger responds to increases in usage and if there are any known attack vectors or exploits to the specific system. I will also explore how centralisation/decentralisation can affect the privacy and security of each element. Centralisation, in

  • Hey Y’all, Some bigger changes going in this week as we prepare for our next hardfork, the date of which should be announced soon so watch out for updates in the community channels! Loki Core Change governance wallet reward from per block to once every 5040 blocks (one week). This reduces blockchain bloat and makes the governance wallet more manageable, 5% amount stays the same, (this will require a hardfork to take effect) Merge upstream again, keeping up to date with bug fixes that were released after bulletproofs release Differentiate coinbase, service-node,

  • Full Time Developers With seven full time developers we were able to launch Service Nodes in September, two months early. Managed to run a test version of Lokinet on a private testing network successfully. Research, review, find and fix critical bugs for Loki and exchanges trading Loki. We have noticed increasing difficulty in fixing bugs and merging changes from Monero as Loki moves away from Monero’s original code. There will be an increase in developer resources to merge these changes in the future. Network Infrastructure & Performance Testing Services In depth

  • Hey Y’all, Lots of hiring this week! We have brought on two new members who will be joining us in the coming weeks - I will introduce them once they complete their first pull requests. Daemon Fix Monero bug using receive time to subtract m_txpool_weight which causes overflow ( Updated repository to include latest fixes from Monero into Loki ( Fix the builds on development branches breaking after upstream changes (,, Service Nodes Swarms first draft is complete ( LLARP / Lokinet We are looking for experienced sysadmins to run nodes that connect to

  • Hey Y’all, Things are moving along at a fast pace as we hire more developers. Service Nodes The first natural Service Node deregistration will be processed in the coming days. We have written a guide on some of the considerations users should make, here: TLDR: Be very careful if you are using autostake in an open or closed pool. Service Node grace period added, this means that Service Nodes can re-register without being deregistered Additional work is being done on swarm testing algorithms. You can see our testing framework

  •   We are very quickly approaching the date where the first Service Node will be deregistered because of a natural expiry. On October the 20th, 30 days since the first Service Node being registered, the first group of Service Nodes will undergo deregistration. There is a couple of things we wanted to go through for Service Node operators so they understand what the process is of re-registering, and issue a few warnings about Autostaking. If you are presently intending on using autostaking, you should read this announcement very carefully.   Updating software The downtime between

  • Hey Y’all, Lots of code going in this week, with some big design decisions especially around Swarms and Loki Messenger. There was also a new release of the the Loki CLI wallet and daemon, which all Service Node operators should update to. The release does not include consensus changes but does change how autostaking works, making users much less likely to lock funds unintentionally by autostaking. The release is here: and there is also a video guide on how to update here: Service Nodes Added grace periods between de-registrations laying the framework for more Swarm

  • Hey Y’all, Another weekly Dev Update for everyone. Service Nodes Added preventative measures to make Service Node staking more robust LLARP / Lokinet If you’re lucky and join our Discord, you might catch Jeff or Ryan, the developers of LLARP, live streaming as they code: , Progress continues on libllarp Optimise the router's inbound links data structure More keepalive tuning Support tunnel "packet info" for better multiplatform support MacOS tunnel support is now fixed No longer stores Introsets when forwarding Improve autoconfiguration A default "hidden service" is made for client access, and configuration

  • Hey Y’all, The dev team had an interesting week, which was primarily spent responding to bugs in the Loki core implementation. Lokinet developers have been working super hard and are getting close to something that is usable by the end user. *** Releases This week we published a minor release which can be found here: This incorporates fixes for newly operating Service Nodes and prevents a burning bug, mentioned below. This update does not contain any consensus rule changes and therefore is a non-mandatory upgrade. However, if you are a Loki merchant, you should update immediately.

  • Hey Y’all, Last week was our biggest release week so far- SERVICE NODES ARE NOW LIVE! Service Nodes Service nodes are now released! At time time of publishing this, there are 84 Service Nodes now running ( There have also been a number of pooled Service Nodes, and some even waiting for contributions. Continue merging upstream Monero changes to Loki ( Finalise the release binaries for Service Nodes including final patches for log file bloat. LLARP / Lokinet If you’re lucky and join our Discord, you might catch Jeff or Ryan, the developers of LLARP, live

  • Hey Y’all, Last update before mainnet Service Node launch! It's getting close now, so make sure you're ready for when we fork on September 20th at block 101250. Service Nodes Final Service Node release is out, it can be downloaded here. All exchanges, as well as most of the major pools, have now updated. Continue merging upstream changes from Monero, which includes bug fixes and performance improvements. 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: , Released LokiNET

  •   As Loki is the first Monero fork (and CryptoNote coin, by extension) to have an active implementation of Masternodes, we are staggering releases and adding features as we go. This is new territory and each change we make to the the Monero codebase must be extensively tested before release.   What Loki Service Nodes do in the short term? (Right now) As part of the 1.0.0 release, Loki Masternodes (called Service Nodes) will have minimum functionality; they will store a full copy of the blockchain, and every hour they will publish an uptime

  • Hey Y’all, Another weekly Dev Update for you to peruse. Service Nodes Over the weekend we will draft the final binaries for Service Nodes; this will include a hard fork height of (101250) ~September 20th. Thus we will begin the mandatory upgrade period for all Service Nodes. Be on the lookout for posts in the announcements channel on Discord or Telegram. If you have enough Loki  and are planning to run a Service Node on the mainnet, there is still time to get hands-on and test by using the testnet guide here: Added a

  • Hey Everyone, We keep chugging forward with testnet this week, Lokinet is developing some more user friendly features, and a couple of developers are in Europe traveling for conferences so we have a smaller dev update this week. Service Nodes Print_sr command is available for users to query the staking requirement at arbitrary heights. Several unit tests are in to validify the isolate parts of the service nodes API. Fix edge cases discovered, failing to restore service node state after a switch to an alternate chain and back. Fix deregistration bug involving

  •   Over the last three months, there has been significant focus on Loki’s layer two, with numerous papers and articles revealing the true scope of Loki’s Service Node functionality with Loki now becoming a fully fledged mixnet. There has also been much talk about how Loki as a currency, or layer one transactional medium, will function in this framework. Initially we envisioned Loki would act as an access token to prevent Sybil attacks, however there are some downfalls of that system which we addressed in an article here. Given we have

  • Testing, testing, testing! A Weekly Dev Update full of testing for y’all this week. Service Nodes Fix consensus issues regarding deregistrations in the transaction pool causing chain splits. Prioritise deregistrations when selecting TX’s from the pool. Add print_sn_status convenience command to directly display the running service nodes’ current state on the network. @Kingsley contributed a fix for the incorrect estimated display of how many days worth of blocks your node is behind. Make uptime proofs more lenient in accepting proofs and culling dead nodes. Fix edge case

  • Hey everyone, Big week of testnet changes this week Service Nodes 0.3.3 Magic Mani tesnet beta, released Published the full Service Node staking guide for testnet here: Autostaking Interactive prompt for registration. Service Node list being stored in the Database and Service Node Integration into Testnet Explorer see Two essential consensus bugfixes in the way we do quorum vote counting. Provide mechanisms for displaying Service Node analytics with the commands print_sn <pubkey> LLARP / Lokinet If you’re lucky and join our Discord, you might catch Jeff or Ryan, the developers of LLARP, live streaming as they code: ,

  • Hey Everyone, The development pace in the Loki office has been consistent and quicker than expected, and I'm happy to announce that we will be launching Service Nodes well ahead of schedule. A huge thank you to our two main Service Node developers, jcktm and Doy-lee, who have been putting in long hours to get this out. This will mark the first time Proof of Service has been implemented on a CryptoNote coin and we’re really excited to have everyone onboard to test it out. How will the rollout/update process work? Beginning

  • Hey Y’all, Some big things on the horizon for Loki, and a new dev update so we keep the community in the loop! Service Nodes Updated wallet to support staking transactions where the unlock time does not apply to the change address. Extensive testing of Service Nodes has begun. Use of boost::round and other math libraries used for consensus code. Pooled registration contributions. QCop has been merged into the development branch for sending out deregistrations Add RPC calls for generating the service node registration command for participants LLARP / Lokinet If

  • Hey Y’all, Another weekly dev update to keep everyone up to speed: Loki Base Layer Pull request submitted for Time Locked transactions to now be locked per output instead of the whole of the transaction: Testing still needs to be done. Enable storage of the Service Node list in the database, this will reduce time spent scanning the blockchain on startup. Testing still required. Service Nodes Pull request has been submitted and is in review for quorum cop polling the state of the network. It currently integrates with de-registration to autonomously monitor

  • Hey Y’all, Big week, big update! Loki Baselayer We have released new Loki Daemons for all operating systems in anticipation for activation of the altered emissions curve. The new clients will fork at height 64324, approximately 31st of July UTC. You can read more about why this change is occuring here: Service Nodes Deregisters has passed the 5th iteration and now merged into the development build, which completes the first prototype of being able to become a service node and expire after the registration duration. Add support for pooling multiple stakers to register

  •   This article is intended as a basic overview as to the reasoning behind changing Loki’s emission curve. To this purpose we have largely simplified the factors and influences at play; for a more in depth understanding, please refer to our paper Loki Cryptoeconomics: Alterations to the Staking Requirements and the Emission Curve.   DISCLAIMER This article contains charts and figures which include examples of return of investments and prices for the Loki cryptographic coin. These prices are examples only and are not a prediction, forecast, or representation as to any actual likelihood of

  •   We’re very pleased to present this proposal to the community after many weeks of patience. We have reviewed the Loki cryptoeconomics extensively with assistance from Dr Brenden Markey Towler of the University of Queensland, working with the RMIT Blockchain Innovation Hub.   Today we present two documents. The first is our economics paper: Proposal: Alterations to the Loki Cryptoeconomics. This document outlines the problems we have considered, some solutions to them, and an explanation of our final selection.   The second is a report by Dr Brenden Markey-Towler, Cryptoeconomics of the Loki network,  which

  •   Weekly dev update for Y’all, a little late this week since we were busy writing papers 🙂 Service Nodes Split up service node pubkey from service node address Service Node Deregister has progressed to the 3rd iteration which includes tightening down the registration protocol, fixing up loose-ends, integrating various endpoints together and approaching production level. 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: , Progress continues on libllarp DHT query iteration fix Convert C files to

  • Hey Y’all, New week, new update! Service Nodes Set a threshold of required votes for deregister TX’s to be created to handle spamming of deregister TX’s using different vote combinations for the same service node. Service node lists are being integrated into the deregister system. There's a new sheriff in town, Quorum Cop enforces pre-determined node behaviour in a decentralised way. QC executable has created, reading from the wallet and pulling height from the daemon. Boilerplate uptime proof messaging written. Work in progress: Miscellaneous bug fixes LLARP / Lokinet If you’re lucky and join our Discord,

  •   Put simply, Sybil attacks are where one person or entity creates multiple fake identities, usually to either subvert some part of a reputation system, or to effectively create large scale denial-of-service attacks. [1] Sybil attacks present problems to systems that maintain a low barrier of identification. With Loki’s focus on privacy and its P2P nature, methods are required to identify unique individuals without requiring some proof of personhood (i.e. government ID or License)     In Loki’s case, Sybil attacks could be used to either spam path creation on Lokinet (more on this

  • Hey Y'all, Got a Winter weekly update for you. Service Nodes Deterministic selection of Service nodes from a sorted list has passed 2 code reviews and is merged Service node deregistration transactions have passed the first stage of code review, fixes are being made for an immediate merge 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:, Released LokiNET 0.0.1 Progress continues on libllarp. Fixed DHT lookups. Implement CoDel>congestion handling (to defeat bufferbloat) and further tuning. Private

  • Hey Y’all, Got a new weekly update, NOW WITH ADDED ANNOUNCEMENTS Service Nodes Staking transactions no longer require the private view key to be exposed. Instead, the TX private key is exposed: Service Node deregristration transactions, and peer-to-peer voting are complete: Added functionality for retrieving a quorum list from a specified block height: LLARP / Lokinet has been announced and you can read more about it here. I will now be featuring it in my weekly updates. If you’re lucky and join our Discord, you might also catch Jeff, the lead developer

  • Loki’s Exploration into the Mixnet Space   We have been dropping lots of not-so-subtle hints that we have been working on a decentralised mixnet, and it's finally time to reveal what we’ve been working on. This article, along with the soon-to-be-released white paper version 3 should get everyone up to speed on Lokinet.   Mix What? Mixnet is a term used to describe an overlay network that operates on top of the internet. You might have heard of Tor or I2P- these are both mixnets. So what's the idea behind a mixnet? Typically, when

  • Hey Team, Back again with another weekly update. Service Nodes Service node block reward distribution and validation has been built: In progress: Separating partial deregistrations from the transaction system and broadcast them as votes over P2P into their own pool, to eventually be formed into authoritative service node deregistration transactions: Merged relevant Monero changes into Loki: Begun work changing time locked transactions to reference specific outputs rather than locking the whole transaction: Android Mobile Wallet Re-skin and core functionality complete, as well as touching up final visual design points including a website to

  • Hey Team, I’m going to start giving weekly updates on what the development team is up to. It can be hard for the community to see what we’re working on as we sometimes operate out of our own Loki forks, then merge back when things are ready to move into production. My hope is that these updates will shed light on the project’s development. This weeks updates Service Nodes Service node lists: will be used to create the authoritative state of the service node network: Service node registration transactions: time locked TXes that

  • In the context of a cryptocurrency, an ASIC (Application Specific Integrated Circuit) is a chip that is specifically designed to mine a certain cryptocurrency or a certain hashing algorithm. Recently, there have been a number of high profile ASIC miners released for cryptocurrencies previously believed to be ASIC resistant [1]. So what’s the problem with ASICs? ASICs usually provide a significant advantage over graphics cards (GPUs) and CPU mining; so much so that once ASICs are released it is generally un-profitable to mine without one. This in itself it not entirely

  • The 2nd Layer solutions proposed by Loki allow users significant functionality that cannot be provided by a Monero fork alone. Namely, Loki will incentivise a group of nodes that perform specific networking tasks and will build the basis for a new type of mixnet. Mixnets that have the properties of Sybil attack resistance are highly resilient to large-scale network analysis. This protection is provided by market operations, which make it prohibitively expensive to own a large portion of nodes operating on the mixnet. Operating on top of this incentivised second layer will

  • Foreword We started Loki because we believed we had ideas that could improve the range of tools people use in their pursuit of privacy and safety online. Thankfully, it appears thousands of people see the potential in our ideas, and dozens of firms, funds and individuals have supported our project to date. With this support, I believe we can create a protocol that will help people across the globe keep their data safe. We have always intended to be as transparent and open as possible, and we wish to share the

  • There are a lot of community members who ask if Loki is trying to compete with Monero. At face value, it seems like an obvious assumption to make. However, our intention is to use Monero as a proven and solid basis to build an additional feature set that goes beyond anonymous payment systems. So long as Monero maintains its efforts to be the pinnacle of private transaction networks, it is unlikely that Loki will ever pose a ‘threat’ to the Monero project. Competition is a funny concept when it comes to