Bitcoin Forum
April 27, 2024, 04:28:41 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 [410] 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 ... 499 »
  Print  
Author Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)  (Read 784624 times)
Deafran
Jr. Member
*
Offline Offline

Activity: 49
Merit: 4


View Profile
March 12, 2021, 01:34:32 AM
 #8181

Hello,

Running PhoenixMiner / Windows 10 with 12 Nvidia Cards is running fine, but when adding the 13th Card, I got an "Out of Memory" Error. Adding extra RAM or enlarging Swap File doesn't help. Using different RTX and GTX Card, always the same.

Is this a hard limit, or is there a way to work around this?

Thanks for help!


red panda mining

19 card  

https://www.youtube.com/watch?v=N_9-3zVsgDg
1714192121
Hero Member
*
Offline Offline

Posts: 1714192121

View Profile Personal Message (Offline)

Ignore
1714192121
Reply with quote  #2

1714192121
Report to moderator
"Your bitcoin is secured in a way that is physically impossible for others to access, no matter for what reason, no matter how good the excuse, no matter a majority of miners, no matter what." -- Greg Maxwell
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714192121
Hero Member
*
Offline Offline

Posts: 1714192121

View Profile Personal Message (Offline)

Ignore
1714192121
Reply with quote  #2

1714192121
Report to moderator
1714192121
Hero Member
*
Offline Offline

Posts: 1714192121

View Profile Personal Message (Offline)

Ignore
1714192121
Reply with quote  #2

1714192121
Report to moderator
PhoenixMiner (OP)
Full Member
***
Offline Offline

Activity: 357
Merit: 101


View Profile
March 12, 2021, 03:53:23 AM
Last edit: March 12, 2021, 04:17:58 AM by PhoenixMiner
Merited by miner29 (5)
 #8182

I'm currently mining with PhoenixMiner using NiceHash (I would stop using NH if I felt I could make batch file correctly!) as it is by far the best miner I've used due to how stable it is, the level of info displayed and the amount command line of switches.

I'm only using my laptop (yes well aware of the risks and I know I'm not going to make a fortune) with its GTX 1660 Ti (temps around 65-67 with good airflow) and I use the following extra launch parameters:

-lidag 3 -mcdag 1 -mi 14 -nvdo 1 -eres 3 -cclock -305 -mclock +575

My questions are am I using them correctly? Are there some where the value could be changed? Do I need all of the ones I'm currently using?

Thanks in advance!
  The parameters are fine but you may try using -powlim to lower the core clock instead of using -cclock. On most Nvidia cards -cclock will not lower the voltages sufficiently (or at all), and the GPU will consume more power than needed. Start with -powlim -10 (this will decrease the power limit by 10%), then try decreasing the power limit further (e.g. -powlim -20) until the hashrate starts to be affected.



I don't blame you for wanting to keep your identity a secret, and good job standing your ground.  I wouldn't have reacted to Nicehash's message any differently.  

However, there were a few days this past week where your clients were scrambling trying to find your software, and since this thread is under constant attack by malware shilling sockpuppets, this episode put your clients in a high-risk situation.  Many didn't know whether the software they found was the right version, and there was also suspicion that your Mega and Bitcointalk.org accounts were hacked, or (god forbid,) you went rogue yourself.

Checksums are great, but they don't guarantee that your accounts haven't been hacked, or the software and checksums weren't replaced by the hacker.  To help the members of this forum (and the folks at Github will appreciate it also) I suggest you create and stake a PGP key that you use to sign the binaries and/or the checksums.  That gives the community a second factor for authentication.  If this kind of thing happens in the future we can use the PGP to authenticate your checksums or the binaries and avoid this kind of drama.
  This is not a bad idea, and we will definitely look into it. Our main concern is with github - if somebody starts complaining to them like they did to MEGA, they may close our account there too. We already prepared a few backup hosts but won't make them public until they are needed (hopefully not soon).




Well for me I am and have been using most versions of Phoenix miner with no issues. I am currently using Phoenix 5.5c within the Nicehash miner for about the last month. Only to switch things up for a BTC payout. Otherwise I normally have used the Phoenix miner as a stand alone.

I am glad to see the Phoenix devs coming forward to defend themselves and go to lengths to give reassurance on their software and that they are not "MIA"

Lets hope both Nicehash and Phoenix can find a middle ground and get this resolved soon for the benefit of everyone who uses both software's. Its not healthy for the mining world to have doubts on either side.

MMNC Smiley
  We certainly don't want any "wars" with NH, or anybody else. If they were just telling their clients to avoid third-party miners (and they are doing this for months) without spreading any FUD, well, we may not like it but we would accept it without any complains. But apparently that wasn't enough to move people to their miner, so they had to start smearing us.




Hi, hoping for some help with 1 of my 3090's I use for mining. Using v5.5c.
The problem I'm having is as soon as it hits around 60c temp, the performance drastically goes down. For some reason the card stops pulling the usual ~350 watts and only draws ~270 watts after 60c ish temperature is hit. I have a 2nd 3090 which pulls much higher, has no monitors plugged into it and draws around 400 watts. That card will happily go up to 66-67c temps and remains at the 400 watts draw. I'm really scratching my head with the first 3090. It hurts watching it's hshrate go from 120mh to 90mh just because the temp climbs from 56c to 60c lol. Meanwhile the 2nd card doesn't seem to care about temperature and will chug away doing 122mh with 400 watts.
If you need any extra information such as logs, OC settings etc then please let me know and I can provide them.

  Yes, a log will be helpful, but first make sure you add the command-line option -hstats 2 to see the actual clocks, and the reason for throttling (we assume that there is throttling involved), and because 60C is too low for temperature-related throttling, it is probably power-related but we need the log for more information.

  If the card is throttling because of the power limit, you can increase it with this option -powlim +20,0 (the 0 is to leave the power limit of the second card at default value as it doesn't have throttling issues).

Hi Phoenix, thanks for the response. I've added in the command line options you suggested and ran the miner for a couple minutes. Sadly the -powlim argument didn't really help. I wasn't sure what the most convenient way of sharing the log would be so I just went ahead and threw it in a pastebin. You can see that here: https://pastebin.com/q780sgsL

The exact cards are EVGA 3090 FTW Ultra's and I'm using EVGA's Precision X1 overclocking software. The OC settings I'm running are the same for each card and they are as follows.
GPU: -400
Mem: +1200
Power and Temp target slider is maxed at 119% for power and 91c for temp. The fans are also all set to 100%.
   The log also shows that the performance cap (throttling) reason for the first GPU is the temperature:

Code:
GPU1: cclock 990 MHz, cvddc 743 mV, mclock 10702 MHz, p-state P2, pcap temp

    The others called it correctly - the memory is overheating.



... and when we release the actual new version, it will not be named 5.5d[/b].


Hello. Thanks for the releases.
Will you add more DAG epohs in the next release?
  We will but even the current limit (epoch 500) should be enough for at least 14-15 more months.



Hello. Thanks for the releases.
Will you add more DAG epohs in the next release?
I agree. Current epoch # 400, there are less than 100 left because I think that it will stop working much earlier than 500.

I saw some other ethash miners add more DAGs...
  No, 5.5c will work without any problems until epoch 500 (provided that you have enough VRAM). But it is not a big deal to increase limit, and we will do so for the next release.




You could opt for a middle ground, producing your own private key and signing all subsequent PhoenixMiner releases with it, without registering with an official CA to sign that key. You could then post your public key here in the thread's first post, so any future binaries can be verified against it.
  Yes, it seems that a lot of people will be OK with this, so we will probably do it soon. We will also put the public key in another big "verifying" transaction to prove we are behind it.




Dear Phoenix Miner Dev,

With the impending end of life for ethereum mining in the near future any plans to add Ravencoin to the mix since other progpow crypto is already on the list?
 Yes, but not in the next release - it is already feature-frozen. But definitely in a few months at most.





Phoenix still needs our support because today some of my friends asked if they could use this program.
NiceHash blamed the developer for a lot and still hasn't apologized. But they did not forget to post QuickMiner on Twitter today.
At this rate, Phoenix will become an underpopular miner.
  Thank for you support. Do not worry too much about that - people will "vote" with their rigs. If their miner is so good, they wouldn't resort to such dirty tactics, and we believe that whole thing will blow over soon enough.
WARMANGALAXY
Jr. Member
*
Offline Offline

Activity: 69
Merit: 1


View Profile
March 12, 2021, 04:23:15 AM
 #8183

пpивeт, Фeникcы, кoгдa нoвыe peлизы?
WARMANGALAXY
Jr. Member
*
Offline Offline

Activity: 69
Merit: 1


View Profile
March 12, 2021, 04:26:35 AM
 #8184

Phoenix, I want to tell you that on Nvidia in the RaveOS and mmpOS system, a kernel fix for Nvidia video cards was released. It was also possible to change the PState from 2 to 0. It is in Linux. This innovation increases the stability of the graphics cards, does not allow the core to jump up and down, reduces power consumption and increases the hashrate. This update greatly stabilizes the performance of all NVIDIA graphics cards on GDDR6
Littlegrand
Jr. Member
*
Offline Offline

Activity: 104
Merit: 5


View Profile
March 12, 2021, 11:34:21 AM
 #8185

I have a rx 5700 xt MSI Mech on Windows 10.  

I run it with rx580s. It works fine at 57mh/s but will randomly cut back to 47mh/s(sometimes after 2 days, sometimes after 2 hours. I tried lowering the clock/mem even down to 52mh/s but this still happens randomly and I have to reboot in order to fix it.

Any ideas whats wrong or how to diagnose it?

Thanks
th00ber
Hero Member
*****
Offline Offline

Activity: 789
Merit: 501


View Profile
March 12, 2021, 12:18:18 PM
 #8186

Hi, hoping for some help with 1 of my 3090's I use for mining. Using v5.5c.
The problem I'm having is as soon as it hits around 60c temp, the performance drastically goes down. For some reason the card stops pulling the usual ~350 watts and only draws ~270 watts after 60c ish temperature is hit. I have a 2nd 3090 which pulls much higher, has no monitors plugged into it and draws around 400 watts. That card will happily go up to 66-67c temps and remains at the 400 watts draw. I'm really scratching my head with the first 3090. It hurts watching it's hshrate go from 120mh to 90mh just because the temp climbs from 56c to 60c lol. Meanwhile the 2nd card doesn't seem to care about temperature and will chug away doing 122mh with 400 watts.
If you need any extra information such as logs, OC settings etc then please let me know and I can provide them.
Known issue of the 3080/3090
The GPU is cool, but the mem temp is too hign.
Add backplate fans to cool the mem and it will be ok
And if you don't care about losing waranty, you can also change/add thermal pads
miniero
Jr. Member
*
Offline Offline

Activity: 58
Merit: 4


View Profile
March 12, 2021, 02:24:14 PM
 #8187

Hello,

Running PhoenixMiner / Windows 10 with 12 Nvidia Cards is running fine, but when adding the 13th Card, I got an "Out of Memory" Error. Adding extra RAM or enlarging Swap File doesn't help. Using different RTX and GTX Card, always the same.

Is this a hard limit, or is there a way to work around this?

Thanks for help!


red panda mining

19 card  

https://www.youtube.com/watch?v=N_9-3zVsgDg

Thank you! Do you know something about the setup and the settings of that monster?
pabapt
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
March 12, 2021, 03:39:48 PM
 #8188

Hi, hoping for some help with 1 of my 3090's I use for mining. Using v5.5c.
The problem I'm having is as soon as it hits around 60c temp, the performance drastically goes down. For some reason the card stops pulling the usual ~350 watts and only draws ~270 watts after 60c ish temperature is hit. I have a 2nd 3090 which pulls much higher, has no monitors plugged into it and draws around 400 watts. That card will happily go up to 66-67c temps and remains at the 400 watts draw. I'm really scratching my head with the first 3090. It hurts watching it's hshrate go from 120mh to 90mh just because the temp climbs from 56c to 60c lol. Meanwhile the 2nd card doesn't seem to care about temperature and will chug away doing 122mh with 400 watts.
If you need any extra information such as logs, OC settings etc then please let me know and I can provide them.

  Yes, a log will be helpful, but first make sure you add the command-line option -hstats 2 to see the actual clocks, and the reason for throttling (we assume that there is throttling involved), and because 60C is too low for temperature-related throttling, it is probably power-related but we need the log for more information.

  If the card is throttling because of the power limit, you can increase it with this option -powlim +20,0 (the 0 is to leave the power limit of the second card at default value as it doesn't have throttling issues).

Hi Phoenix, thanks for the response. I've added in the command line options you suggested and ran the miner for a couple minutes. Sadly the -powlim argument didn't really help. I wasn't sure what the most convenient way of sharing the log would be so I just went ahead and threw it in a pastebin. You can see that here: https://pastebin.com/q780sgsL

The exact cards are EVGA 3090 FTW Ultra's and I'm using EVGA's Precision X1 overclocking software. The OC settings I'm running are the same for each card and they are as follows.
GPU: -400
Mem: +1200
Power and Temp target slider is maxed at 119% for power and 91c for temp. The fans are also all set to 100%.

The problem with most 3090s is the memory junctions temp, I solved that locking the clock to 1200mhz on afterburner, maxing fan1 to 100% and fan2 min 70% while I wait for thermal pads to repad the card.  All this with +1300 Mem.
epic-math
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
March 12, 2021, 03:51:43 PM
Last edit: March 12, 2021, 11:42:07 PM by epic-math
 #8189

I'm receiving the following error but I can't find much information about it:

Using AMD RX gpus

GPU[X]: unable to init straps

Any help would be greatly appreciated!

***EDIT: Fixed, it was a driver issue.
Kiawpqe
Jr. Member
*
Offline Offline

Activity: 63
Merit: 1


View Profile
March 12, 2021, 05:58:33 PM
 #8190

I'm receiving the following error but I can't find much information about it:

Using AMD RX gpus

GPU[X]: unable to init straps

Any help would be greatly appreciated!

Hi there
does not give enough information.
Amd RX Huh?
If it is RX 580:
CHECK IF YOU RUN PM AS ADMINISTRATOR.
If it is RX 6800:
THIS GPU DOES NOT ACCEPT STRAPS in PM YET.
more info to help
natewin
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
March 12, 2021, 08:00:33 PM
 #8191

@PhoenixMiner

Any plans for monitoring and allowing fan control based on memory temperature?

Aside from the weirdness going on lately, Nicehash Quickminer does have some really nice new features.  Itcan set fan speed based on monitoring of 'Hot Spot' memory temp in DDR6 cards and Memory TJ on 3080/90 cards.
djeZo
Hero Member
*****
Offline Offline

Activity: 588
Merit: 520


View Profile
March 12, 2021, 11:37:12 PM
 #8192

I hope this post does not get deleted, because my posts were getting deleted.

I am making this post on my behalf, has nothing to do with NiceHash and NiceHash is not aware of it. This is my personal view and NOT a statement from NiceHash.

Let's start with timeline several months ago, before the big BTC hype, when BTC was still just around 10k. Who was mining back then? Old school miners. People that know how to mine, people that use dedicated rigs, are well aware NOT to store any personal data on these PCs. Keep private keys away. Minerstat for example, is actually well aware of this, and they made a suggestion
Quote
Don't mine on personal computer. We do know what minerstat application includes, but we can never know what is in the mining clients as they are closed source.
source: https://minerstat.com/help/how-to-secure-your-mining-environment

So, generally, it is well known that it is simply too risky to just mine on your own PC. You need to have a dedicated rig for that, if you wish to mine.

What happened then? BTC started rising and with it all other altcoins and ethereum. NiceHash made some campaigns and there will be more - to get general population (especially gamers into mining). Let's put out this fact: these people DO NOT have dedicated rigs for mining, they DO MINE on their personal computers. The thing that everyone here knows is very risky to do.

But everything is fine, when each person decides for himself. If you are prepared to take the risks and you do install close source miners from anonymous developers, that is on you and nobody else. Nobody can be blamed for your choice, right?

Now, this things becomes way more complicated, if there is someone else who installs this on your PC - like NiceHash. And if you didn't notice the total ignorance by the majority of people towards this problem, to the point of even making jokes of "stealing my porn collection". These things are not something you make fun of. These things can destroy a company and put people behind bars. Yes, NiceHash is aware of this problem, was aware of this BEFORE phoenix saga happened, that is why there were certain threads opened and posts made. There were plans to inform public better about this issue. NiceHash started solving this issue from two perspectives: first was to inform the public and second was to create alternative that would at least come close to the closed source solutions made by anonymous developers.

Until last weekend, everything was calm. Then NiceHash started getting reports about PhoenixMiner Mega.nz download issue. Okay, it can happen, developer would surely fix the issue and upload new bins, inform us about new link. But nothing. We decided to write to developer - no response. After no response, we started getting worried. Is that an exit scam? Did we just distribute malicious software from anonymous developer and will be held responsible for installing malware on 300k computers worldwide? This was the main question in the company. How would ANY reasonable person react to this speculation? Keep it quiet and hope that this is not true? Well... hope is not enough, hope doesn't absolve you from responsibility. Yes, NiceHash do have 3rd party EULA that every user has to confirm, but like I mentioned before, nobody was reading that. People gave jack shit about it and really didn't care. They were under complete illusion that "NiceHash is a big company, they surely must have taken care of what I am installing, no?". Perhaps if this happened and there was a court case, NiceHash could win, but that doesn't mean NiceHash would survive.

And when we took a deeper look - developer gone for 1.5 months, constant attempts to push 5.5d bins, someone was doing hash checks and said these don't match (not sure why that was but as later found out - probably because of different zip files), it was just a big panic and a race with a time - if there is a malicious attempt, we need to inform users ASAP and reduce possible damage. Considering how long developer did not react (it must have been like 3 days), we were sure he/she/they are not coming back and the only question remaining was: is there an exit scam or not? Why did we think so? The reasons cannot be simply explained with one sentence, but I have made explanation available here: https://www.reddit.com/r/NiceHash/comments/lzsheq/phoenixminer_howwhywhat_statement_from_it_expert/

But on Monday morning, look, developer is back! I was sure, we need to make an apology now. Even though, we never said that there is malware, we only warned users there COULD be, people panicked and simply overlooked our "COULD" word. So, my belief was to make a sorry statement at least for this indirect damage. And if you ask me, I am still sorry for this. I know what it means, if developer intentions are not harmful, and until there is name to be kept, I am sure, intentions are not harmful. I know how much damage from reduced income this must have caused. But I cannot decide for the company what statements to give out. This is not in my power and voting was against doing this. If it helps you PhoenixMiner, personally, I am sorry for this, truly I am.

Now, let's also debate the other very suspicious events that were going on before developer reappeared and which do not make much sense and were completely unnecessary and must have been related to something else, which made the whole disappearance even more suspicious. I believe, if there were none of these activities, things would probably go into different direction, perhaps even towards official sorry statement.

So, after the announcement was made, there was immediate FUD by Josip Juhas, that NiceHash has pushed malicious 5.5d binaries to all NiceHash users and that this is just a campaign to fix own mistake. I have asked Josip to take this statement down, because it was not true. It was not true according to the source code, which is publicly available and everyone can analyze and confirm that this could not have happened unless the real developer pushed these bins on Mega.nz. Also, not a single user reported getting 5.5d bins and nobody reported anything about being infected. But Josip Juhas continued pushing this FUD to the point so others have copied his statement, including Alchemy from RedPandaMining and this statement was then spread by RedPandaMining all around the community through his YouTube channel. Besides that, someone (definitely not developer) also started massive shill campaign on all social media posting either this exact same FUD about 5.5d binaries being pushed or diversion - some events from NiceHash's history to discredit NiceHash warning as false and as something you really don't have to worry about. I cannot prove who was behind this campaign, but if developer wasn't available, then I would guess it was definitely NOT the developer. And the developer would be the only one having interest doing that. So who else would be doing that? I still don't know, but if I'd have to point my finger I'd say Josip Juhas. It fits his profile. Why?

Let me tell you something about Josip Juhas, aka minerstat owner. Josip Juhas was convicted two times in Slovenia and spend some time in prison. First time, he was convicted for planned murder. With some other people, they had a plan to hire a young woman, insure her for large sum of money (2.5mil EUR) and then murder her to get this money. So, basically, to make insurance fraud. He got 1 year of prison for this (because it was never executed and was only planned). Second time, he was convicted for extorting women. There were 3 guys, one had sex with women and they taped acts. After the act, there was extortion for money so they would keep quiet and not tell their husbands. At least 3 women were the victims. Not much was revealed publicly, because identity of victims was hidden. He got around 3 years of prison for this crime. Sources (unfortunately in Slovenian, but you can use google translate):
https://www.vecer.com/kronika/do-grla-vpleten-v-dogovor-o-umoru-bo-terjal-odskodnino-zaradi-pripora-10075458
https://old.slovenskenovice.si/crni-scenarij/doma/za-nacrtovani-umor-sta-dobila-po-10-let
https://old.delo.si/novice/kronika/kljucno-prico-cakajo-na-sodiscu-in-v-zaporu.html
There are a lot more sources available, I just listed few. How do I know this? Josip Juhas once worked for NiceHash. He resigned somewhere in the middle of 2017. He wasn't fired, he resigned, let me make this very clear. Also, he is well aware of dangers of mining on personal computer - he has this text I quoted before on minerstat webpage. So, why would he do what he did then you may ask yourself? Deep inside, he must know the dangers, deep inside he knew that NiceHash distributed PhoenixMiner on many PCs around and deep inside he knew that this could be the end of NiceHash if it turns out to be true - that there is an exit scam. But if NiceHash makes a big warning, and it turns out to be true, then NiceHash would survive, because people were warned and they could have reacted fast enough to prevent damage. Do you see reasoning now? Josip Juhas wish that NiceHash would die since 2017 when he resigned. He created kinda competitive service - minerstat, so of course, he wants NiceHash gone, obliterated. And by spreading malware, that would be the perfect way. So, making any warnings, that is actually bad - he doesn't want NiceHash to make warnings, he wants NiceHash to make mistakes, so he could take over with minerstat. You can go search his history of comments here and you will notice that he was constantly bad mouthing NiceHash for no apparent reason. I have contacted Josip Juhas at the end of 2020, was expecting to get bad mouthed but was surprised that he was being very polite. Now I see, it was all only the act. His plan was to sell minerstat to NiceHash for 5 million EUR. Of course NiceHash turned that down. There was no reason for him to talk to NiceHash anymore after that. He was so convinced that he was building "something" for NiceHash for the past 3 years, but when we told him that we don't need his service, he was very disappointed. And this is what you get if you don't pay... Basically, if he had a sex tape, it wouldn't be a question "can you please buy this for 5mil?" but rather statement "give me 5mil or I release this sex tape to the public!".

So, be very careful when you deal with him. Never make any business with him. Better not even talk to him. And I am sure he will come up with some bullshit about me being the owner and that nobody likes me and that I am alone and that people are leaving NiceHash. NiceHash has about 50 people and is growing, getting more people every month. What he talks "supposedly about me" is actually his own personality. Josip Juhas has only his girlfriend and one guy from 2017. That is whole minerstat. Only brainwashed people can work with/for him. Sooner or later, anyone realizes that it is impossible to do business with him or impossible to work with/for him.

So, what will happen now in the future? NiceHash Miner will introduce some way of putting PhoenixMiner back in, it just isn't going to be automatic download by NiceHash. That is just way too risky. When people manually insert miners in, then NiceHash cannot be responsible for anything malicious if it ever happened. Similar destiny awaits all other anonymous miners. We don't hate PhoenixMiner and we did not want to destroy PhoenixMiner. This is just malicious talk. There was a risky situation and we had to take extraordinary action to protect NiceHash.

And regarding Josip Juhas. Well, we can just hope that he doesn't murder us all... because after all... he could be capable doing that. I know he will be fighting hard and try to delete this post I made. He was able to reach with mods somehow to delete my other posts. Let's see if he get's so lucky this time too. If he does, then mod, whoever is deleting this post, perhaps you should think twice - isn't this bitcointalk, a forum where free speech is guaranteed?

vig3
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
March 13, 2021, 02:16:36 AM
 #8193

Is it me or has Mega always been a bit sketch?
dazmann
Jr. Member
*
Offline Offline

Activity: 45
Merit: 6


View Profile
March 13, 2021, 02:17:42 AM
 #8194

Djezo,
Your posts were being deleted because you were telling people to commit suicide. I myself reported your post, I would consider that a nice reason for a ban but hey this is bitcointalk, free speech amirite?

You should read more contemporary books or watch more tv shows because your level of articulation is very low. You hide your non-apology through a wall of text, deflecting everything you did wrong while making terribly placed branding calling up Nicehash time and time again. Moving the goal post is the weakest form of non-argument after ad hominem. I suggest you take the L, apologize and move on. Be humble. You may be an IT specialist but you're terrible at marketing and reading the room.
PhoenixMiner (OP)
Full Member
***
Offline Offline

Activity: 357
Merit: 101


View Profile
March 13, 2021, 07:43:50 AM
Last edit: March 13, 2021, 08:36:35 AM by PhoenixMiner
 #8195

I hope this post does not get deleted, because my posts were getting deleted.
Not by us, we can't delete any posts here, and if your posts got deleted on bitcointalk.org, you are probably in the wrong. Also, complaining about deleted posts is a bit rich, after your company locked up the thread started by us on your subreddit.


I am making this post on my behalf, has nothing to do with NiceHash and NiceHash is not aware of it. This is my personal view and NOT a statement from NiceHash.
So what exactly is your position in NiceHash? Owner, CEO, just another employee? Did you had any part in taking these decisions? You can't have it both ways - talking like you own (or at least run) NiceHash, then go back to just sharing your "personal view".


Let's start with timeline several months ago, before the big BTC hype, when BTC was still just around 10k. Who was mining back then? Old school miners...
Fortunately (at least from our perspective), the vast majority of miners are still old school.


Yes, NiceHash do have 3rd party EULA that every user has to confirm, but like I mentioned before, nobody was reading that. People gave jack shit about it and really didn't care. They were under complete illusion that "NiceHash is a big company, they surely must have taken care of what I am installing, no?". Perhaps if this happened and there was a court case, NiceHash could win, but that doesn't mean NiceHash would survive.
Let's just stop with all this nonsense about "corporate responsibility". The most important reason to create a corporation, is to limit the responsibility of the owner(s)! But even if we accept that you were genuinely concerned for your users, where is the huge post on your site, warning users about the latest Windows vulnerability for example? Where is the post saying "format your disks, install the latest revision of Windows 10 immediately by downloading it directly from Microsoft, and change all your passwords because of XYZ"?


And when we took a deeper look - developer gone for 1.5 months, constant attempts to push 5.5d bins, someone was doing hash checks and said these don't match (not sure why that was but as later found out - probably because of different zip files), it was just a big panic and a race with a time - if there is a malicious attempt, we need to inform users ASAP and reduce possible damage.
Posts with fake versions of PhoenixMiner have appeared on this thread for years! All of them were promptly removed by the moderators. What changed on March 6th (besides MEGA deleting our account)? And the story about the checksums is pure BS. Of course the checksums of the fake 5.5d won't match with these that are posted by us here - that is the whole point of the checksums!


Considering how long developer did not react (it must have been like 3 days), we were sure he/she/they are not coming back and the only question remaining was: is there an exit scam or not?
Yes, we are guilty of not reacting in time. The only thing that we can say in our defense, is that none of us really subscribes to, or participates in the modern way of living our lives "online" all the time. We check our devfee hashrate for any indication of anything wrong happening multiple times a day but otherwise, we keep our work and our lives mostly offline except around the releases of the PhoenixMiner. Perhaps we were too complacent, and we have taken steps to make sure we react much faster should anything like this happens in the future.


But on Monday morning, look, developer is back! I was sure, we need to make an apology now. Even though, we never said that there is malware, we only warned users there COULD be, people panicked and simply overlooked our "COULD" word. So, my belief was to make a sorry statement at least for this indirect damage. And if you ask me, I am still sorry for this. I know what it means, if developer intentions are not harmful, and until there is name to be kept, I am sure, intentions are not harmful. I know how much damage from reduced income this must have caused. But I cannot decide for the company what statements to give out. This is not in my power and voting was against doing this. If it helps you PhoenixMiner, personally, I am sorry for this, truly I am.
A five-year-old would come up with a better apology. "I'm sorry, but it wasn't my fault anyway."


Now, let's also debate the other very suspicious events that were going on before developer reappeared and which do not make much sense and were completely unnecessary and must have been related to something else, which made the whole disappearance even more suspicious. I believe, if there were none of these activities, things would probably go into different direction, perhaps even towards official sorry statement.

So, after the announcement was made, there was immediate FUD by Josip Juhas, that NiceHash has pushed malicious 5.5d binaries to all NiceHash users and that this is just a campaign to fix own mistake. I have asked Josip to take this statement down, because it was not true. It was not true according to the source code, which is publicly available and everyone can analyze and confirm that this could not have happened unless the real developer pushed these bins on Mega.nz. Also, not a single user reported getting 5.5d bins and nobody reported anything about being infected. But Josip Juhas continued pushing this FUD to the point so others have copied his statement, including Alchemy from RedPandaMining and this statement was then spread by RedPandaMining all around the community through his YouTube channel. Besides that, someone (definitely not developer) also started massive shill campaign on all social media posting either this exact same FUD about 5.5d binaries being pushed or diversion - some events from NiceHash's history to discredit NiceHash warning as false and as something you really don't have to worry about. I cannot prove who was behind this campaign, but if developer wasn't available, then I would guess it was definitely NOT the developer. And the developer would be the only one having interest doing that. So who else would be doing that? I still don't know, but if I'd have to point my finger I'd say Josip Juhas. It fits his profile. Why?

OK, let unpack this. You obviously have a beef with this person, and you may very well have good reasons for this. So, let's set the record straight: we don't have any business with him, the only association is that we added link to minerstat in our main post after he asked us nicely in a PM - the same as with the other few links in our first post. None of them paid us with fiat, crypto, or in any other way, all they did was to tell us "Hey, we are featuring your miner on our site/service/whatever since forever, would you add a small link to us?". After a quick check of the website or service in question, we did add a link. We can't do detailed background check or ask them for they real identities, nor do we want to. We never received any complains about these services being untrustworthy, or malicious.

With that being said, why can't you admit that you have created this shitstorm yourself? The hysterical blog post of your site was indicative of something much more serious than "the developer of PhoenixMiner disappeared, and his MEGA account was deleted". Given your past security record, a lot of people probably thought that there must be something that you are not telling them, like mistakenly pushing the fake version of PhoenixMiner on their PCs, and then trying to absolve yourself of any responsibility.

So, you have to either admit your employees are grossly incompetent, or that you had created this FUD campaign for other reasons. We don't think your employees are that incompetent.


Let me tell you something about Josip Juhas, aka minerstat owner. Josip Juhas was convicted two times in Slovenia and spend some time in prison.
...
How do I know this? Josip Juhas once worked for NiceHash. He resigned somewhere in the middle of 2017. He wasn't fired, he resigned, let me make this very clear.
  Let us get this straight. You knew about his criminal past, yet you hired him? Well, this sure seems to be a recurring theme in NiceHash! In contrast, none of the people on our team were ever convicted, or even accused of any criminal activity. It's probably part of the reason why we can't find common ground - your environment and values are quite different than ours.


So, be very careful when you deal with him. Never make any business with him. Better not even talk to him.
...
And regarding Josip Juhas. Well, we can just hope that he doesn't murder us all... because after all... he could be capable doing that.
 Don't worry, we are not making any business with him (in case your concern is genuine). However the same goes for you. Your attempts to make us reveal our real identities were quite chilling. After all this, can you blame us that we don't want to reveal our identities? We don't have a problem with our respective governments knowing our identities, as we pay all required taxes, but we won't risk our well-being just so that you can have piece of mind by knowing who we are.



So, what will happen now in the future? NiceHash Miner will introduce some way of putting PhoenixMiner back in, it just isn't going to be automatic download by NiceHash. That is just way too risky. When people manually insert miners in, then NiceHash cannot be responsible for anything malicious if it ever happened. Similar destiny awaits all other anonymous miners. We don't hate PhoenixMiner and we did not want to destroy PhoenixMiner. This is just malicious talk. There was a risky situation and we had to take extraordinary action to protect NiceHash.
   Nothing changes for us too. We will warn people to be cautious when doing business with NiceHash. There are just too much shady things connected to your company - people with past criminal activity, security breaches, theft of huge amount of BTC, not taking any responsibility for preventing 51% attacks on the weaker coins through your service (how hard could it be to detect the mined coin by the DAG epoch, and to sound the alarm if someone tries to mine XYZ with more than 51% of the current network hash?).

   Finally, let's just stop with this BS, as it benefits no one. Everyone can make their own conclusions, and we are are sure that most miners have much better things to do with their time than reading about this storm in a teacup. We know we do.
fdov
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
March 13, 2021, 08:34:00 AM
 #8196

I started to think nicehash pushed the wrong version because of their massive overreaction over a broken link.
I have also shared this view with communities on the interwebs.

1. Sourcecode of nicehash is available on github, no changes since Mar 1, 2021.
2. A PhoenixMiner version was pushed to auto-update-enabled clients after this date, without github commits. Nicehash claims it was to disable the old phoenixminer.
3. Claiming you can check github for the source-code is crap. We can't know if they pushed some wrong url without committing to github.
4. IF you installed the 5.5d from spam posts in this forum, I would suggest exactly the reciepe NiceHash is suggesting to everyone who ever used phoenixminer.

Makes you think... but we don't know.

My suggestion to everyone keeping nicehash installed: Disable auto-update.
They can basically install and run anything they want on your machines with this feature enabled.
Nicehash can sign binaries as much as they want, I don't trust this feature from this source.


kthxbye.
shiftoshi
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
March 13, 2021, 10:18:06 AM
 #8197

and we are are sure that most miners have much better things to do with their time than reading about this storm in a teacup. We know we do.
Hey now. I just woke up and reading this with my coffee is a great start of my day. Smiley

Shlimann
Jr. Member
*
Offline Offline

Activity: 54
Merit: 5


View Profile
March 13, 2021, 10:52:05 AM
 #8198

Let me tell you something about Josip Juhas, aka minerstat owner. Josip Juhas was...
You justify yourself as a child.
"It was not me who broke this vase, this is all Josip Juhas!"
You have done tremendous damage to PhoenixMiner. A lot of my friends believed the blog post.
You didn’t even apologize, you just non-stop promoting your crappy QuickMiner and come up with childish excuses on the forum, and in reddit you delete posts that tried to explain the situation.
Be a man, admit your guilt, although this will no longer help bring back the Phoenixminer audience ...
Digital_Seytan
Jr. Member
*
Offline Offline

Activity: 221
Merit: 2

digiseytan@walletofsatoshi.com


View Profile WWW
March 13, 2021, 01:39:28 PM
 #8199

PM dev why does the phoenixminer software use more power and less hashrate ??

PMiner 5.5c  -straps 1 - 5 x gtx 1060 6GB 435.5 Watt and 116.5 Mhs

Gminer 2.47  -Mt 1 5xgtx 1060 6GB 417 Watt and 117.2 Mhs


same setting all afterburner


DonateSATS:Digiseytan@WALLETOFSATOSHi.COM
SHOPFREE: https://satsback.com/register/1QEJyGPlg4LN5kwx
ETC+Zil Pool:https://k1pool.com/invite/895eb07555
earlybird36
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
March 13, 2021, 03:50:04 PM
 #8200

Is there any way to delay the application of overclock on the core during dag creation. I know its possible on the memory with -mcdag but Im having issues on the coreclock during dag creation process. I know increasing memory will increase the hashrate but in my case, increasing the coreclock increases the hashrate as well. Weirdly it only happens on my gtx 1070.
Pages: « 1 ... 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 [410] 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 ... 499 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!