Author

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

sr. member
Activity: 280
Merit: 250
im having some big troubles here, i bought 0.079BTC x11 hashing power to hash at coinmine.pw .... the pool did not credit any balance or share to my account, i already send several emails to the pool support and also posted my problem at their bitcointalk thread: https://bitcointalk.org/index.php?topic=406178.280

Its not fun or fair to loose my hard earning of over 2 weeks in just 20 minutes and nobody reply or look at the situation (the owners) to help, please kindly help me support from nicehash to see if there was share work done on your side so i can have proof to send to the pool owner

If your BTC balance was reduced, then work was done. We have our own share validators in place. But if the pool you selected mined coin that does not use X11 coin, then all shares from NiceHash to the pool would be rejected.

Are there not enough orders for my 30 MH's?   I am trying to figure out if my fail over to my backup pool is legit as there are not enough orders or is there an issues here with NiceHash or is there an issue with my Fail-over and the way it is working..

We REALLY need more clear easy to read vision on # of orders vs. numbers of miners and when one side or the other is short..

Something simple like..

There are currently Orders for 4.2 TH and there are miners providing 5.2 TH... So there is an overage of 1 TH that will cause some miners here to fail over to their Back up pool.

OP please advise..


Also.. Rejects a lot higher for me than normal. Normal on here has been less then 1%..  Now on here my Reject rate is 13+%   Is this a Miner issue or a pool Issue?




That sounds like you having connection issues with NiceHash. We did no changes that could reflect this behavior, also there is no one else complaining regarding this.

Orders are pretty much irrelevant for providers. You are paid the average price, not the price of order your miner is working on. We changed this distribution to more fair one quite a while ago. You are paid what main page says and what following API says: https://www.nicehash.com/api?method=stats.global.current
full member
Activity: 289
Merit: 100
O2-Protocol.com Carbon Offset DeFi
im having some big troubles here, i bought 0.079BTC x11 hashing power to hash at coinmine.pw .... the pool did not credit any balance or share to my account, i already send several emails to the pool support and also posted my problem at their bitcointalk thread: https://bitcointalk.org/index.php?topic=406178.280

Its not fun or fair to loose my hard earning of over 2 weeks in just 20 minutes and nobody reply or look at the situation (the owners) to help, please kindly help me support from nicehash to see if there was share work done on your side so i can have proof to send to the pool owner
member
Activity: 112
Merit: 10
Are there not enough orders for my 30 MH's?   I am trying to figure out if my fail over to my backup pool is legit as there are not enough orders or is there an issues here with NiceHash or is there an issue with my Fail-over and the way it is working..

We REALLY need more clear easy to read vision on # of orders vs. numbers of miners and when one side or the other is short..

Something simple like..

There are currently Orders for 4.2 TH and there are miners providing 5.2 TH... So there is an overage of 1 TH that will cause some miners here to fail over to their Back up pool.

OP please advise..


Also.. Rejects a lot higher for me than normal. Normal on here has been less then 1%..  Now on here my Reject rate is 13+%   Is this a Miner issue or a pool Issue?


member
Activity: 112
Merit: 10
Is something wrong with Nicehash?   I have all 30 MH's pointed here but a lot of my MH's is failing over to my backup pool... Why???

Also getting Large Rejects rate  19.42 (9.88%)    WAY High..

Something is wrong with Nicehash..  Heading someone else for a while.
p4u
member
Activity: 111
Merit: 10
crypto lover
Any idea what difficulty should i set on Raspberry Pi with 5 blades (25 Mh/s)+?
Presuming you mean share difficulty:

Higher if you want less bandwidth consumption, but more variance.
Lower if you want higher bandwidth consumption, but less variance.

Performance/output will be statistically the same no matter what share difficulty the pool is using.  1 share every few seconds on average is a reasonable target, IMO.

I would say that higher is always better in reference to the profitability. The RTT (round-trip-time) between the worker and the pool will be something like 30ms (in one of the best scenarios). It means 3% of a second, so 1 share every 2 seconds means 1.5% of penalization (if not using jobs queue of course).
The minimum network I/O the better, always.

EDIT: actually it will depend on the implementation of the worker client. In if it is blocking until he gets the ACCEPT or not.
hero member
Activity: 700
Merit: 500
Any idea what difficulty should i set on Raspberry Pi with 5 blades (25 Mh/s)+?
Presuming you mean share difficulty:

Higher if you want less bandwidth consumption, but more variance.
Lower if you want higher bandwidth consumption, but less variance.

Performance/output will be statistically the same no matter what share difficulty the pool is using.  1 share every few seconds on average is a reasonable target, IMO.
member
Activity: 97
Merit: 10
Any idea what difficulty should i set on Raspberry Pi with 5 blades (25 Mh/s)+?
sr. member
Activity: 280
Merit: 250
Check your stats to see what is going on.
newbie
Activity: 6
Merit: 0
Now that the DDOS issues are behind us, how are you systems producing X11? I have about 6-7MH on the X11 algorithm and for some reason for the past 2-3 days, production has been nonexistent. Per day since the 22nd, my gear seems to be producing around 0.003BTC, which is nowhere near the actual amount I should be getting according the prices up on Nicehash.

Before the stat reset after the fight against DDOS, I was pulling in 0.01 BTC per 24 hours consistently.
sr. member
Activity: 280
Merit: 250
I had an order pointed at drkpool.com:3333 - 542 GH were accepted, then my order went dead. Gave it two hours, while my physicals miners were working fine with the pool; cancelled and resubmitted the order - losing my non-refundable fee in the process. My physical miners are still running great with the pool, NiceHash has my pool as dead still.

Current order is 9235.

Not happy  Huh

That sounds like pool blocked NiceHash. Some pools are still using old techniques and are not adjusted to high speed hashing power. I suggest you contact them and inform about this.
hero member
Activity: 979
Merit: 510
I will chime in and say that DDoS protection is around 7x more expensive than the DDoS attack rental to bring said protection down.
It's a hard battle to win, but using CDN and fallbacks can help just hard to code.
hero member
Activity: 539
Merit: 500
I had an order pointed at drkpool.com:3333 - 542 GH were accepted, then my order went dead. Gave it two hours, while my physicals miners were working fine with the pool; cancelled and resubmitted the order - losing my non-refundable fee in the process. My physical miners are still running great with the pool, NiceHash has my pool as dead still.

Current order is 9235.

Not happy  Huh
sr. member
Activity: 280
Merit: 250
If your order is not the top most, then you may still be in queue. Orders are filled in a following way; miners from low paying orders are directed to high paying orders, but not all at the same time, just up to 200 every 2 minutes. Orders are always being filled from top towards bottom. If your order is somewhere in the middle and orders above yours are not fully filled, then top orders have priority and you will have to wait to get hashing power.

If your pool is unstable, then you loose miners and will have to gain them again using method above. So it is very important to choose stable pool that doesn't drop connections.

But as you can see all orders above me are filled, and orders below me, way down to 0.7 are even filled. It stayed like this for another 2 hours until I cancelled the order and opened another. I was mining on Dedicated Pools Amsterdam server which is rock solid with 100% efficiency.

Then it is clearly possible that the pool was unstable. Dedicatedpools are known to be unstable, I have personally seen how dedicatedpools go down and all orders mining on it appear dead then.
sr. member
Activity: 252
Merit: 250
If your order is not the top most, then you may still be in queue. Orders are filled in a following way; miners from low paying orders are directed to high paying orders, but not all at the same time, just up to 200 every 2 minutes. Orders are always being filled from top towards bottom. If your order is somewhere in the middle and orders above yours are not fully filled, then top orders have priority and you will have to wait to get hashing power.

If your pool is unstable, then you loose miners and will have to gain them again using method above. So it is very important to choose stable pool that doesn't drop connections.

But as you can see all orders above me are filled, and orders below me, way down to 0.7 are even filled. It stayed like this for another 2 hours until I cancelled the order and opened another. I was mining on Dedicated Pools Amsterdam server which is rock solid with 100% efficiency.
newbie
Activity: 16
Merit: 0
What happens if you use another BTC address?
FYI... My stats are active again without resetting my miners. Also my payment went out for the first time in several days once my stats became active.
sr. member
Activity: 280
Merit: 250
If your order is not the top most, then you may still be in queue. Orders are filled in a following way; miners from low paying orders are directed to high paying orders, but not all at the same time, just up to 200 every 2 minutes. Orders are always being filled from top towards bottom. If your order is somewhere in the middle and orders above yours are not fully filled, then top orders have priority and you will have to wait to get hashing power.

If your pool is unstable, then you loose miners and will have to gain them again using method above. So it is very important to choose stable pool that doesn't drop connections.
sr. member
Activity: 252
Merit: 250
I understand how the NiceHash system works for a renter. Put in a price, if your the highest your MH are filled, other wise your in the queue. My problem im noticing is I put in a price higher than what is currently listed and my MH limit doesnt get filled, yet the cheaper prices are fully filled. I know that there is a lag between switching over but it still wont fill after an hour.
I thought the higher price gets preference over which order is placed first.
Can someone let me know how it works??

Here is a screenshot. My order is in the blue unfilled to the limit. Yet below mine at 0.7 BTC/GH and hashing at 3 GH

http://imgur.com/E5Rowzz
member
Activity: 112
Merit: 10
So is it normal for 1 BTC per MHS's per day to drop so much when prices rise???  I guess despite the drop we still making about the same since the price is up?   No one asking or worried about it but me so I guess so.

Or is this the new normal due to all the ASIC's coming on-line?


But a little surprised NiceHash is so low.. Since its more like the leaseRigs sites but better IMO..

p4u
member
Activity: 111
Merit: 10
crypto lover
Please add a HTTP-JSON API so we can check the profitability of NiceHash and the current status, so we can program scripts to control our workers.
sr. member
Activity: 280
Merit: 250
Well I am not sure where all the figures come from but I tried a side by side NiceHash vs Clevermining comparison
Date May 21st to May 22nd full 24hrs on both with 50,000 kh/s scrypt on each pool.
Here was my results NiceHash 47.2 mh/s scored me only .11618195 BTC plus 975 doge from a backup pool.
CleaverMining 46.76 mh/s scored me .13008909 BTC
If anyone has any ideas on how to make my kh/s more profitable let me know. Grin

We were under attack and no new orders were placed so for large amount of the time, miners were working on cheap orders for as little as 0.001 BTC/MH/day (yes some lucky buyers got quite some out of this).
Jump to: