[ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool

[nicehashdev]

Dont think its a failure. But is it right that it jump between X11 and X13? Never saw the Algo jump to scrypt or nscrypt.

Scrypt or nscrypt haven't been more profitable so far.

[Dehumanizer]

I am having some problem with X11 and X13 pools right now. Both X11 (port 3336) and X13 (port 3337) are shown as DEAD in sgminer. All other ports for scrypt, nscrypt and keccak are alive and working.
What could cause this?

[Bawb3]

I've been mining on NiceHash for quite a while now, and while I love the simplicity of the service, and the payouts have been good. However I have a question about how the btc/ghs/day price is determined.

From what I understand, the site takes an average of all existing, not-dead orders to determine what the current payout is for shares coming in (that number next to each algo on the main page). The problem I'm seeing is when people add orders that are so low-priced, orders which will never actually get filled or worked on, are still bringing down the average payout price. Could this be abused by simply adding a bunch of lowball orders that never will receive any hash power, just to lower the overall average? Or are those orders marked dead after sitting idle for x time? If not, wouldn't it make more sense to take the average of the orders that are currently being worked on by miners, as opposed to including ones sitting there doing nothing?

Sure, this could be offset by using the price limit feature, but they seem to have encouraged a lot of people to not use it. If more miners used the price feature, people putting in very low orders would be guaranteed to never receive hash power, even if the service get DDOS attacked, and new orders cant be put in.

[nicehashdev]

I am having some problem with X11 and X13 pools right now. Both X11 (port 3336) and X13 (port 3337) are shown as DEAD in sgminer. All other ports for scrypt, nscrypt and keccak are alive and working.
What could cause this?

Try again after 3 hours.

I've been mining on NiceHash for quite a while now, and while I love the simplicity of the service, and the payouts have been good. However I have a question about how the btc/ghs/day price is determined.

From what I understand, the site takes an average of all existing, not-dead orders to determine what the current payout is for shares coming in (that number next to each algo on the main page). The problem I'm seeing is when people add orders that are so low-priced, orders which will never actually get filled or worked on, are still bringing down the average payout price. Could this be abused by simply adding a bunch of lowball orders that never will receive any hash power, just to lower the overall average? Or are those orders marked dead after sitting idle for x time? If not, wouldn't it make more sense to take the average of the orders that are currently being worked on by miners, as opposed to including ones sitting there doing nothing?

Sure, this could be offset by using the price limit feature, but they seem to have encouraged a lot of people to not use it. If more miners used the price feature, people putting in very low orders would be guaranteed to never receive hash power, even if the service get DDOS attacked, and new orders cant be put in.

Orders that have no miners working on do not contribute to price at all, because no BTC is taken from these orders.

[trc]

I've done this last week but haven't posted here. A CSS mod via chrome extension called stylebot. When you add the extension, you'll be able to apply any mod submitted for a given site from its menu. "Install style from social"

Black NiceHash:
http://stylebot.me/styles/5879

Screenshot is old but code is updated to work with new site updates. Font is also changed because it wasn't very comfortable on chrome.

This just changes the css but if you're skeptical, wait for a probable NiceHash approval.
Enjoy.

[espressodelisi]

is there a problem with payments?


I have a payment record in payments list but when I click the blockchain.info link it says transaction not found and I have not received that payment.

This is the problem item from the payments list:

Date UTC   TXID   Amount BTC   Fee BTC
2014-06-09 14:41:36   1153a3de188d17384bf381d1aa197c70925270cff6328a60703f0124fc5e618f   0.00200609   0.00004094

[nicehashdev]

https://blockchain.info/tx/1153a3de188d17384bf381d1aa197c70925270cff6328a60703f0124fc5e618f

[espressodelisi]

https://blockchain.info/tx/1153a3de188d17384bf381d1aa197c70925270cff6328a60703f0124fc5e618f

thanks for the info.
I think I should a little bit longer to see the transaction.

[atomrigs]

Please add a new hash algorithm, JHA.
It is currently used for JackPotCoin (JPC), but very soon it will be very popular among other new clones using this algo.
Right now the hashpower in JPC has not catched up its price increase speed. There is BIG demand for hash power in the community.

Currently the main exchange is
https://bittrex.com/Market/Index?MarketName=BTC-JPC

Main JPC Info
https://bitcointalk.org/index.php?topic=584481.0

You find JHA's technical features on
http://www.bomijoa.com/?document_srl=4631

Q1. What is Jackpot Hashing Algorithm? And what’s the purpose of it?

A: JHA has designed using Random Hashing Method and Random Variable Hashing Round using SHA3, Blake, Grøstl, JH, Skein. and, Archive the highest Secure Level via the currently announced methods without increase the requirements such as electric or hardware cost.  and Permanently ASIC resist because of there are multi-level of anti-parallelism in instruction, sub module, even full rounds of hashing.
We using SHA3 512 Hashing for input round, and 0~7 extra random hashing rounds are followed. The length of round will be adjusted by time.

Reduce the hashing load but increase the security
JHA is using variable random hashing rounds, it will reduce the hashing power requirements to 1/2 compare the linear hashing method. but, Up to 16234 times higher security. And, The rounds will be increased by time via increasing of mining hardware to protect the old CPU and GPU miner.

Permanent ASIC resist without increase the hardware power usage.
To archive the large scale miner such as ASIC miner, JHA need the very high power host processor to increase the threads of compute unit in ASIC or the modern GPU. It will increase the mining hardware cost (not just chip level) and make impossible to use with coin.

Power saving for GPU.
Using heavy anti-parallelism, it using < 75% of ALU in the modern SIMD GPU. and, It force to work GPU in the lower power consumption mode.

[kenshirothefist]

Please add a new hash algorithm, JHA.

Yes, it looks like an interesting algorithm. I can see it uses (yet another) fork of sgminer for AMD GPU miners ... if you can merge JHA support from this https://github.com/rtc29462/sgminer into the new sgminer v5 https://github.com/sgminer-dev/sgminer/tree/v5_0, then we'll add this algo to NiceHash and include it into our profit-switching mode. Get in touch with mrbrdo, the current sgminer v5 maintainer (https://github.com/mrbrdo) and try to do the merging.

[DareC]

Multi-algo ports all seem down.

[lbr]

Multi-algo ports all seem down.

+1

[guzzzi]

Multi-algo ports all seem down.

Yes here too ... everything is dead

[elpsycongro]

x13 showing as dead

[jedimindtriks]

cant connect to x13 as well.

i have to use trademybit in the meantime

[oktay50000]

pool getting disconections and dead
fix please

[nicehashdev]

Fixed. There were some issues regarding sockets.

[punisher1]

you can fix the work restart in the miner ?
how about pool disconecting the miner after work restart sometimes can be fixed ?

[nicehashdev]

you can fix the work restart in the miner ?
how about pool disconecting the miner after work restart sometimes can be fixed ?

Many rapid work restarts are actually rewards to you.

Use compatible mining software from here: https://www.nicehash.com/software/ to get rid of disconnects.

[punisher1]

i`m using sgminer from http://getpimp.org but only on NiceHash i`m getting enough work restart , and my hash rate goes down after many these .