[ANN] TeamRedMiner - Old Thread

[kerney666]

Any chance x22i algo will be added? Or is it possible to make it dual miner with ethash and lyra2z or some other combination?

Our roadmap is to go through all of the major algos first before we discuss venturing into any dual mining setup. X22i is not on our list at the moment though. We're currently working on CNv8, imho the results are looking very promising.

does it support failover pools?

No, I'm sorry to say we are lacking some very relevant features, pool strategies with multiple defined pools being one of them. As soon as CNv8 is out we should do a round on the host side code again and add better support.

[1714544264]

1714544264

[peteris-apse]

You have done amazing job! Nn nvidia front there are many good miners like zenemy, cryptodredge, t-rex. Theres not much on team red side - cryptonight and ethash algos only basically. With very few exceptions. I am happy that i could mine lyra2z and now phi2 with your miner on my amd rigs. Still with little, but profit.
Thank you!

After cnv8 whats next planned algo?

[Miner108]

Hello!
How to add backup pools?

[SigiSinatra]

I already gave "the best miner ever" title to teamredminer...no doubt about it.
It is great that you intend to implement cn v8 in the miner but I think that you should focus on some other algos unless you're sure that your v8 miner will provide significantly better hashrate. There are already a lot of great cn miners with a lot of builtin features (watchdogs,api,customscripts support,multi-cn algo switch fast/v8/heavy/haven etc.). It's your call of cores, but I think that you should focus on upcoming Zcoin hardfork new mining algo : https://zcoin.io/mtp-hard-fork-what-you-need-to-know/ and possibly to new upcoming Ethereum Prog-Pow.
It's so frustrating that nvidia miners always have mining software ready just on time and we with amd need to wait for several months after launch.

[kerney666]

Hello!
How to add backup pools?

Sorry to say, we're lagging in basic miner functionality, it's currently not possible . We've been prioritizing algo and kernel work, and we refuse to steal from some open source project to use as the basis for this miner, we write everything from scratch. Adding the API was the last big push on the host side. We'll make another push shortly though. Pool failover strategies will be added in some form.

[kerney666]

I already gave "the best miner ever" title to teamredminer...no doubt about it.
It is great that you intend to implement cn v8 in the miner but I think that you should focus on some other algos unless you're sure that your v8 miner will provide significantly better hashrate. There are already a lot of great cn miners with a lot of builtin features (watchdogs,api,customscripts support,multi-cn algo switch fast/v8/heavy/haven etc.). It's your call of cores, but I think that you should focus on upcoming Zcoin hardfork new mining algo : https://zcoin.io/mtp-hard-fork-what-you-need-to-know/ and possibly to new upcoming Ethereum Prog-Pow.
It's so frustrating that nvidia miners always have mining software ready just on time and we with amd need to wait for several months after launch.

We know our hashrates for CNv8 now, only miner work left. Imho it was time well spent, but we should be announcing shortly and everyone can decide for themselves. However, one of our main goals with this miner was to shoot down the stupid "truths" that some algos are for Nvidia only, and I can agree that working on CNv8 doesn't really fit that profile - it's rather already an AMD only algo .

Me and todxx will decide what to focus on next shortly, we have quite a few options. Adding all CN variants and the Heavy family is one thing. Going for Zcoin MTP or x16r is another, just to take a few examples. We might also branch out and do parallel work between us. ZCoin's MTP is a mess though, they have killed the normal stratum protocol for a pool/miner, it really is a shame. I wish they could have tweaked a few design decisions and mining would continue to work as usual, but no. Miners now need to send large proofs (> 150kb or something) for every share to the pool. We did provide our point-of-view to the Zcoin team, but to little avail.

[joseph32]

X16r would be a great next algo, but only worth if AMD can compete with nVidia hashrate.

[alucard20724]

was version 0.3.3 re-released?... github says it was released 2 days ago, however, i got it from github nine days ago.

[pbfarmer]

Anyone able to get the api to respond in 0.3.3?  Doesn't work for me...

[Grumo]

Team Red Miner version 0.3.3
[2018-10-27 17:33:43] Failed to initialize device number 0.


with 2 vega 56 under windows, latest drivers

[kerney666]

was version 0.3.3 re-released?... github says it was released 2 days ago, however, i got it from github nine days ago.

There was an issue with the Linux tarball, the gzip compression wasn’t applied so people got “corrupt file” errors when trying to extract. It was fixed two days ago, hence the new timestamp.

[kerney666]

Anyone able to get the api to respond in 0.3.3?  Doesn't work for me...

Confirmed working with Awesome Miner and MinerStats. What is your command line, and do you connect from the same computer or some other machine on the network?

[kerney666]

Team Red Miner version 0.3.3
[2018-10-27 17:33:43] Failed to initialize device number 0.


with 2 vega 56 under windows, latest drivers

Hi!

I would guess that you have two OpenCL platforms (zero and one). Unless specified on the command line, the miner checks for devices on platform zero. Please try adding "--platform=1" to your command line together with the rest of the parameters.

[5BTC]

Any idea when you expect the CNv8 release?

Have you tested it on Linux with multiple Vegas?

[todxx]

Any idea when you expect the CNv8 release?

Have you tested it on Linux with multiple Vegas?

We're hoping to get CNv8 out in the next couple days.

We have not yet tested it on a linux system running multiple vegas, but we have tested it on a linux system with 7 x 470s and everything ran fine.
I would expect the same for a system with multiple Vegas.
Do note that CNv8 will require amdgpu-pro drivers version 18.30 or newer on linux for both Polaris and Vega cards.  We do not initially plan to support CNv8 on ROCm.

[todxx]

New release v0.3.4 posted!

This version now includes cryptonight v8 support!
Also better reporting of GPU hashrates and reporting of submitted/accepted/rejected shares.
Please note that we have changed how we report GPU hashrates.  Hashrates reported by the miner are now the full GPU hashrates.  Previously hashrates reported were after dev fee deduction.

Since we expect a lot of questions and comments about cryptonight v8, we have created a new thread for it here.
Please post any cryptonight v8 related comments and questions in that thread.

[9ville]

Device number * is out of range.
What's the problem?

[N2DCRYPT]

Device number * is out of range.
What's the problem?

Try adding --platform=1 to your bat file.

[alucard20724]

New release v0.3.4 posted!

This version now includes cryptonight v8 support!
Also better reporting of GPU hashrates and reporting of submitted/accepted/rejected shares.
Please note that we have changed how we report GPU hashrates.  Hashrates reported by the miner are now the full GPU hashrates.  Previously hashrates reported were after dev fee deduction.

Since we expect a lot of questions and comments about cryptonight v8, we have created a new thread for it here.
Please post any cryptonight v8 related comments and questions in that thread.

are there parameters to be added to phi2?  cause it would appear that 0.3.4 has killed the hashrate for phi2

[kerney666]

New release v0.3.4 posted!

This version now includes cryptonight v8 support!
Also better reporting of GPU hashrates and reporting of submitted/accepted/rejected shares.
Please note that we have changed how we report GPU hashrates.  Hashrates reported by the miner are now the full GPU hashrates.  Previously hashrates reported were after dev fee deduction.

Since we expect a lot of questions and comments about cryptonight v8, we have created a new thread for it here.
Please post any cryptonight v8 related comments and questions in that thread.

are there parameters to be added to phi2?  cause it would appear that 0.3.4 has killed the hashrate for phi2

That is surprising really, we haven't touched those kernels at all, should be exactly the same. On my Windows box, running the v0.3.2 vs 0.3.4 for a few mins with a 580+560+Vega 64, I get the following:

v0.3.2

[2018-10-30 13:10:12] Stats GPU 0 - phi2: 4.919Mh/s (4.320Mh/s)
[2018-10-30 13:10:12] Stats GPU 1 - phi2: 2.034Mh/s (1.834Mh/s)
[2018-10-30 13:10:12] Stats GPU 2 - phi2: 9.880Mh/s (8.948Mh/s)
[2018-10-30 13:10:12] Stats Total - phi2: 16.832Mh/s (15.103Mh/s)


vs

v0.3.4

[2018-10-30 13:05:52] Stats GPU 0 - phi2: 5.076Mh/s, avg 5.073Mh/s, pool 5.089Mh/s 27/0
[2018-10-30 13:05:52] Stats GPU 1 - phi2: 2.087Mh/s, avg 2.114Mh/s, pool 1.926Mh/s 8/0
[2018-10-30 13:05:52] Stats GPU 2 - phi2: 10.18Mh/s, avg 10.18Mh/s, pool 12.08Mh/s 55/0
[2018-10-30 13:05:52] Stats Total - phi2: 17.34Mh/s, avg 17.36Mh/s, pool 19.10Mh/s


In v0.3.2 we displayed the net user hashrate (3% dev fee subtracted), this has changed in 0.3.4, we now display the raw hashrate. Adjusting for that change: 17.36 * 0.97 = 16.84, close enough to 16.832. So, I don't see a regression bug on my Windows box at least.

Can you give a quick description of your setup (os/driver/gpus) and what you're seeing?

Cheers, K