V1.1.2
+ Added algorithm 'sha256dt' (NOVO coin) for CPU/GPU mining, fee 0.85%
+ Added ETHASH/ETCHASH + SHA256DT dual mining mode
+ Added AUTOLYKOS2 + SHA256DT dual mining mode
+ Lowered devfee for 'sha512_256d_radiant' algorithm to 0.85% (CPU/GPU)
+ Reworked auto-tune procedure for GPU's
+ Added parameter '--gpu-disable-interleaving' which disables interleaving of threads (only when same GPU runs 2+ threads) - might get better hashrate in some cases
+ --gpu-buffer-mode 1 should work more stable on 4GB GPU's now
+ Bug fixes & minor improvements

V1.1.1
+ Added algorithm 'evrprogpow' (EVRMORE coin) for CPU/GPU mining, fee 0.85%
+ Performance increase on 'cryptonight_gpu' algorithm for RDNA/RDNA2 GPU's
+ Performance increase on 'sha512_256d_radiant' algorithm for RDNA2 GPU's
+ Performance increase on 'lyra2v2_webchain' algorithm for GPU's
+ Progpow algorithms bugfixes [kawpow, firopow, epic, sero, veil, veriblock, zano]
+ Added parameter '--force-msr-tweaks' which forces usage of MSR tweaks for CPU mined algorithm/s *
+ Added support for gfx1036
+ Fixed detection of RX550 GPU's on newer AMD drivers

***
MSR tweaking was enabled by default for every algorithm on previous miner versions if miner had admin/root privileges.
Not every CPU mineable algorithm benefits from this, so from this version it will be automatically enabled only to algorithms that are known to benefit from it.
If one wants to force enable MSR tweaking it can be done adding '--force-msr-tweaks' parameter

V1.1.0
+ Performance increase on 'sha512_256d_radiant' algorithm for GPU's
+ Small performance increase on 'sha512_256d_radiant' algorithm in DUAL mining modes [ ETHASH/ETCHASH/AUTOLYKOS2 ]

It's not a clean install if you have windivert service installed, cause that's what NAUGHTY5 indicates.

V1.0.9
+ Added algorithm 'pufferfish2bmb' for Polaris/Vega cards
+ Performance increase on 'sha512_256d_radiant' algorithm for GPU's
+ Reworked ZIL mining modes*
+ Added automatic caching of ZIL DAG for ETHASH/ETCHASH + ZIL (if GPU has enough VRAM to hold both DAG's)
+ Added nicehash compatibility for algorithm 'verushash'
+ Added parameter '--disable-auto-affinity'
+ Bug fixes

***
ZIL can be mined in a few ways :

1. ETHASH/ETCHASH + ZIL [ mining ETHASH/ETCHASH until ZIL time, then it switches to ZIL, mines it, and returns to ETHASH/ETCHASH mining. Uses a pool that automatically does the switching, ezil.me for example]
2. ZIL + Any algorithm [ mines the second algorithm until it's ZIL time - then it switches to ZIL, mines it, and returns to second algo mining when done with ZIL ]
3. ETHASH/ETCHASH + ZIL + ALPH/IRONFISH/HEAVYHASH/KASPA/RADIANT [ mines ETHASH/ETCHASH + ZIL on ezil.me for example, with the second algorithm simultaneously. ETHASH/ETCHASH + ZIL uses a pool that automatically does the ZIL switching, ezil.me for example ]

Examples:

1. ETCHASH + ZIL
--disable-cpu --algorithm etchash --pool stratum+tcps://eu.ezil.me:24443 --wallet etc-wallet.zil-wallet

2. ZIL + KASPA
--disable-cpu --a0-is-zil --algorithm etchash --algorithm kaspa --pool stratum+tcps://eu.ezil.me:24443 --pool ru.acc-pool.pw:16061 --wallet etc-wallet.zil-wallet --wallet kaspa-wallet

3. ETCHASH + ZIL + RADIANT
--disable-cpu --algorithm etchash --algorithm sha512_256d_radiant --pool stratum+tcps://eu.ezil.me:24443 --pool stratum-eu.rplant.xyz:7086 --wallet etc-wallet.zil-wallet --wallet radiant-wallet


Notes :
--a0-is-zil can be used only for case nr. 2! [ ZIL + Any algorithm ]
If you don't have enough VRAM for ZIL DAG + second algorithm's memory requirements, add --gpu-buffer-mode 1 to your cmd parameters

***
--disable-auto-affinity

Use this parameter if you have a multi node CPU, and the automatic affinity setup isn't working the way you want it.
You will need to run a miner instance per node, and define --cpu-threads manually.

Example in Windows :
start /NODE 0 /B /W SRBMiner-MULTI.exe --disable-auto-affinity --disable-gpu --cpu-threads 48 ...
start /NODE 1 /B /W SRBMiner-MULTI.exe --disable-auto-affinity --disable-gpu --cpu-threads 48 ...

V1.0.8
+ Added algorithm 'blake3_ironfish' (IRONFISH coin) for CPU/GPU mining, fee 0.85% *
+ Added ETHASH/ETCHASH + BLAKE3_IRONFISH dual mining mode
+ Added AUTOLYKOS2 + BLAKE3_IRONFISH dual mining mode
+ Added algorithm 'pufferfish2bmb' for RDNA cards [ 5xxx ]
+ Performance increase on 'autolykos2' algorithm for RX5700/XT GPU's
+ Small performance increase on 'kaspa' algorithm for RDNA cards [ 5xxx ]
+ Algorithm 'autolykos2' possible fix for situation when miner isn't creating dataset
+ Algorithm 'autolykos2' now uses 1 thread per GPU as default (was 2) - hashrate should be more stable
+ Possible fix for miner crashing when it's trying to reconnect to the pool

***
Algorithm 'blake3_ironfish' stratum implementation does not send back a message to the miner if share was accepted/rejected, so
you won't have statistics about this in the miner - only how many shares were sent to the pool.
Tested on zk.work pool.

Ironfish is at the moment running at an incentivized testnet.

V1.0.7
+ Added algorithm 'pufferfish2bmb' (BMB - Bamboo) for GPU mining [ rdna2 only ], fee 1.00%
+ Small performance increase on 'pufferfish2bmb' algorithm for CPU's
+ Reduced devfee for 'autolykos2' (ERGO) to 1.00%
+ Possible fix for 'Can't switch to algorithm 1' issue when using --multi-algorithm-job-mode 3
+ Bug fixes

V1.0.6
+ Added algorithm 'pufferfish2bmb' (BMB - Bamboo) for CPU mining, fee 1.00%*
+ Algorithm 'xdag' is now compatible with the new XDAGj network protocol

***
Algorithm 'pufferfish2bmb' stratum implementation supported only ( ffmpool.com )

You can do these combinations with SRBMiner :

ethash + kaspa
ethash + blake3_alephium
ethash + heavyhash
ethash + sha512_256d_radiant

etchash + kaspa
etchash + blake3_alephium
etchash + heavyhash
etchash + sha512_256d_radiant

autolykos2 + kaspa
autolykos2 + blake3_alephium
autolykos2 + heavyhash
autolykos2 + sha512_256d_radiant

V1.0.5
+ Added algorithm 'sha512_256d_radiant' (RAD - Radiant Layer One) for CPU/GPU mining, fee 1.00%
+ Added ETHASH/ETCHASH + SHA512_256D_RADIANT dual mining mode
+ Added AUTOLYKOS2 + SHA512_256D_RADIANT dual mining mode
+ Fixed issue with dual mining ethash using nicehash mode
+ Added automatic caching of ZIL DAG in dual mining mode [ETH/ETC] (if GPU has enough VRAM to hold both DAG's)
+ Added parameter '--gpu-ethash-dag-cache' to set caching of specific ETH/ETC epoch in dual mining mode [ def. is epoch 0 - ZIL ]

That's not possible.

V1.0.4
+ Improved performance on all dual mineable algorithms for RDNA2 GPU's
+ Minor bug fixes

Same as for every other algorithm, stratum only.

V1.0.3
+ Added algorithm 'mike' (Vkax coin) for CPU mining, fee 0.85%
+ Significantly improved performance on 'curvehash' algorithm for GPU's
+ Reduced devfee for 'kaspa' and 'heavyhash' to 0.85%
+ Using any of the supported dual mining combinations, automatically enables auto tune
+ Added possibility to disable an algorithm in dual mining mode per GPU*
+ Default value for '--gpu-dual-max-loss' is lowered from 5% to 3%*

***
It is now possible to disable one of the algorithms in dual mining mode per GPU.

--gpu-id ETHASH_GPUS;KASPA_GPUS [separator between GPU's is !, as usual]

For example you have a 4 GPU rig and want to dual mine ETH+KAS on GPU's 0,1,3 and ETH only on GPU 2 (without KAS) :

--gpu-id 0!1!2!3;0!1!3


***
--gpu-dual-max-loss parameter should be used to set the ratio between the hashrates of the two algorithms in dual mining mode.
Lower value gives higher priority to the first algorithm (ETH/ETC/AUTOLYKOS2).
As always, GPU CORE clock affects the effectiveness of this parameter. Sometimes a slightly higher CORE clock can make a big difference.

Devfee is mined on a different connection, not the same you are connected to the pool. Also you won't see any devfee shares sent on the screen/log - it's not displayed to the user.
What happened in your case that i don't know, but i am almost certain it's wasn't mining to my devfee wallet. There are also a few mechanisms that abort devfee mining if it might get stuck.

V1.0.2

+ Added ETHASH/ETCHASH + HEAVYHASH (OBTC/PBTC) dual mining mode
+ Added AUTOLYKOS2 + HEAVYHASH dual mining mode
+ Faster DAG creation on RDNA2 GPU's
+ Possible fix for case when some RDNA/RDNA2 GPU's won't create DAG for ETHASH/PROGPOW algorithms on Linux based OS

No

V1.0.1

+ Added auto tune for dual mining (use --gpu-auto-tune 1 to enable)*
+ Added parameter '--gpu-dual-max-loss' which defines the maximum loss of A0 hashrate we allow while auto tuning in dual mode, defined in percent
+ Minor bug fixes

***
Auto tune for dual mode:

Auto tune will try to find the best intensity value for the SECOND algorithm, which heavily depends on the CORE clock of your GPU.
Higher the clock, probably higher the intensity value will be.

You can set the maximum loss of hashrate (in percent) you allow for the FIRST algorithm by using the '--gpu-dual-max-loss' parameter which accepts a number between 1 and 90.
Default for this value, if not set, is 5%.

Dual ethereum/kaspa example [allow max 10% loss in hashrate for ethereum]:

V1.0.0

+ Added ETHASH/ETCHASH + BLAKE3_ALEPHIUM dual mining mode
+ Added AUTOLYKOS2 + BLAKE3_ALEPHIUM dual mining mode
+ Fixed ETHASH/ETCHASH + KASPA mining on nicehash
+ Added parameter '--gpu-table-slow-build' which slows down DAG/Datatable creation for ETHASH/ETCHASH/UBQHASH/PROGPOW/AUTOLYKOS2 algorithms (might help in avoiding crash)
+ Parameter '--gpu-dual-mode' isn't needed anymore, miner will auto check if selected algorithms are eligible for dual mining
+ Fixed a few bugs related to dual mining mode

Dual mining tips:

Same as before, it is important to follow this simple rule:

If you increase CORE clock of the GPU because you want higher hashrate on A1 (KASPA/ALEPHIUM), you probably should also increase intensity of the SECOND algorithm too!
Not doing so might leave you on the same hashrate even if you increased the CORE clock!

Example:

Leave intensity of A0 on auto, and set intensity of A1 to 4 : --gpu-intensity 0 --gpu-intensity 4 , or --gpu-intensity 0;4

Dual ethereum/alephium example:

--disable-cpu --algorithm ethash --algorithm blake3_alephium --pool ethereum-pool-here --pool alephium-pool-here --wallet ethereum-wallet-here --wallet alephium-wallet-here

Dual ergo/alephium example:

--disable-cpu --algorithm autolykos2 --algorithm kaspa --pool ergo-pool-here --pool alephium-pool-here --wallet ergo-wallet-here --wallet alephium-wallet-here

0.9.9

+ Improved performance of KASPA mining in dual mode for ETH/ETC+KASPA and AUTOLYKOS2+KASPA for some GPU's [ read instructions below* ]
+ Added algorithm 'curvehash' for GPU mining*
+ Fixed compatibility of KawPow with miningpoolhub pool


***
Dual mining tuning:

Intensity of the second algorithm (KASPA) affects how much time should be spent on mining the second algorithm (KASPA).
Value of intensity goes from 1-31 , but everything over 8 will probably only degrade performance of both algorithms too much.

There is only one tip : if you want more KASPA you will need to increase CORE clock AND also the intensity of the second algorithm (KASPA)
Increasing only CORE clock without setting a higher intensity value probably won't increase KASPA hashrate.

Some GPU's can use only predefined intensities:

Polaris : 1, 2, 4
Rx550/Rx560 : 1

***
Curvehash GPU:

This is a quick release - it was tested on Windows on drivers < 22.x. and it should work ok.
Linux and mining os-es were barely tested - polaris works - not sure about the rest.. Rocm is not supported.

If a pool has a very low start diff. you should use parameter '--diff-factor' so you shouldn't flood the pool with shares.

OC Tip: MEM clock should go down as much as possible, CORE should go up as much as possible