So, what OS are you using? I'm trying to find a pattern here because I'm hearing other ETH miners have the same issue.

Yes I can see the memtweak is off, thanks. However, I'm very surprised about your 1080 being slower than my 1070Ti on epoch 383. I'm getting 24.5Mh/s with PL 90W, CORE 0, MEM +1000. DAG generation time is ~8.8s, without memory tweaks

Hmm, very curious indeed. I did a benchmark with my 1070Ti with --mt 5 on Linux and didn't notice a hashrate decrease for 383/384 epoch threshold. Could you try benchmarking without --mt?
UPD: What OS are you using? Win 7 by any chance?

20201121 13:45:23 WARN: BENCHMARK MODE (ethash)
20201121 13:45:23 WARN: EPOCH 383
20201121 13:45:23 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20
20201121 13:45:26 GPU #0: generating DAG 3.99 GB for epoch 383 ...
20201121 13:45:38 GPU #0: DAG generated [time: 12377 ms], memory left: 3.58 GB
20201121 13:45:55 GPU #0: using kernel #2
20201121 13:45:56 Total: 21.47 MH/s
20201121 13:45:58 Total: 21.48 MH/s

20201121 13:46:40 WARN: BENCHMARK MODE (ethash)
20201121 13:46:40 WARN: EPOCH 384
20201121 13:46:40 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20
20201121 13:46:43 GPU #0: generating DAG 4.00 GB for epoch 384 ...
20201121 13:46:55 GPU #0: DAG generated [time: 12389 ms], memory left: 3.57 GB
20201121 13:47:13 GPU #0: using kernel #5
20201121 13:47:14 Total: 20.87 MH/s
20201121 13:47:16 Total: 20.88 MH/s

I reckon this info is only relevant for 4GB cards where the GPU can't hold the entire DAG. 1080Tis have plenty of memory, so it must be something different. You can do some experiments with "t-rex -a ethash --benchmark --benchmark-epoch NNN" and see how it behaves for different epochs

20201121 11:30:24 WARN: BENCHMARK MODE (ethash)
20201121 11:30:24 WARN: EPOCH 383
20201121 11:31:10 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:31:13 GPU #0: generating DAG 3.99 GB for epoch 383 ...
20201121 11:31:20 GPU #0: DAG generated [time: 8008 ms], memory left: 3.28 GB
20201121 11:31:37 GPU #0: using kernel #2
20201121 11:31:38 Total: 33.39 MH/s
20201121 11:31:40 Total: 33.39 MH/s

20201121 11:32:32 WARN: BENCHMARK MODE (ethash)
20201121 11:32:32 WARN: EPOCH 384
20201121 11:33:02 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:33:05 GPU #0: generating DAG 4.00 GB for epoch 384 ...
20201121 11:33:13 GPU #0: DAG generated [time: 7936 ms], memory left: 3.27 GB
20201121 11:33:30 GPU #0: using kernel #5
20201121 11:33:31 Total: 20.89 MH/s
20201121 11:33:33 Total: 20.88 MH/s

20201121 11:34:52 WARN: BENCHMARK MODE (ethash)
20201121 11:34:52 WARN: EPOCH 385
20201121 11:35:22 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:35:25 GPU #0: generating DAG 4.01 GB for epoch 385 ...
20201121 11:35:33 GPU #0: DAG generated [time: 7950 ms], memory left: 3.27 GB
20201121 11:35:51 GPU #0: using kernel #5
20201121 11:35:54 Total: 20.72 MH/s
20201121 11:35:56 Total: 20.72 MH/s

20201121 11:37:05 WARN: BENCHMARK MODE (ethash)
20201121 11:37:05 WARN: EPOCH 390
20201121 11:37:36 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:37:38 GPU #0: generating DAG 4.05 GB for epoch 390 ...
20201121 11:37:46 GPU #0: DAG generated [time: 8030 ms], memory left: 3.22 GB
20201121 11:38:04 GPU #0: using kernel #5
20201121 11:38:05 Total: 20.66 MH/s
20201121 11:38:07 Total: 20.66 MH/s

20201121 11:38:58 WARN: BENCHMARK MODE (ethash)
20201121 11:38:58 WARN: EPOCH 395
20201121 11:39:29 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:39:32 GPU #0: generating DAG 4.09 GB for epoch 395 ...
20201121 11:39:39 GPU #0: DAG generated [time: 8111 ms], memory left: 3.24 GB
20201121 11:39:57 GPU #0: using kernel #5
20201121 11:39:58 Total: 20.40 MH/s
20201121 11:40:00 Total: 20.41 MH/s

Wow, that difference in hashrate can't be explained by a not functioning memory tweak. "--mt" is only supposed to boost your hashrate by a couple of MH/s per card, there's definitely something else going on. I've seen similar reports elsewhere it's a common problem regardless of what miner is used. I'm not aware of a solution for this issue, unfortunately.

It does

It depends on the liquidity chart. It's possible that Latoken has more premium coins. It depends on when you deposited those coins on Latoken as well, how premium were they? If you purchased reserve it depends on who you bought it from, how premium/fast did those coins convert?

The only difference between Latoken and the wallet is the exchange does what's called "liquidity mixing" where for a smoother trading experience a user who buys liquid will have a share in the total liquidity pool for the users at that moment who are also liquid. This prevents a user from accidentally buying sub-premium liquidity because they can't see a users liquidity distribution chart. The reserve however is very specific and it's somewhat random the reserve quality you buy from a reserve seller. Although I suspect most of the reserve is premium because of people who deposited later with a better set of liquid coins.

So please I want you to take a look at the send tab and then activate coin select. Then look at all the inputs you can possibly spend. You will notice each input has a liquidity chart. If you click on that chart you can see that each chart is different and the amount of coins distributed is different for each index. You can also see these charts on the block explorer too.

The pegging works by balancing the wallet amounts based on present liquidity and votes, so depending on what the people want and the liquidity of Bitbay forces the coins in reserve to keep price stable. The reason you cannot see the trading on Latoken is because Bitbay is presently under maintenance, don't worry trading will resume soon.

This may happen as not 100% nodes were updated before hard fork.
So you unluckily stuck into abandoned chain looks like.
Simplest and quick way:

1. stop qt wallet
2. backup wallet.dat somewere
3. remove all files in datafolder except wallet.dat
4. place bootstrap.dat in datafolder
5. start qt wallet

bootstrap file is updated up to Jan 23 - bypassing fork point, so you should be safe after resync.
it may take 2-3 hours to load from bootstrap which is much faster then ordinary resync.

What do you mean by adding BitBay? I know it's a European exchange with several altcoins but there's no CLAM pair.

We are now open for trading:  https://freebitcoins.com/xchange/market/BTC_CLAM

Thanks for waiting.

No KYC, no daily withdraw limits, no bullshit, all crypto.  Gl & hf.

Guys, you should update the wallets to the latest version. This is a compulsory update, otherwise you will not be able to use your coins. Also the collateral to make MN is 10000 coins now.
Follow the steps:
1. Copy paste the wallet.dat file somewhere safe and then delete the entire Harvest folder.
2. Install the new wallet from the below link for wallets: https://github.com/HarvestMasternodecoin/HarvestCore/releases
3. You might see warning messages, click OK and proceed, once the wallet syncs, you can close wallet and then replace the wallet.dat with the old backed up wallet.dat file
4. Restart wallet to see your previous balance.
5. There will be some lost coins as we rolled back the chain to 15th June to get people back on single blockchain instead of the multiple blockchains they were on.
Source Code : https://github.com/HarvestMasternodecoin/HarvestCore
One Click MN Setup : https://github.com/HarvestMasternodecoin/OneClick_MN_Setup[/size]

I understand. I will look into this. It is specific to the nicehash version and is the result of an unexpected change from bitmain. They have removed fan control from the user in their latest releases. I will see if o can add that back in.

-j