SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[feekiller]

V1.6.6


+ DevFee mining is not displayed anymore to the user. The first devfee isn't mined in the first 5 minutes, so if you want to kill / restart the miner, set your scripts to do it before 5 minutes.
Also if using a custom algo switching software (that restarts the miner) , you are using the miner in normal mode (not algo switching mode), so the devfee is not tracked across switches.

NICE. OR ALL USE THIS:

DEVFEE = 0

Ver 1.6.4

Start.bat

start coin.bat
timeout 6970
taskkill SRBMiner-CN.exe
start start.bat



OR:
Start.bat

start "coin.bat"
timeout 6970
taskkill /F /IM "SRBMiner-CN.exe"
start "start.bat"

[1713872096]

1713872096

[1713872096]

1713872096

[1713872096]

1713872096

[christiano88]

V1.6.6


+ DevFee mining is not displayed anymore to the user. The first devfee isn't mined in the first 5 minutes, so if you want to kill / restart the miner, set your scripts to do it before 5 minutes.
Also if using a custom algo switching software (that restarts the miner) , you are using the miner in normal mode (not algo switching mode), so the devfee is not tracked across switches.

NICE. OR ALL USE THIS:

DEVFEE = 0

Ver 1.6.4

Start.bat

start coin.bat
timeout 6970
taskkill SRBMiner-CN.exe
start start.bat



OR:
Start.bat

start "coin.bat"
timeout 6970
taskkill /F /IM "SRBMiner-CN.exe"
start "start.bat"

Dude, just GTFO already...

[hmgp]

Thanks Dok! Trying Monero on nanopool and I have 4 Vega 56 - 2 are Sapphire, 1 is MSI, 1 is Powercolor, in case this detail matters. It goes off correctly, connects to the pool and just stays there getting jobs but doing zero shares... switch the miner and I have shares after 5 secs, but I really don't want to switch miner

Let's try this :

Working! Thank you =) Must have been something with the regedit I was doing before. I'll leave it for now and later on try to add the --resetvega, min_rig_speed and try to put the overdrive profiles on the start bat so it's called in the beginning.

Thanks again

[citronick]

doktor,

For pools file:

Can I put moneroocean pool as the first pool, and non-algo swicthing pool, ie xmr.nanopool in the subsequent pools.

I assume, sbrminer will lock in the first pool and will failover to 2nd pool when moneroocean pools goes offline.

At the moment this is working with 2 x Vega54 with latest blockchain drivers.

Thanks

[dragonmike]

At the moment this is working with 2 x Vega54...

Are these the extra-marital love children of a Vega 56 daddy and a Vega 64 mommy?

[citronick]

At the moment this is working with 2 x Vega54...

Are these the extra-marital love children of a Vega 56 daddy and a Vega 64 mommy?

LOL.... given the crypto bloodbath, your post really made my day... ha ha!

[doktor83]

doktor,

For pools file:

Can I put moneroocean pool as the first pool, and non-algo swicthing pool, ie xmr.nanopool in the subsequent pools.

I assume, sbrminer will lock in the first pool and will failover to 2nd pool when moneroocean pools goes offline.

At the moment this is working with 2 x Vega54 with latest blockchain drivers.

Thanks

it will detect that pool is not capable of algo switching, so it will revert back to normal mode (itt will turn off the --usealgoswitching)

[duyquang06]

- If using Blockchain drivers, hashing speed should be like it was before in ver 1.6.2


U save my vegas, again !

Just out of curiosity, why dont you use some of the preferred drivers?

Because it BlueScreenOfDeath everytime i install new driver, no matter which version, idk why, and yes i try so fucking many drivers version, so tired. So i just stick with Aug23.

[wgestickley]

Do i have to setup a own config file for xtl tu use Algo switch?

[doktor83]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

[wgestickley]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

Understood

5 supported algos - 5 configs

[doktor83]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

Understood

5 supported algos - 5 configs

that's right. Its better this way because you can set everything separately for every algo, like min_rig_speed, reboot_script etc

[iisbetoq]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

Understood

5 supported algos - 5 configs

that's right. Its better this way because you can set everything separately for every algo, like min_rig_speed, reboot_script etc

how about pools ? do i need make separated pools ? or just change on algos.txt
pools" : "pools-algoswitch.txt", to pools" : "pools-normalv7.txt",

[N2DCRYPT]

Dok, thanks for all your wonderful work on this miner, been on it for a while!

I'm curious, could you clarify how MoneroOcean works? I can figure most stuff out on my own, and I've got algoswitch algos and config files all setup and going, but one thing that confuses me is that I'm only getting NormalV7 jobs, even if I modify my algos.txt file for normalv7 hashes down to 200 H/s.

How can I verify and be sure that the switcher works and will switch to other algos when they're more profitable? Or does MoneroOcean decide what coin will be mined by all miners regardless of individual hashrate? Will appreciate any help!

[doktor83]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

Understood

5 supported algos - 5 configs

that's right. Its better this way because you can set everything separately for every algo, like min_rig_speed, reboot_script etc

how about pools ? do i need make separated pools ? or just change on algos.txt
pools" : "pools-algoswitch.txt", to pools" : "pools-normalv7.txt",

At the moment only Monero Ocean is the only pool supporting this so you can set it in pools-algoswitch.txt :

{
"pools" :
[
{"pool" : "gulf.moneroocean.stream:10016", "wallet" : "your-xmr-wallet", "password" : "x"},
{"pool" : "de.moneroocean.stream:10016", "wallet" : "your-xmr-wallet", "password" : "x"},
]
}

then in algos.txt set on every algo the pool to pools-algoswitch.txt.

So you made only 1 pool file.

[doktor83]

Dok, thanks for all your wonderful work on this miner, been on it for a while!

I'm curious, could you clarify how MoneroOcean works? I can figure most stuff out on my own, and I've got algoswitch algos and config files all setup and going, but one thing that confuses me is that I'm only getting NormalV7 jobs, even if I modify my algos.txt file for normalv7 hashes down to 200 H/s.

How can I verify and be sure that the switcher works and will switch to other algos when they're more profitable? Or does MoneroOcean decide what coin will be mined by all miners regardless of individual hashrate? Will appreciate any help!

it should send you jobs based on your own hashrate + some calc it does on the profitability. I don't know how it works.
To test it try setting an algo hashrate other than normalv7 to a high number

[iisbetoq]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

Understood

5 supported algos - 5 configs

that's right. Its better this way because you can set everything separately for every algo, like min_rig_speed, reboot_script etc

how about pools ? do i need make separated pools ? or just change on algos.txt
pools" : "pools-algoswitch.txt", to pools" : "pools-normalv7.txt",

At the moment only Monero Ocean is the only pool supporting this so you can set it in pools-algoswitch.txt :

{
"pools" :
[
{"pool" : "gulf.moneroocean.stream:10016", "wallet" : "your-xmr-wallet", "password" : "x"},
{"pool" : "de.moneroocean.stream:10016", "wallet" : "your-xmr-wallet", "password" : "x"},
]
}

then in algos.txt set on every algo the pool to pools-algoswitch.txt.

So you made only 1 pool file.

ah i see, i use this proxy https://github.com/sebseb7/cryptonote-proxy
atm i use for 1 variant to change other coin, when i want change to other variant i must turn-off my miner then turn-on again

[wgestickley]

In MO the three Coins

XHV
TUBE
RYO

has the same algo (Heavy), but in SRB each are different
(SABER, HEAVY, HAVEN)

Which should I put in the switch config file?

[N2DCRYPT]

In MO the three Coins

XHV
TUBE
RYO

has the same algo (Heavy), but in SRB each are different
(SABER, HEAVY, HAVEN)

Which should I put in the switch config file?

All of them. Haven and Bittube use tweaked versions of heavy.

[wgestickley]

Ahhh...

i can´t connect to pool... I only get a error Message...

Any help?

{"pool_use_tls" : false, "pool" : "gulf.moneroocean.stream:10128", "wallet" : "4Cf2TfMKhGhJ2vsM3HeBUnYe52tXrvv8X1ajjuQEMUQ8iU8kvUzCSsCEacxFhEmeb2JgPpQ5chdyw3U iTfUgapJBhCxqisgNo5PFSQ9MwW", "password" : "MINER1"},