Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 259. (Read 794394 times)

To make it easier to get started with NiceHash mining, I've created a guide with preconfigured settings for NiceHash using Awesome Miner.

Awesome Miner will also show the current profitability of the current NiceHash pool.


More information about this software can be found in this thread.

That's what the /s means

ok now i see you multiple it by seconds  thanks 

Its going on for a while now. Every time I compare the expected shares with my actual shares I see these discrepancies, I have seen it even worse. Yesterday I mined for over an hour with 60TH/s, I provided 5% of the entire p2pool during this time I should have found 12 shares and found only 2.

LOL , good one and well said

Same way a train going at 50 miles per hour would do 1200 miles per day.

There are 86400 seconds in a day, if that helps.

how can a 10 MH/s Scrypt rig produces 864 GH in one day.  it produces 10mh a day ty

37 vs 79 shares is within perfectly reasonable margin of error, too... It's nonsense to conclude from those results that "The hash rate that comes from nicehash is definitely poisoned" - complete nonsense.

I can show you plenty of mining stats that line up with that margin of error (e.g. I have found 1/3 as many blocks as expected, and over 3x as many blocks as expected over long long mining periods before).

Basically, every pool is vulnerable to this kind of attack at the end then. Unfortunately, nothing comes to my mind what we could do to resolve this issue. It is the fundamental issue of pooled mining in my opinion. But I doubt that the majority of provided hashrate is poisoned. And if it bothers you so much, then I suggest you to not use p2p pools.

Maybe someone is trying to hurt your business. Also he wouldn't make much less profit, he only filters out very difficult shares, the shares that are much more difficult than the easy shares that are used to count the hash rate. Unfortunately on p2pool also the difficult shares are needed, these are the shares that solve the blocks on the p2pool internal share chain, they are so high that only very few per hour are solved by an average miner. It reports the hash rate correctly with the help of the easy shares but it can't solve any p2pool share chain blocks which are needed to get reward on p2pool.

I have had it running now for 19.5 hours @ 20 TH/s, here are the results:



start: 22:30
end:   18:00
duration: 70200 seconds

my rate:     17.8 TH/s (average during above period)
pool rate: 1050.0 TH/s (average during above period)

expected time to share: 884 s  (=  15s * 1050 / 17.8 )
expected shares total:  79

actual shares total:    33  (4 orphan, 0 dead)


The hash rate that comes from nicehash is definitely poisoned. Maybe I should rent some more and point it to GHash.IO where It counts only the low difficulty shares.

The scrypt pool is dead? 

Again? 

Need some help.  I am mining on an sha256 pool and the difficulty for the worker is at 256.  I put in an order and it keeps going to "Disconnected. Pool difficulty too low" and showing the difficulty at 16, which is not correct.  How do I get nicehash to recognize that it is a higher difficulty?

Sorry, but for sure pools are OK - I'm using them directly. Can't connect only from nicehash (which of course in general like v much!).  
... yes , it's possible they block your IP
Best!

Can someone share me a bat file for sgminer 5.0 switching x11-13-15. thanks in advance.

I can make statement regarding usual stratum server for mining (not sure how much is p2p related to that); Shares can be used only on wallet that issues the work (target pool), because another wallet would have another address and all shares for target pool are invalid for another wallet - that is similar question that someone may ask himself why not keep high diff shares for self (or keep solved block for self and not send that share to the pool - that share is ONLY valid for pool's wallet).

If miner filters out all high shares, then he also makes less profit, because less shares are being sent.


It means that you should use another pool, because this one cannot be compatible with NiceHash, because there is no enough room for NiceHash to delegate work provided by remote pool. Usual, 95% of pools use extranonce2 size 4, we also permit 3, but if it is 2 or 1, we do not permit that - too small extranonce2 would cause quick nonce exhaustion on miners thus making them force to start sending duplicates.


It means that remote pool is unreachable (no connection could be established). Either address is incorrect, domain is not resolved to proper IP, pool is down, pool blocks our IP, wrong port, not stratum, or temporary internet connection problems between NiceHash and remote pool.

Anyone get error
but i am work fine
mining with my own RIG x11

but until now iam still confused
altcoin price is up and down, what exactly nicehash rate based on the price

sometimes get 0.6 so i can get ~400.000 mBTC per day
but if a lower price to 0.2 just get ~200.000 mBTC per day

Someone with lots of hash power 50+ TH/s is running a block withholding attack on nicehash. I just ordered no limit (~60TH/s) for over an hour and there were **no** shares above a certain difficulty. I noticed it because I mined at p2pool where I should have found lots of blocks on the share chain during that time (I had over 5% of p2pool for more than one hour) and then found only two blocks on the p2pool share chain.

No dead or orphans either, just none at all. At least 55 of these 60 TH/s were poisoned and useless: see here: http://37.59.48.89:9332/static/graphs.html?Day

Edit: Or maybe its the owner of nicehash himself who filters out all shares suitable to produce a p2pool share chain block and uses them himself.

Can't connect (Keccak) to: stratum+tcp://erebor.dwarfpool.com:3339
and also can't to: stratum+tcp://maxpool.1gh.com:17333

Status in order is constantly: Connecting to remote pool.

Please help

"Disconnected. Remote pool extranonce2 size too small."

What does that mean to my order?
Again something wrong here.....and no explanation 

Update

https://www.dropbox.com/s/i9j2wgx5923axub/NiceHash_stats.apk