Author

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

sr. member
Activity: 457
Merit: 273
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.
sr. member
Activity: 282
Merit: 250
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://bitcointalksearch.org/topic/annjpcmake-jackpotcoin-great-again-584481

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.
full member
Activity: 322
Merit: 100
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
trc
full member
Activity: 164
Merit: 100
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. Smiley
Enjoy.
sr. member
Activity: 280
Merit: 250
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.
newbie
Activity: 44
Merit: 0
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.
member
Activity: 77
Merit: 10
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?
sr. member
Activity: 280
Merit: 250
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.
newbie
Activity: 53
Merit: 0
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.
full member
Activity: 144
Merit: 100
Hey guys. If you are using the v5 builds of sgminer and have problems, please let us know here: https://github.com/sgminer-dev/sgminer/issues/new

First for those who cannot or don't want to help with the problems, you can run with a single pool and there should be no problems. The issues are usually happening when switching algorithms.

We are aware of a few issues and are working to fix them (there has been significant progress already in the past few days). It helps if you run sgminer with "-v" option  and show us a screenshot or copy-paste of text in sgminer when it crashes. For Linux users you can also use this configure "CFLAGS="-g -O1 -Wall -march=native" ./configure" and then make, which will enable better traces on crash. Also you can run with "-T -v" or even "-T -D" which will give much more information and thus make it easier to find and fix the problems.
sr. member
Activity: 280
Merit: 250
Is it possible to add a "Total Unpaid balance BTC" for all Algos together on the Website when watching the AccountPage?

Will think about that one. Until we have unified minimal payment threshold in place, this total balance might cause additional confusion.

Could you make ajax refresh when user clicks to refresh orders?

Also, it's very unhandy to cancel the orders and create a new ones when i'm going to decrease the price. Why does it not allowed?

Why do you need it?

Price reduction is not permitted for obvious reasons - you could drag current miners with you. In practice, someone setting top price and collecting all miners could then drop price severely down to 0.01 giving miners very small payment. All miners would have to get disconnected if price gets decreased and for that reason, new order is needed.
newbie
Activity: 38
Merit: 0
Could you make ajax refresh when user clicks to refresh orders?

Also, it's very unhandy to cancel the orders and create a new ones when i'm going to decrease the price.  Why does it not allowed?
newbie
Activity: 53
Merit: 0
Is it possible to add a "Total Unpaid balance BTC" for all Algos together on the Website when watching the AccountPage?
sr. member
Activity: 280
Merit: 250
1. For experienced user, it is way simpler to simply copy & paste whole line in, no doubt about that. But we are worried about newbie users. There were already tons of mistakes, people don't include port, they make double stratum+tcp and similar nonsense. When port is separate it explicitly forces you to use it.

2. Added.
newbie
Activity: 38
Merit: 0
I really like to use your service, and I have two suggestions:

1. Could you make one field for pool instead of "Stratum hostname or IP" + "Port" ? I often copy direct line from my pools.conf, like "stratum+tcp://stratum.anypool.com:3333". And I have to delete "stratum+tcp" and then cut port and paste it in another field.

2. There is no total BTC cost in completed orders list. I'd like to know how much did I paid for that.
sr. member
Activity: 280
Merit: 250
Not really, we have prepared binaries too. Just check the page I referred you to.
full member
Activity: 130
Merit: 100
My rigs frequently see the nicehash pools as dead and jump to a backup pool. This happens frequently, almost every 5 minutes. Is it just me?

This is happening if you don't use recommended software that supports extranonce1 change. Check here: https://www.nicehash.com/software/

Ahh okey Smiley So its time to spend hours in the wilds of linux stuff :I
sr. member
Activity: 280
Merit: 250
My rigs frequently see the nicehash pools as dead and jump to a backup pool. This happens frequently, almost every 5 minutes. Is it just me?

This is happening if you don't use recommended software that supports extranonce1 change. Check here: https://www.nicehash.com/software/
Jump to: