There have been some nasty scammers going around. A friendly reminder that we will never DM you first, and to always make sure you are downloading official releases (,, This particular scam involved a misspelt GitHub repository, make sure you’re careful about where you download software from.
Attention all Service Node operators:We’ve released a patch that resolves an issue which caused some Loki Storage Servers to become unreachable. This patch is a recommended upgrade, as it will improve the stability of your Service Node.Loki Launcher instructions: instructions :

We’ve patched a bug that caused Session Desktop users to be unable to restore from seed. Session IDs created on desktop client versions pre-1.0.3 are still functional, but are not able to restore from seed. To restore from seed, you’ll need to create a new Session ID on Session Desktop v1.0.4 or later. Desktop clients should automatically receive a notification to update to version 1.0.4. Mobile clients are unaffected by this bug.

A brand new Lokinet version is rolling out on mainnet — Lokinet 0.7.0 is running on 78 Service Nodes and counting! If you’re a SN operator and want to upgrade to 0.7.0, get in touch with us.Read about Lokinet 0.7.0 and all the other goings-on at Loki in this week’s Dev Update:
What the fork? That’s right, it’s Valiant Vidar 7.0.0. The next Lok iNetwork hardfork is coming soon to a Service Node near you. This one’s packing onion requests for Session, the Loki Name System, and an adjustment to the block reward. Read more:
Hardforks are hard work! 👷We've just put the finishing touches on Valiant Vidar, ready for the hardfork in about a week — locked in at block height 496,969. Check out all the Loki news in this week's Dev Update:

The Valiant Vidar hardfork will arrive at block height 496,969. For those of you playing at home, that's around 2PM AEDT March 25. 🗓️(We'll update this time as we get closer to the block height.)

ATTENTION ALL SERVICE NODE OPERATORSThe mandatory upgrade period has begun. Start upgrading your Service Nodes to the Valiant Vidar compatible binaries now. This hardfork will require upgrades to Lokinet, lokid and the Loki storage server. The instructions for upgrading have changed, so please read them carefully. If you are running a custom installation with firewalling then note that this upgrade requires a new storage server port (22020 by default) to be opened.The mandatory upgrade period will end at block 496,969 (about 7 days from now), so make sure you have upgraded before then.Loki Launcher instructions: instructions :
Aaaaaaare you ready to hardfork?That’s right, Valiant Vidar is almost here — bringing LNS names for Session, a rewritten Lokinet DHT, and Blink by default.Check out all the latest Loki news in this week’s Dev Update:
One more time for the Service Node ops in the back — Valiant Vidar is just over 5 hours away!We've also rolled out a Loki Storage Server upgrade — but it's optional.New upgrade instructions:Loki Launcher:

Loki Name Service.Blink transactions by default.Improved onion routing for Session.Valiant Vidar is here — and it's packing some serious heat.

With the arrival of Valiant Vidar, the Loki suite now has namespaces! Our new LNS system means you can assign a custom username or alias to your Session ID or Loki wallet address. Here's how it all works:
Hi, my name is __. 👋Been wondering how to snag yourself a username with Valiant Vidar's new Loki Name System? 🤔Well, here's how:
Instant private transactions. Sound too good to be true? Well, it’s not. With Valiant Vidar, Blink is now switched on by default.Here's everything you need to know:
Give me a G! Give me a U! Give me an I! Give me a GUI!That’s right, it’s a shiny new Lokinet GUI, coming soon to a client near you.Here's everything you need to know about Loki this week: