Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 268. (Read 794394 times)
July 15, 2014, 10:01:58 AM
Since yesterday my SHA hashrate has been way down. I thought it was my rig (S2) and started tweaking things, but when nothing fixed it I reverted to what I had and tried another pool (multipool.us) ... with the exact same settings I get ~1116 Gh/s on multipool, and about 976 Gh/s on Nicehash ... prior to yesterday I'd get ~1.1 Th/s on Nicehash with those settings ... not sure what's up ... anyone else experiencing anything similar? Is it related to the DDOS?
July 14, 2014, 11:50:28 PM
what is up with these 0.0900 BTC orders (SHA256) running at full speed without limit? Break even is currently around 0.0290!
Did someone hack the website and is draining it empty? Surely nobody in their right mind would pay 3 times the market price to rent hash power.
Did someone hack the website and is draining it empty? Surely nobody in their right mind would pay 3 times the market price to rent hash power.
Shh... don't point stuff like this out, some of us are trying to make money!!!
July 14, 2014, 11:14:47 PM
who the f give a damn about ipominer?
Its a Great Pool ! ...the real question is who cares what YOU a newbie sock puppet thinks...Answer Nobody. As far as what NiceHashDev has to say about the problem being discussed not happening at other pools I say BS ive had a ton of problems and disconnects and lower than expected hashrate at Dedicated pool as well IPOminer and this all started just recently when you clearly changed something.
going to trash ipominer? fuck that NH has robbed me out of damn near 2 btc in the last few weeks, probly using the hash I paid for to mine themselves, so if its fuck anybody it fuck fucking thiefhash.
July 14, 2014, 09:26:46 PM
who the f give a damn about ipominer?
Its a Great Pool ! ...the real question is who cares what YOU a newbie sock puppet thinks...Answer Nobody. As far as what NiceHashDev has to say about the problem being discussed not happening at other pools I say BS ive had a ton of problems and disconnects and lower than expected hashrate at Dedicated pool as well IPOminer and this all started just recently when you clearly changed something.
July 14, 2014, 08:46:19 PM
I love the new Refill button, have you thought about adding a pause button?
I'm often mining a coin by difficulty and manually canceling the order and redoing the order when difficulty drops. A pause button would be AWESOME.
I'm often mining a coin by difficulty and manually canceling the order and redoing the order when difficulty drops. A pause button would be AWESOME.
July 14, 2014, 02:40:01 PM
Thank you, NiceHash.
EXCELLENT site.
EXCELLENT site.
July 14, 2014, 02:26:59 PM
who the f give a damn about ipominer?
July 14, 2014, 02:24:54 PM
what is up with these 0.0900 BTC orders (SHA256) running at full speed without limit? Break even is currently around 0.0290!
Did someone hack the website and is draining it empty? Surely nobody in their right mind would pay 3 times the market price to rent hash power.
Did someone hack the website and is draining it empty? Surely nobody in their right mind would pay 3 times the market price to rent hash power.
Hate to think of this, but could newbies really mistake sha256 for nist5? icebergcoin was rented heavily everywhere..
Else, I dunno, but my wallet sure loves it as I have my bitcoin miners on here.
July 14, 2014, 01:12:22 PM
Python stratum-mining doesn't have an option to decide how it processes packets. It runs under twisted and all of the json code is handled by the stratum package that was written directly by slush himself.
If a miner can connect fine, and then nicehash puts something in between the miner and the pool that makes things stop working, it seems to me it's nicehash's problem and responsibility to fix this and if he needs to involve the pool owner he should be respectful and not try to shift blame by calling out the pool in public like he has. To my knowledge there is no contract between nicehash and ipominer and if nicehash does not give the user a choice in pools then they are responsible when things don't work.
If a miner can connect fine, and then nicehash puts something in between the miner and the pool that makes things stop working, it seems to me it's nicehash's problem and responsibility to fix this and if he needs to involve the pool owner he should be respectful and not try to shift blame by calling out the pool in public like he has. To my knowledge there is no contract between nicehash and ipominer and if nicehash does not give the user a choice in pools then they are responsible when things don't work.
I doubt the issue is inside slushs code, but must be related to recent addition of variable diffs by Ipominer.
I am sorrry, but it looks like you don't have full understanding of how our system works exactly. Did someone ask you to post in this thread? Because you started posting just yesterday.
All other pools except Ipominer works fine.
Cgminer/sgminer is not god. I will remind you of the bugs that we discovered - extranonce in cgminer 3.7.2 and idlebug was present in even most recent cgminer and sgminer. Guess with what was idlebug related? Networking! So, we simply cannot afford to take another publicly available code and say - this code is 100% reliable, we have to build on top of that. No, the only valid document we take are specifications (yes, these are poor) written by slush himself and found at various places around the internet.
I found a post by slush regarding a similar problem, but with regards to the pool rather than miner:
I have read the discussion about separating target/difficulty and work data. I have to say I think this was a mistake as it opens possibilities for abuse. I think something about these issues should go in the docs. Otherwise someone is going to create a naive implementation with some nasty issues.
Well, after discussion with Kano I slightly changed my mind. As I described few posts ago, with slightly modified meaning of "set difficulty" message, everything should be fixed.
Instead of meaning "stop sending lower difficulty shares than X immediately", set_difficulty should mean "all next jobs are using difficulty X". This still keeps the concept of separated difficulty message from the job itself, it doesn't require sending both messages together, fixes the problem of roundtrips (sending some bad-diff shares by the client because of latency) etc. It also gives the possibility to choose if pool wants to change difficulty in aggressive or in lazy way; by just sending "set difficulty" message without new job with clean_jobs=True, clients will slowly adopt higher difficulty as miners will start using new jobs, but pool can enforce higher difficulty with immediate effect by sending clean_jobs=True, as it is now.
This change in protocol is also backward compatible, because pools using current meaning of set_difficulty don't need to change anything, they just *may* stop sending clean_jobs job, if they want. Because of this, it is win-win solution for me. I described this already, but the idea didn't get any significant attention yet.
Quote
Is it ok to pipeline commands to the client? That is, send the difficulty change and new work (2 RPC calls) in quick succession without waiting for a reply to the first.
Yes, commands (notifications) can be pipelined. set_difficulty() and notify() don't expect any response from the client. Just sending one packet with both commands serialized is possible.
One interesting part is:
This service abstracts the pool it's mining on away from the end user and out of the user's control, correct?
To my knowledge there is no contract between nicehash and ipominer and if nicehash does not give the user a choice in pools then they are responsible when things don't work.
There are two types of "users" on NiceHash - buyers and sellers. The sellers (miners) are the ones who don't know where their shares are being directed at. The buyers are the ones who do the directing. So in that sense, users (buyers) do have a choice in pools. Now, Ipominer's site says it uses a "modified Proportional scoring system". If this system was paying out based on the higher difficulty (the same one that miners on NiceHash were using), then there shouldn't be a problem other than the aforementioned hashrate display issue. If instead, however, their system was basing share payout value on the lower diff, or not at all for those shares, then there's a problem. The solution would be to recalculate submitted share value and pay their users a compensation for the difference.
July 14, 2014, 11:41:48 AM
can't connect to stratum 
(port 4xxx and 3xxx)
nslookup info:
Non-authoritative answer:
Name: stratum.nicehash.com
Address: 159.8.2.66
EDIT: Looks working now. Thanks!
(port 4xxx and 3xxx)nslookup info:
Non-authoritative answer:
Name: stratum.nicehash.com
Address: 159.8.2.66
EDIT: Looks working now. Thanks!
July 14, 2014, 11:39:43 AM
what is up with these 0.0900 BTC orders (SHA256) running at full speed without limit? Break even is currently around 0.0290!
Did someone hack the website and is draining it empty? Surely nobody in their right mind would pay 3 times the market price to rent hash power.
Did someone hack the website and is draining it empty? Surely nobody in their right mind would pay 3 times the market price to rent hash power.
Maybe it was for BitcoinDark
July 14, 2014, 11:35:25 AM
what is up with these 0.0900 BTC orders (SHA256) running at full speed without limit? Break even is currently around 0.0290!
Did someone hack the website and is draining it empty? Surely nobody in their right mind would pay 3 times the market price to rent hash power.
Did someone hack the website and is draining it empty? Surely nobody in their right mind would pay 3 times the market price to rent hash power.
July 14, 2014, 11:09:36 AM
Hi, when i put a X13 order to buy M/Hs... the system say "PLEASE WAIT"... for hours.
Im been trying a lot... Is the first time that I want to place order..
Somebody know whats happen?
Im been trying a lot... Is the first time that I want to place order..
Somebody know whats happen?
July 14, 2014, 10:55:40 AM
Let me guess, another attack...?
Time to used backup pool
maybe coz Gaza cyber war effect
What Gaza cyber war... maximum they have there is 3 camels and suicide bombers... "cyber war"...maybe coz Gaza cyber war effect
July 14, 2014, 08:41:03 AM
Time to used backup pool
maybe coz Gaza cyber war effect
maybe coz Gaza cyber war effect
July 14, 2014, 07:56:37 AM
Yes, now they target stratum ports and cause familiar issues for legit miners to be unable to connect.
July 14, 2014, 07:39:53 AM
Unfortunately another DDOS attack, but has been filtered out now.
I really wish there was a good way to find the perpetrators of these attacks and prosecute them.
We forward each attack to authorities. We also pointed out several suspects that have motive for these attacks. The investigation is going on, of course, perpetrators will not know that until police knocks on their doors.
BTW; The last attack was more than 1.5 gbps.
Cripes, that is a few bots. Unfortunately, with people getting higher and higher home Internet speeds it doesn't take too many remote controlled computers to generate a boat load of traffic.
EDIT: And they are back offline. Not a good morning.
July 14, 2014, 07:31:38 AM
This service abstracts the pool it's mining on away from the end user and out of the user's control, correct?
why do you care? you pointed your pool to nicehash or what?
July 14, 2014, 07:27:26 AM
Unfortunately another DDOS attack, but has been filtered out now.
I really wish there was a good way to find the perpetrators of these attacks and prosecute them.
We forward each attack to authorities. We also pointed out several suspects that have motive for these attacks. The investigation is going on, of course, perpetrators will not know that until police knocks on their doors.
BTW; The last attack was more than 1.5 gbps.
July 14, 2014, 07:25:13 AM
Unfortunately another DDOS attack, but has been filtered out now.
I really wish there was a good way to find the perpetrators of these attacks and prosecute them.
Jump to: