What is there to mine with Rainforest?
Only thing I found is MBC, and it's not that profitable
Is there anything else?
Topic: WildRig Multi 0.35.1 beta 2 multi-algo miner for AMD & NVIDIA - page 39. (Read 92020 times)
MTP algo supported?
highly recommend miner
Vega on rainforest with last preview (4) 75-77Mhs - with latest (preview 5) 100-105Mhs
Weeee, profitable you say?
What hashrates are the usual suspects (Polaris, Vegas) getting on rainforest?
Right now I'm not 100% sure, network is increasing, and there is no calculator for it as I know %) About hashrate - up to 50MH/s per RX580 in stock, and 90MH/s per Vega64.What hashrates are the usual suspects (Polaris, Vegas) getting on rainforest?
Checked the numbers and ran the math myself... Nothing spectacular but hey... What is spectacular nowadays huh!
Weeee, profitable you say?
What hashrates are the usual suspects (Polaris, Vegas) getting on rainforest?
Right now I'm not 100% sure, network is increasing, and there is no calculator for it as I know %) About hashrate - up to 50MH/s per RX580 in stock, and 90MH/s per Vega64. What hashrates are the usual suspects (Polaris, Vegas) getting on rainforest?
cant wait for next release until nvidia miners will pump net HS on new rainforest algo
-.-
What hashrates are the usual suspects (Polaris, Vegas) getting on rainforest?
cant wait for next release until nvidia miners will pump net HS on new rainforest algo
-.-
Using RX 580's can't get this to work with the new wildrig.exe
wildrig.exe --algo rainforest --opencl-threads 2 --opencl-launch 18x0 -o --url=stratum+tcp://multi.extremehash.io:7443 --user=Mj71AhzQpNcKW4h2hTjWo4y6RtWhKFqGy8 -p c=MBC -R3
Do you see what I'm doing wrong?
Yes, -R3 in the end of bat-file wildrig.exe --algo rainforest --opencl-threads 2 --opencl-launch 18x0 -o --url=stratum+tcp://multi.extremehash.io:7443 --user=Mj71AhzQpNcKW4h2hTjWo4y6RtWhKFqGy8 -p c=MBC -R3
Do you see what I'm doing wrong?
If you want it as part of password, use -p "c=MBC -R3"ps: two threads is bad idea since preview 4. Use 1, also try auto for --opencl-launch, because now it should be higher for better hashrate
cant wait for next release until nvidia miners will pump net HS on new rainforest algo
-.-
Using RX 580's can't get this to work with the new wildrig.exe
wildrig.exe --algo rainforest --opencl-threads 2 --opencl-launch 18x0 -o --url=stratum+tcp://multi.extremehash.io:7443 --user=Mj71AhzQpNcKW4h2hTjWo4y6RtWhKFqGy8 -p c=MBC -R3
Do you see what I'm doing wrong?
wildrig.exe --algo rainforest --opencl-threads 2 --opencl-launch 18x0 -o --url=stratum+tcp://multi.extremehash.io:7443 --user=Mj71AhzQpNcKW4h2hTjWo4y6RtWhKFqGy8 -p c=MBC -R3
Do you see what I'm doing wrong?
cant wait for next release until nvidia miners will pump net HS on new rainforest algo
0.15.4 preview 3
- added rainforest algo(MicroBitcoin)
- extended information in console(there is a bug for Linux, network difficulty always zero)
- fixed Tonga support
Download
- added rainforest algo(MicroBitcoin)
- extended information in console(there is a bug for Linux, network difficulty always zero)
- fixed Tonga support
Download
i can use my ryzen apu rig,copy kernel-gfx900.bin kernel-gfx902.bin,then can use apu to rig.
i rig in version wildrig multi 0.15.2.2,but in version 0.15.3.8,it had no kernel-gfx900.bin and i can't rig in apu.can the next version support gfx902?
Ok, I can do that, but mining on APU... this is a bit weird i rig in version wildrig multi 0.15.2.2,but in version 0.15.3.8,it had no kernel-gfx900.bin and i can't rig in apu.can the next version support gfx902?
i can use my ryzen apu rig,copy kernel-gfx900.bin kernel-gfx902.bin,then can use apu to rig.
i rig in version wildrig multi 0.15.2.2,but in version 0.15.3.8,it had no kernel-gfx900.bin and i can't rig in apu.can the next version support gfx902?
i rig in version wildrig multi 0.15.2.2,but in version 0.15.3.8,it had no kernel-gfx900.bin and i can't rig in apu.can the next version support gfx902?
Thanks.
I've also noticed that the reported hashrate varies by quite a bit. Is this calculated based on actual results or something else? Here's an example:
Looks like you are mining x16 family algo, or similar(bitcore, timetravel and x21s). Each of these algorithms have hashorder thing. By simply saying, more green there - higher hashrate I've also noticed that the reported hashrate varies by quite a bit. Is this calculated based on actual results or something else? Here's an example:
To my understanding, variance is and should be happening only on x16r and x16rt since the used algos vary, for others just the order changes so it should be stable
Lets say it takes 10ms to calculate a slow algo and 1ms a fast one, so if you do slow first then the fast one, its 10 + 1 = 11ms
And if the order is reversed then its 1 + 10 = 11ms again... Just that you eventually do it with more algos.
x16r and x16rt the algos used are random (from a given set) so it varies, but for example x16s, its same algos but different order, so it remains stable
maybe I miss something, but this logic supports my own experience mining them
They random too. And, e.g. dedal, can even change amount of that hash functions in chain. Probably "hash order" bad term here, need to rename it somehow. Thanks.
I've also noticed that the reported hashrate varies by quite a bit. Is this calculated based on actual results or something else? Here's an example:
Looks like you are mining x16 family algo, or similar(bitcore, timetravel and x21s). Each of these algorithms have hashorder thing. By simply saying, more green there - higher hashrate I've also noticed that the reported hashrate varies by quite a bit. Is this calculated based on actual results or something else? Here's an example:
To my understanding, variance is and should be happening only on x16r and x16rt since the used algos vary, for others just the order changes so it should be stable
Lets say it takes 10ms to calculate a slow algo and 1ms a fast one, so if you do slow first then the fast one, its 10 + 1 = 11ms
And if the order is reversed then its 1 + 10 = 11ms again... Just that you eventually do it with more algos.
x16r and x16rt the algos used are random (from a given set) so it varies, but for example x16s, its same algos but different order, so it remains stable
maybe I miss something, but this logic supports my own experience mining them
Thanks.
I've also noticed that the reported hashrate varies by quite a bit. Is this calculated based on actual results or something else? Here's an example:
Looks like you are mining x16 family algo, or similar(bitcore, timetravel and x21s). Each of these algorithms have hashorder thing. By simply saying, more green there - higher hashrate I've also noticed that the reported hashrate varies by quite a bit. Is this calculated based on actual results or something else? Here's an example:
To my understanding, variance is and should be happening only on x16r and x16rt since the used algos vary, for others just the order changes so it should be stable
Thanks.
I've also noticed that the reported hashrate varies by quite a bit. Is this calculated based on actual results or something else? Here's an example:
Looks like you are mining x16 family algo, or similar(bitcore, timetravel and x21s). Each of these algorithms have hashorder thing. By simply saying, more green there - higher hashrate I've also noticed that the reported hashrate varies by quite a bit. Is this calculated based on actual results or something else? Here's an example:
To my understanding, variance is and should be happening only on x16r and x16rt since the used algos vary, for others just the order changes so it should be stable
Jump to: