What causes the odd cyclical difficulty peaks every hour or so? Doesn't seem to correlate with hash rate increasing or decreasing and the "unknown" blocks make up almost 50% of the daily blocks to random addresses versus the pools holding the majority of the hash rate.
Also, is the PoS blocks just an error on MPS or is staking part of BTCZ?
https://miningpoolstats.stream/bitcoinz

Just curious, I am interested in investing more into BTCZ before the price grows even more.

The block confirmation times seem to go from a few seconds to up to 30+ minutes per block due to this, which could cause some issues down the road.
What difficulty adjustment method is used?

Is there a link that is WGET friendly for Linux?

What CPU or settings were being used to reach 37H with a single wallet?

I'm having the same issue, only about 2 cores being used, no matter how many threads, and even on a 5900X getting 10H, while the network is over 2KH from launch.
Mined all night and not even 1 block.
Plus only 2.6 coins per block, worth 11 cents each.

When mining Flux on a pool, how do you determine what address you receive your parallel rewards to?

For those without a LHR card would there be any benefit to this beyond spreading out risk between coins?
Also +1 on Flux

Using 1.24 Ubuntu 18 :
OpenCL driver version: 470.82
00:00:00 [2021-11-12 22:43:26.417] Cuda driver version: 11.4
00:00:00 [2021-11-12 22:43:26.417] Cuda runtime API version: 11.4

terminate called after throwing an instance of 'cuda_runtime_error'
terminate called recursively
terminate called recursively
terminate called recursively
Aborted (core dumped)

Going to try updating drivers

Edit: Getting closer?
00:00:00 [2021-11-12 23:04:31.759] OpenCL driver version: 495.29
00:00:00 [2021-11-12 23:04:31.843] Cuda driver version: 11.5
00:00:00 [2021-11-12 23:04:31.843] Cuda runtime API version: 11.5


terminate called after throwing an instance of 'cuda_runtime_error'
  what():  CUDA error in func set_constants at line 925 invalid device symbol
Aborted (core dumped)

Not sure what to do, T-rex and others working but I wanna go faster

Is it possible to get 1.21 with Cuda 11.5 for Linux?
I'm using Ubuntu 18.04 which has always done solid for me.
Should I upgrade to 20.04?

Also if I have a high CPU load should I use the no cpu usage switch?
I've tried increasing the niceness priority but for some reason can't get below 0 without renice which breaks my script
Does dual mining eth zil on the same pool need any tags or slow things down like ssl?

I also use T-rex and having this issue as well, tried low default and high intensity and kernels.
Client side is 32mh~ the highest Ive seen and client pool rate says higher than that usually.
But pool side the rate 20-40% less after a couple 6 hour tests. Around 1% stales which are paid at 80%.
T-rex is about 29.5MH but poolside is exactly that as well.
This is on a 1070 setup Linux latest drivers and version plus older ones.

I am using SSL on both Trex and TBM.
Could SSL or something else make that much of a difference on TBM but not Trex?
I need to try other pools.

Any plans on 11.5 cuda for Linux or does it help much compared to 11.4?

I was curious if there was a way to tell when the miner is collecting it's dev fee, to help check pool rates.
I saw that it's continuous, but wasn't exactly sure how that would affect hash rates pool side.  Is it like 1 second every 200 seconds or something else? I don't see it mentioned in the logs.

Is it possible to get a 11.2 Ubuntu 18 build?

Excited to try out 1.15 with my new Linux rig!

0.8.6 works with the latest drivers for VII and XT series.
Very good speeds 62MH 6800XT and 86.5MH+ on VII with no memory timing changes.
Able to still use 6800XT as main display watching videos and even some games no issue.

I assume there may be a way to squeeze more out of 6xxx series in the future? Since smaller chips but uses about the same watts as the R7 but with less hash?
This isn't a problem of TRM as all software does this that I have tried.

Thanks for your work!

Thanks for the info no xintensity!
In regards to Vega and VII, with default mem timings other miners(with OLD drivers which I don't wanna run) seem to get better speeds.  The Watt Usage is 50 less though so I don't mind it much!
However also your 6000 series speeds are insanely good pool side seems to be hitting 70s at time, while others are high 50s. 7% higher at least local and so far 15% higher pool side with MPH.
If I could just get my R7 up to around 70-80mh with TBM I'd be sooo happy.
In fact maybe it's hitting those speeds pool side and just not showing it PC side.  I'll report back later.
Because I hit 170mh pool side at times with just 2 cards.

Thank you so much for the update and information!

What's the max --xintensity for AMD? 25?

First, big fan of your work over the years sp_ !
Second, I am trying to tweak my R7 to get the old hashrate I used to get with much older drivers.
Yours work with the very latest AMD drivers.
I'm getting very low watt usage about 50 watts less than usual, but also almost half the speed.
I'm not sure if it's from the drivers or intensity or what.
Using the same clock volt settings as before.
I get 1MH faster for my 6800.

Is there a way to see the intensity currently being used with Dynamic?
Also being able to set different intensity for different cards would be great!

Any plans on adding support for Radeon VII with newer drivers? 
I updated to most recent drivers for the 6800 XT, which really helped a lot of features and stability, but it killed my R7.
Works with other miners, but really like TRM

Anyone happen to still use them? I see a lot of volume on calculator websites, but curious if it's faked or something else.

What pools could you recommend for stale share support?

Any update on Pacmic 2021 being refunded?