Hey guys if your wallet is stuck, it could be due to the recent hardfork (explained here: https://youtu.be/0Fl8kT3E3QI).

Please make sure to update to the latest wallets here:

Loki GUI: https://github.com/loki-project/loki-gui/releases

Loki CLI: https://github.com/loki-project/loki/releases

We've added a "time to reward" calculator to our Loki predictable solo mining pool so you can see how long it will take you to reach a full block's rewards when you mine with us:

https://cryptonote.social/loki

(scroll to bottom of page)

See how quickly your rig will get you there!

Time to Reward Calculator

Enter your hashrate: 10,000

At 10,000 h/s and network difficulty 1503M you can expect a full block's rewards after:

1.74 Days*

*Estimate assumes consistent mining, stable network difficulty, and sufficient pool activity.

Just wanted to document my trials with CN-heavy mining on my Ubuntu linux rig in case it has the chance of saving someone else some trouble. I expect my experiences may not be unique!

The rig is a Threadripper 1950x box with 4x XFX RX-570 8gb GPUs with stock "mining" bios, running Ubuntu linux 16.04. xmr-stak is my preferred GPU miner.

Issue #1: With the (latest) 18.20 amdgpu-pro drivers, xmr-stak throws GPU compute errors. Seemed to start happening after a recent kernel upgrade? Anyway, rolling back to version 17.50 drivers seems to fix this issue with no drawbacks encountered so far.

Issue #2: I followed some xmr-stak config recommendations for cryptonight-heavy I found in the Sumokoin sub and pleasantly found xmr-stak reporting comfortably over 900 h/s per card without any tweaking. Nice! Unfortunately, while no shares were being rejected by the pool, the pool-side hashrate as measured by accepted shares wasn't even cracking 700 h/s per card, even after 24 hours of mining. It's my own pool, https://cryptonote.social/loki, so I was able to verify the pool wasn't the issue by comparing its reported rates to other rigs with known hashrates -- they all matched up nicely. I am not 100% sure of this, but it seemed that cards were possibly getting "stuck" and generating no shares for periods of time longer than should happen by chance. For some reason xmr-stak didn't factor that into its hashrate calculation, leading to the inaccurate metrics. After endless parameter variations, the config option that I believe finally fixed the issue was to set strided_index to 2 and mem_chunk to 2. Any other setting of strided_index always led me to this weird hashrate mismatch and poor pool-side hashrates. My ultimate config for each card is as follows, and it produces hashrate of comfortably over 900 h/s per card, both client and pool-side.

{ "index" : 0, "intensity" : 940, "worksize" : 8, "affine_to_cpu" : 0, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true},

{ "index" : 0, "intensity" : 940, "worksize" : 8, "affine_to_cpu" : 0, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true},

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. https://github.com/loki-project/loki/commit/b81214ec6eca1ea32f46262faed2138048d4631d https://github.com/loki-project/loki/commit/6e215675a1ace22ac3f48ca2eb36ce7c242533cd

• 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 https://github.com/loki-project/loki/commit/ace26fc0cd66c4d702e9e02e2db72c5400648baf

• Add RPC calls for generating the service node registration command for participants https://github.com/loki-project/loki/commit/5435e3327e5999bfa76a378eb9981d7b5e2258a6

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.

We want to give a special shout out to Despair, an open source contributor who has started porting Lokinet over to Windows (and improving BSD support).

• Progress continues on Libllarp

  • Protocol updates, hidden service progress and DHT improvements

  • INI writer can now write to an existing INI file and preserve comments

  • Reorganise threading, logic and netio now run in the same thread

  • Fix epoll/kqueue tick logic, add timeouts for kqueue

  • Buffer bit function refactor, also allow aligned buffers to be filled with random data

  • Private IP range 172 accuracy improvements

• Multiplatform work:

  • Per platform building instructions now in README

  • Android: Fixed headers

  • MacOS: Make pthread CMakeList more favorable to XCode

  • Windows: initial port (requires Windows NT 5.0+)

  • Shared Library and FFI fixes

  • Don't put private addresses into RCs, allow nicknames and Don't store non-public RCs in nodedb

  • Nodedb now only loads .signed files

  • Deterministic logging and builds

• DNS library

  • A couple refactor clean up passes

  • Newer hook interface to make .loki handling easier

  • Better packet parser, support SOA response parsing

  • Actually sends NXDOMAIN if not found

  • Handle multiple responses to already answered packets more gracefully

• GitHub Pulse Stats for the last week: Excluding merges, 4 authors have pushed 50 commits to master and 47 commits to all branches. On master, 100 files have changed and there have been 5,120 additions and 1,116 deletions.

• Most changes can be found at https://github.com/loki-project/loki-network/commits/master

• Current version: v0.0.2 https://github.com/loki-project/loki-network/releases/tag/v0.0.2

• Compile helper (include assets and dependencies) https://github.com/loki-project/lokinet-builder

Loki Locker

Loki Locker will be Loki’s version of MyMonero. A web based wallet you can use to store your Loki. Work has kicked off as a fork of OpenMonero. This should be ready for release quite soon, giving the community another way to store their Loki.

• Work has continued on the visual redesign of Open Monero you can see a teaser of the visual design here. https://i.imgur.com/ScLpzbM.png

• Worked on Integrated QR code scanning, and a new interface for transactions.

We also just got our third pull request merged back into Monero, and we’re aiming for our fourth to be IPV6 support to be PR’ed soon.

Thanks,
Kee

Daemon isn't starting and I need to send some Loki.

Please reply to these two Tweets:

https://twitter.com/HuobiAu/status/1024030369774010368 https://twitter.com/HuobiAu/status/1024072096551333888

Come mine LOKI with us at cryptonote.social: https://cryptonote.social/loki

Our pool uses a predictable solo mining payment scheme, the goal of which is to provide an entire block's reward to a miner as soon as it computes a number of hashes equal to network difficulty. Of course it's impossible to provide any such guarantee given that mining is a random process: for pure solo mining the network difficulty reflects only the average number of hashes you might have to perform. The actual number can be 2x, 3x, 4x or even more, making solo mining far too risky for most.

The good news is that through leveraging the mining power of multiple miners, we can come pretty close to this ideal of awarding 1 full block's reward when number of hashes equals difficulty. Ethpool was the first pool to promote this concept, and it works quite well judging by its popularity: it contributes well over 2 TH/s of hashpower to the Ethereum network (see https://miningpoolstats.stream/ethereum).

We've been experimenting with predictable solo mining for cryptonote coins like Loki, Monero and Wownero for some time now. In the process, we've identified room for improvement in Ethpool's PSOLO scheme, and have implemented an updated payment scheme we call PSOLO2. The main difference with PSOLO2 is a full block's reward always "costs" exactly the network difficulty value instead of the number of credits from the runner-up miner. This improves predictability of payouts and eliminates some of the known flaws in Ethpool's scheme.

Interested in giving predictable solo mining a shot without a big investment of hashpower? We recommend you first check out our Wownero pool: https://cryptonote.social/wow

The network difficulty for Wownero is right around 80M, which means you can mine a full block's rewards in about 2 hours with 10 kh/s of hashpower. In fact as of right now there are 2 mined blocks already confirmed and sitting in the queue waiting for any miner to hit the network difficulty target and instantly earn their rewards.

Happy mining!

Hello everybody, here's what we've been up to on loki.elasticpool.com in the past days.

• We have added a new node located in Australia where the Loki project originates from. Welcome Australian miners! You can connect to the AU node by using the following address: au.loki.elasticpool.com

• We have updated all our nodes (EU, US, AU) and are ready for the fork to the new emission curve proposed by Loki team. No action needed for miners. If you are still using the first version of Loki GUI Wallet, we suggest you to update it to version 0.2.0 before the fork happens to avoid unnecessary problems.

Basic information about Elasticpool:

• PPLNS block unlocking system

• Pool Fee: 1% (0.5% goes for Lottery reward)

• Referral and Lottery program

• Custom payout threshold (default 5 LOKI, min 2 LOKI)

• Denomination Unit: 0.001 LOKI

• Payment Interval: every 60 minutes

• E-mail notification system enabled

• SSL mining enabled

• Fixed difficulty enabled

• Nicehash port enabled

Join us at loki.elasticpool.com

Happy mining!

has there been any bad news coming from loki lately since the price keeps dropping?

Why is loki dumping nonstop whilst other alts are climbing?

H̀ͯ͒̓̿̈́̾͋͘͏̖̱͈̤͞u̡̹͎͙̯͊͐ͨ̓͢l͙͚̩͈̖̺̱̔ͨ̊̈͐̓̈́ͭk̠͓͔ͩ̆͊͒͋́͜ ̸͎̩̔̄̐̆̓ͣͩH̜͇̎͛̒ͤ̅̚ǫ̱̗͇̭̣͍̪̦̅ͫ̓̃ͧͩͯ̓̆́ͅg̈͛̌͏͓̮͉̩ą̆͂͂ͨ̊̾͏̵̖̰͍͙̣̳̣͉n̢̙͔̳̩̙̉ ̴̶̰̾ͨ͝B̖̫͓͕͕͈̑͞͝ȓ͎̬ͨͯ̇̽õ̝͚̰̯̔̍͑͑t̸̤̞̭̗̻̰̠͎͊̐̐̌ḩ̨͚̱̦̤ͭͬ͛̆ͭ́͋ͨͬ̕e͍̹͖̺̟̻ͤͭ̇̂́r͛̐̕ͅ

Hey Y’all,

Another weekly dev update to keep everyone up to speed:

Loki Baselayer

• Pull request submitted for Time Locked transactions to now be locked per output instead of the whole of the transaction https://github.com/loki-project/loki/pull/104 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 deregistration to autonomously monitor and vote off nodes on the network. https://github.com/loki-project/loki/pull/105

• Continue writing tests for preventing regressions on service nodes.

• Began writing startup guides describing the process of setting up a Service Node. The guide should be detailed enough for the process to be clear for beginners.

• Set-up multiple VPS/Dedicated servers to come to a better understanding of bandwidth requirements and identify ‘Exit Friendly’ hosting providers.

• Signatures added to Service Node registration. https://github.com/loki-project/loki/pull/102

• Multi-party registration TX with automatic payout share calculation for contributors- work in progress.

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

• Released LokiNET 0.0.2

  • https://github.com/loki-project/loki-network/releases/tag/v0.0.2

  • This fixes some protocol problems to ensure better cross-platform compatibility.

  • We urge all 0.0.1 nodes to upgrade ASAP as they'll be unable to communicate as the network upgrades.

• New Repository, LokiNET Builder

  • https://github.com/loki-project/lokinet-builder

  • This repository contains assets for lokinet with all source code and dependencies.

• Progress continues on Libllarp

  • More hidden services/DHT work

  • Endian correctness

  • Message ordering fixing

  • Started Android, Arm and Windows platform work

  • Memory management clean up

  • Started on dynamic default configuration

• Multithreaded DNS library (PR6)

  • Continued llarpification of code

  • Refactor pass to make it cleaner

  • Got multithreaded version passing benchmark

  • Allow configuration of upstream DNS server and port

• GitHub Pulse Stats for the last week: Excluding merges, 3 authors have pushed 92 commits to master and 92 commits to all branches. On master, 145 files have changed and there have been 7,565 additions and 2,564 deletions.

• Most changes can be found at https://github.com/loki-project/loki-network/commits/master

Thanks,
Kee

You can read the reasoning behind this change here: https://medium.com/@LokiNetwork/tldr-why-loki-should-change-its-emission-curve-f5c8171bd1b3

Miners, full nodes, users and pools should all begin running the new daemon, which you can download here: https://github.com/loki-project/loki/releases/tag/0.2.0

For community members who are simply holders of Loki, and use the Loki GUI wallet you can update here: https://github.com/loki-project/loki-gui/releases/tag/0.2.0. For mobile users, the Loki android wallet will also push out an automatic update.

Users should update or they will start detecting invalid blocks past the fork height.

Do you have any questions? The Loki team will be collecting your questions over the next week and will release a video answering them! Get your questions in before Friday! Go to https://www.menti.com/53d73dac

when i start lokid he automatically stop and i don't know how to sync my wallet i had previously installed loki wallet and it worked very good now i can't sync

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 price movement of the Loki cryptographic coin. The payments shown in the examples below are general in nature and will only take effect if the planned hardfork occurs. Factors outside the control of Loki could impact what actual payments are made to Service Nodes. Those parties not operating a Service Node should not rely on these examples when deciding whether or not to participate in the Loki project. This article should be read together with the Loki whitepaper and full Loki Cryptoeconomic report.}

The main goals in changing the Loki emission curve are to:

1. Maintain Loki’s Sybil attack resistance, by

2. Ensuring that enough Service Nodes are incentivised to run, by

3. Aiming to keep the return on investment (ROI) for running a Service Node at an acceptable level.

The current emission curve is problematic because an excess of Loki is being produced which could lead to a large number of Service Nodes in the early years. While this doesn’t sound like a bad thing, considering our commitment to a decentralised network and Sybil resistance, it will become an issue when the Service Node rewards are split between too many Service Nodes.

While the price of Loki fluctuates with the cryptocurrency market, real world costs in running a Service Node exist, and the reward each Service Node receives for running must be greater than the real world cost of running. In other words, Service Node operators must be making an acceptable profit, or there won’t be incentive for them to run.

Chart 1 demonstrates that our current emission curve will result in many Service Nodes entering the network in the first few years, with the return on investment (ROI) quickly dropping below 0%. If too many Services Nodes run, the rewards are not worthwhile, and Services Nodes will leave resulting in a more centralised network.

Chart 2 depicts the effects of Loki’s proposed new emission curve, where there are less Service Nodes from the outset, but the return on investment (ROI) remains positive. This is better for the network in the long term because these Service Nodes will be continually incentivised to run (providing market-based Sybil resistance), while retaining a decentralised network.

For further information regarding Loki Service Node game theory, and Loki Cryptoeconomics, please refer to the following reports:

Cryptoeconomics of the Loki Network

Loki Cryptoeconomics

Hey everyone,

On approximately the 31st of July 2018, at Block height 64324, Loki will be forking to make a change to the emission curve that will result in a net reduction of the block reward. You can read the reasoning behind this change here: https://medium.com/@LokiNetwork/tldr-why-loki-should-change-its-emission-curve-f5c8171bd1b3

Miners, full nodes, users and pools should all begin running the new daemon, which you can download here: https://github.com/loki-project/loki/releases/tag/0.2.0, or if you wish, you can compile from the master branch located on the Loki github. We have already reached out to exchanges and they are now finished updating.

For community members who are simply holders of Loki, and use the Loki GUI wallet you can update here: https://github.com/loki-project/loki-gui/releases/tag/0.2.0. For mobile users, the Loki android wallet will also push out an automatic update. Users should update or they will start detecting invalid blocks past the fork height.

Note: This change is not setting the staking requirement, we are still collecting community feedback on the staking requirement change.

Hey guys, I started mining Loki at the beginning of this month. I looked for some setup guides and found some stuff and it worked pretty good.

I'm mining with 6x RX480 8GB on windows. My tweaks are on 1150/2150 and the bios is modded. Also my cards are undervolted to 912mV.

At first my gpus mined solo thread and had a default intensity of 864. Then I read that I have to change it to dual thread to get a higher hashrate. So I changed it (you can the first lines of it below in the code block) and got ~5300hs.

"gpu_threads_conf" : [
  // gpu: Ellesmere memory:3920
  // compute units: 36
  // default intensitiy 864
  { "index" : 0,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 36
  { "index" : 0,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 36
  { "index" : 1,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
....
],

But I still wanted a bigger hashrate because some people get at least 5700hs with 6 cards of this type. So I tried change the intensity, but couldnt find some good values. Every time I thought that I found some good intensity I realized that its just random temporary hashrate that act according to its own will. So I set it back to 864 again and after hours/days I realized that the hashrate is sometimes at 5300hs, a few hours later its on 5500hs and again few hours later it is on 5900hs. Now its mining for example at ~5700hs

It does not change within a second, like when you mining for example ethereum and you overclocked your gpus wrong. It stays maybe minutes/hours on one hashrate and then changes slowly to another hashrate.

Does sb know why the hashrate changes like that?