SRBMiner-MULTI AMD & NVIDIA & INTEL & CPU miner

[doktor83]

Hi doktor83,

do you have a link for checking the mining on pool1.dynamocoin.org? My console summary is 11 MH/s (all GPUs) with your new version 0.9.2 but i will see it in real !!!!!

Thanks.

I just found out there is this : http://pool1.dynamocoin.org:8086/main.html

You should go into dynamo discord and ask there if you have further questions regarding this pool.

[1713305117]

1713305117

[doktor83]

V0.9.3
+ Performance increase on 'curvehash' algorithm (Pulsar coin) (up to ~40% on some CPU's)
+ Removed algorithm 'argon2id_ninja'
+ Minor bug fixes

[doktor83]

V0.9.4

+ Added algorithm 'sha3d' (Bsha3, Kylacoin, Yilacoin) for CPU/GPU mining, fee 0.85%
+ Added algorithm '0x10' (CHOX - ChainOX) for CPU/GPU mining, fee 0.85%
+ Performance increase on 'curvehash' algorithm (Pulsar coin) ( ~25% )
+ Removed 'astrobwt' algorithm
+ Removed parameter '--gpu-cn-mode'
+ Fixed issue [ https://github.com/doktor83/SRBMiner-Multi/issues/100 ]

[vuli1]

does anyone have an idea how to add srbminer back to Nicehash?
I followed this guide https://github.com/nicehash/NiceHashMiner/tree/master/doc/UserPlugins
but it doeasnt start the miner, neither the benchmark. my guess is algorithm_command_line is wrong or smth...

[doktor83]

does anyone have an idea how to add srbminer back to Nicehash?
I followed this guide https://github.com/nicehash/NiceHashMiner/tree/master/doc/UserPlugins
but it doeasnt start the miner, neither the benchmark. my guess is algorithm_command_line is wrong or smth...

They removed SRBMiner cause i / a lot of other mining software don't comply to their new policy. So my guess is you won't make it work cause they don't want you to run it.

[vuli1]

well, it is possible but version 0.6.0.
I copied miner ID from version 3.0.7.0 and I made new folder in 3.0.7.2 with name of that ID. I copy/paste Srbminer.dll to this new folder and after restart of NH miner was downloaded, but yes, the old version.

EDIT: Afterthat you can extract new version to that folder... I just found a video on YT for adding back Trex minner, it is the same procedure.

[doktor83]

V0.9.5
+ Added algorithm 'yescryptr8' for GPU mining, fee 0.85%
+ Added algorithm 'yescryptr16' for GPU mining, fee 0.85%
+ Added algorithm 'yescryptr32' for GPU mining, fee 0.85%
+ Added algorithm 'frkhash' (Expanse's next algorithm) for CPU/GPU mining, fee 0.85%
+ Lowered devfee for 'autolykos2' algorithm to 1.5%
+ Lowered devfee for 'blake3_alephium' algorithm to 0.85% (CPU/GPU)
+ Small performance increase on 'autolykos2' algorithm for RDNA2 GPU's
+ Small performance increase on 'dynamo' algorithm for GPU's
+ A little bit faster dataset creation on 'autolykos2' algorithm for some GPU's
+ A little bit lower power consumption on 'autolykos2' algorithm for Ellesmere GPU's
+ A little bit lower power consumption on 'ethash' algorithm for RDNA2 GPU's
+ A little bit lower power consumption on 'etchash' algorithm for RDNA2 GPU's
+ If using --cpu-threads parameter, affinity is now auto set for CPU's with 64+ threads too
+ Added parameter '--set-console-title' (Windows only) [set custom title to miner console window]
+ Added parameter aliases for --algorithm, --cpu-threads, --password, --pool, --wallet ( -a, -t, -p, -o, -u )
+ Parameter '--diff-factor' now accepts values in decimal format too
+ Removed support for older GPU's (pitcairn, tahiti, hawaii, fiji, tonga)
+ Minor bug fixes

Why was support for older cards removed?

Although those cards are really old, the real reason for removing support for Pitcairn, Tahiti, Hawaii, Fiji and Tonga is that i don't own any of these GPU's, meaning i can't test / optimise any code for them.

[entryboy]

V0.9.5
Why was support for older cards removed?

Although those cards are really old, the real reason for removing support for Pitcairn, Tahiti, Hawaii, Fiji and Tonga is that i don't own any of these GPU's, meaning i can't test / optimise any code for them.

Oh, no!! Not the Fiji, they are good and have RAM speed (HBM1).

Can you reactivate the the Fiji ? I ask for a good friend.

Thanks.  

[doktor83]

V0.9.6
+ Added algorithm 'kaspa' (KAS - Kaspa coin) for CPU/GPU mining, fee 1.00%
+ Small performance increase on 'heavyhash' algorithm for RDNA2 GPU's
+ Lower power consumption on 'heavyhash' algorithm for RDNA2 GPU's
+ Minor bug fixes

[tale01]

V0.9.6
+ Added algorithm 'kaspa' (KAS - Kaspa coin) for CPU/GPU mining, fee 1.00%
+ Small performance increase on 'heavyhash' algorithm for RDNA2 GPU's
+ Lower power consumption on 'heavyhash' algorithm for RDNA2 GPU's
+ Minor bug fixes

Please support fiji 

[doktor83]

Which driver is last supported for windows in this version

Shouldn't really matter. You got issues on a specific version, or ?

[Nighthog]

V0.9.5
+ Added algorithm 'yescryptr8' for GPU mining, fee 0.85%
+ Added algorithm 'yescryptr16' for GPU mining, fee 0.85%
+ Added algorithm 'yescryptr32' for GPU mining, fee 0.85%

+ A little bit lower power consumption on 'ethash' algorithm for RDNA2 GPU's
+ A little bit lower power consumption on 'etchash' algorithm for RDNA2 GPU's
+ If using --cpu-threads parameter, affinity is now auto set for CPU's with 64+ threads too
+ Added parameter '--set-console-title' (Windows only) [set custom title to miner console window]
+ Added parameter aliases for --algorithm, --cpu-threads, --password, --pool, --wallet ( -a, -t, -p, -o, -u )
+ Parameter '--diff-factor' now accepts values in decimal format too
+ Minor bug fixes

Great work here!

Interesting to see the yescryptR 8/16/32 algorithms on the GPU.

Getting some 12~13kH/s with a 6900XT on [R16] as I was gathering some QOGE for fun.
A little better than on CPU 8core Ryzen for ~2kH/s.

Better efficiency on GPU ~250W vs CPU ~100W PPT values.

[doktor83]

V0.9.7

+ Performance increase on 'kaspa' algorithm for RDNA2 GPU's
+ Performance increase on 'heavyhash' algorithm for RDNA2 GPU's
+ Lower power consumption on 'kaspa' algorithm for RDNA2 GPU's
+ Lower power consumption on 'heavyhash' algorithm for RDNA2 GPU's
+ Added limited support for some algorithm's on Vega's (gfx900) for drivers newer than 20.40 (Linux - ROCm) *
+ Added GPU power reading capability for Polaris/Vega on Windows
+ OpenCL variables will be now set automatically from miner

***
Supported algorithms for Vega ROCm: ethash, etchash, autolykos2, kaspa, progpow_epic, cryptonight_xhv, cryptonight_gpu, verthash

Note : Performance of these algorithms is much better on older (20.40) drivers!

[doktor83]

V0.9.8

+ Added ETHASH/ETCHASH + KASPA dual mining mode
+ Added AUTOLYKOS2 + KASPA dual mining mode
+ Performance increase on 'curvehash' algorithm for CPU ( up to ~40% )
+ Added parameter '--gpu-dual-mode' which must be used to enable the new dual mining mode
+ Upgraded command line parser*
+ Bug fixes

***
To maximise your mining profits, SRBMiner added real dual mining of :

ETHASH/ETCHASH + KASPA
AUTOLYKOS2 + KASPA

This feature is still in experimental/beta phase, so feedback is welcome.

Setup procedure for the new dual mining mode is exactly the same as before, you just need to append parameter '--gpu-dual-mode' to enable the new mode.

You can manually set the intensities for both algorithms if you wish, it can have a positive/negative impact on the hashrates.
An auto tuning mode for the new dual mining is planned to be added in the future.
Currently using the '--gpu-auto-tune' parameter won't do anything.

Dual ethereum/kaspa example:

--disable-cpu --algorithm ethash;kaspa --gpu-dual-mode --pool ethereum-pool-here;kaspa-pool-here --wallet ethereum-wallet-here;kaspa-wallet-here

Dual ergo/kaspa example:

--disable-cpu --algorithm autolykos2;kaspa --gpu-dual-mode --pool ergo-pool-here;kaspa-pool-here --wallet ergo-wallet-here;kaspa-wallet-here


***
Upgraded command line parser:

Order of parameters doesn't matter anymore, parser will internally fix ordering.
Also there is a new way of defining multiple algorithms, parameters will be merged.

Example :
--algorithm ethash;kaspa can be written as --algorithm ethash --algorithm kaspa

Rule is that first defined parameter will be defined for algorithm1, same parameter if used will be defined for algorithm2 , etc..

Example:
--algorithm ethash;kaspa --gpu-intensity 24;23 can be written as --algorithm ethash --gpu-intensity 24 --algorithm kaspa --gpu-intensity 23


Example for previous ethereum/kaspa can be written as (ex.):

--gpu-dual-mode --algorithm ethash --pool ethereum-pool-here --wallet ethereum-wallet-here --algorithm kaspa --pool kaspa-pool-here --wallet kaspa-wallet-here --disable-cpu

[doktor83]

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

[doktor83]

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

[doktor83]

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]:

Code:

--disable-cpu --gpu-auto-tune 1 --gpu-dual-max-loss 10 --algorithm ethash;kaspa --pool ethereum-pool-here;kaspa-pool-here --wallet ethereum-wallet-here;kaspa-wallet-here

[LaaMos Seeth]

Hey! Is it possible to use SRBMiner for solo mining without stratum?

[doktor83]

Hey! Is it possible to use SRBMiner for solo mining without stratum?

No

[LaaMos Seeth]

Hey! Is it possible to use SRBMiner for solo mining without stratum?

No

Sorry to bother you, but can you create such version to mining in solo like in good old days? Or it is too hard to realize technically ?