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

[NiceHashSupport]

hi guys ...

why do stratums drop connection when connected to them for a period of time ...

stratehm proxy connects to westhash ...

then after a period of time - westhash drops those connections and refuses to reconnect them - no matter what algo ...

is this an inherent problem? ...

#crysx

Contact support with your IP and we will look into it.

[1715071632]

1715071632

[1715071632]

1715071632

[1715071632]

1715071632

[1715071632]

1715071632

[1715071632]

1715071632

[chrysophylax]

hi guys ...

why do stratums drop connection when connected to them for a period of time ...

stratehm proxy connects to westhash ...

then after a period of time - westhash drops those connections and refuses to reconnect them - no matter what algo ...

is this an inherent problem? ...

#crysx

Contact support with your IP and we will look into it.

will do ... tanx ...

it is from an aws server - but with a static ip ( elastic ip ) ...

will contact support with more detail ...

#crysx

[Searing]

Also what diff must put at worker
Per Titan miner?

Use this:

stratum+tcp://stratum.nicehash.com:3333/#xnsub#skipcbcheck

or

stratum+tcp://stratum.westhash.com:3333/#xnsub#skipcbcheck


You can use parameter d=diff in your password to set starting difficulty

bfggminer -o stratum+tcp://stratum.nicehash.com:3333/#xnsub#skipcbcheck -u YOUR_BITCOIN_ADDRESS -p d=16384 ...

Ok seems I'm on ..trying out my 2 cube titan setup (6 cube is still on litecoinpool) but does the difficulty setting even do anything in the password above?

put in the d=16384 but my adv page on the titan shows difficulty accepted as 16 so far

perhaps just leaving it blank? I assume your site auto adjusts the Titan accordingly anyway (or so it seems)

Anyway if this d=16384 in password does not do anything of note with the Titans because of auto adjustment at your end I'll yank it out .just to cut
down on the clutter and leave it blank

and I assume you want me to run this for say 48hrs before judging your site on speed / payouts / etc as a 'shake down' so to speak

anyway so far it is hashing let me know if I missed a particular setting or something to improve my tweaking of the above

[NiceHashSupport]

d= is used only for configuring starting diff.

[tbearhere]

Yes and is it possible to lower the difficulty a bit on the advantage?  I mean sending in 30 mh/s quark at  .160 or .320 is a little high. Sometimes makes my miner hash restart like it's not sending any yahs for like 30 seconds. thx

PS I like your new layout.  

[nicehash]

We're rolling in some new updates, therefore our service will be interrupted for short periods of time in the next 24h hours.

[chrysophylax]

We're rolling in some new updates, therefore our service will be interrupted for short periods of time in the next 24h hours.

is any part of this rollout going to be continuous connectivity to stratehm proxy? ...

when the proxy is idle - westhash disconnect the ip - then bans it so it doesnt connect for a period of time ...

we are working on a project ( yes - to bring more people in - to mine and rent ) which requires the persistent connection to westhash / nicehash while idle ...

support just suggested that we have a continuous miner on each of the proxies - but that is impossible ... considering that our project will have close to 36 proxies running on various algos ...

any help in this department? ...

#crysx

[NiceHashSupport]

We're rolling in some new updates, therefore our service will be interrupted for short periods of time in the next 24h hours.

is any part of this rollout going to be continuous connectivity to stratehm proxy? ...

when the proxy is idle - westhash disconnect the ip - then bans it so it doesnt connect for a period of time ...

we are working on a project ( yes - to bring more people in - to mine and rent ) which requires the persistent connection to westhash / nicehash while idle ...

support just suggested that we have a continuous miner on each of the proxies - but that is impossible ... considering that our project will have close to 36 proxies running on various algos ...

any help in this department? ...

#crysx

Unfortunatelly, we are under constant attack by botnet miners, therefore we have filters in place that ban IPs that only idle. If you have large hashing power and static IPs, contact us for a whitelist.

[chrysophylax]

We're rolling in some new updates, therefore our service will be interrupted for short periods of time in the next 24h hours.

is any part of this rollout going to be continuous connectivity to stratehm proxy? ...

when the proxy is idle - westhash disconnect the ip - then bans it so it doesnt connect for a period of time ...

we are working on a project ( yes - to bring more people in - to mine and rent ) which requires the persistent connection to westhash / nicehash while idle ...

support just suggested that we have a continuous miner on each of the proxies - but that is impossible ... considering that our project will have close to 36 proxies running on various algos ...

any help in this department? ...

#crysx

Unfortunatelly, we are under constant attack by botnet miners, therefore we have filters in place that ban IPs that only idle. If you have large hashing power and static IPs, contact us for a whitelist.

yes - that was the explanation that was given ...

i cant believe that in this day and age - people are so damned ruthless with those sorts of attacks ...

we have one static ip - with another 10 to come ...

still setting all the systems up - so this will take about a week to organize ... but we are very appreciative of the offer ...

we will pm you the current ip ( this is the test machine ) to whitelist and will update you next week when we have all of the systems up and running ...

we dont profess to have a lot of hashpower ... we are setting up a hash-donate system for the devs and coins / systems - whereby miners can donate their hashrates rather than just btc ( or other currencies ) ...

if this goes well - and word gets out - the direction this will take will be a positive one ... and one that will be used on only a few pools ... westhash / nicehash being one of the main ones ...

this becomes a win / win situation for you - the pool - and the miner ...

ill pm you the ip now ...

tanx ...

#crysx

[rkinnin]

Are we going to see SHA256 go to 0.110 or higher anytime soon?

[Muhammed Zakir]

Are we going to see SHA256 go to 0.110 or higher anytime soon?

Create a new coin like XPY. You can see a high increase in price.

[innerchaos]

Can I use an S5 on nicehash pools and if so which ones,  or would it be better on antpool
Also should I leave the difficulty alone or add a d=##

[nicehash]

Can I use an S5 on nicehash pools and if so which ones,  or would it be better on antpool
Also should I leave the difficulty alone or add a d=##

Sure you can. Difficulty will adjust automatically, but we suggest you to use advanced firmware:

https://www.nicehash.com/download/AntMiner-S5-SD-firmware_cgminer_4.9.0_nicehash_and_performance_graph.tar.gz

and use this setting for connecting:

stratum+tcp://stratum.nicehash.com:3334#xnsub

[Zels]

Was always like that since westhash started.

Using NH, and WH as failover, and often need weeks/month before my balance on WH is paid since only a few share goes to WH for me

[NiceHashSupport]

perhaps i missed smth, do you payout nicehash and westhash balances separately now ?
(for the same btc addy)

Not in same payment. We will be soon uniting min threshold between both locations.

[nicehash]

Dear users,

Today we rolled out an exiting feature for hashing power buyers: detailed order information with graph and statistics.





How to properly read information about order?

• Interval for all taken measures is 5 minutes. Therefore speed readings at start of order and when order becomes dead or alive will most likely be incorrect.
• Displayed speeds might be in slight discrepancy due to different and/or asynchronized measuring methods.
• Displayed data and chart will auto refresh every 30 seconds.
• Some web browsers may crash occasionally when viewing chart. To avoid this problem, use another web browser (Google Chrome works 100% well).
• Chart data cannot be used as a base to request any sorts of refunds. Due to pay-per-share nature of our payment system, miners are immediately rewarded for each valid share. These rewards are therefore non-refundable because we keep them only as owed balance to miners and not as our funds.

Hopefully these detailed statistics will help you to manage orders even more efficiently. You'll be able to compare speed and statistics with the ones, showed on you selected target (remote) pool. Now you can truly handle each order as you own virtual miner! Thank you for using our system and keep on hashing

Kind regards,
NiceHash

[nicehash]

IMPORTANT notice for sellers (miners): we're switching to new DNS structure for stratum servers

Hello,

To make our service even more scalable as well as future proof for new algorithms and fluctuating hashing power among different algorithms, we've prepared new DNS naming for our stratum servers.

Please note that there will be no hard switch to the new naming structure, we are using a soft grace period in which old and new naming coexists, and both, old and new stratum addresses works.

Nevertheless, we are asking you to make the following changes to your miner's configurations as soon as possible. The new DNS naming is already active and can be already used. Here are two major changes:

1) westhash.com is being renamed to usa.nicehash.com. This is ONLY true for stratum server addresses, WestHash web interface will still be available at https://www.westhash.com. However, we'll be merging both markets (and later adding also an Asian market) into single web interface in the future updates (of course, still with geographically separated physical locations of servers).

2) Each algorithm is having it's own unique stratum mining DNS address.

---
Here is a list for EU location servers (aka NiceHash):

Code:

scrypt.eu.nicehash.com
sha256.eu.nicehash.com
scryptnf.eu.nicehash.com
x11.eu.nicehash.com
x13.eu.nicehash.com
keccak.eu.nicehash.com
x15.eu.nicehash.com
nist5.eu.nicehash.com
neoscrypt.eu.nicehash.com
lyra2re.eu.nicehash.com
whirlpoolx.eu.nicehash.com
qubit.eu.nicehash.com
quark.eu.nicehash.com

And here is a list for USA location servers (aka WestHash):

Code:

scrypt.usa.nicehash.com
sha256.usa.nicehash.com
scryptnf.usa.nicehash.com
x11.usa.nicehash.com
x13.usa.nicehash.com
keccak.usa.nicehash.com
x15.usa.nicehash.com
nist5.usa.nicehash.com
neoscrypt.usa.nicehash.com
lyra2re.usa.nicehash.com
whirlpoolx.usa.nicehash.com
qubit.usa.nicehash.com
quark.usa.nicehash.com

Note that there is no more "stratum" string, the name of the algorithm implies this. Therefore you have to replace the string "stratum" with "[algorithm].eu" or "[algorithm].usa".

Essentially you have to delete the string "stratum" and then copy-paste "sha256.eu", "scrypt.eu", "x11.eu", "x13.eu", etc. or for USA location (aka WestHash) "sha256.usa", "scrypt.usa", "x11.usa", "x13.usa", etc.

For example, replace:

Code:

stratum.nicehash.com:3333
stratum.nicehash.com:3334
stratum.nicehash.com:3336
stratum.nicehash.com:3337
... etc.

with

Code:

scrypt.eu.nicehash.com:3333
sha256.eu.nicehash.com:3334
x11.eu.nicehash.com:3336
x13.eu.nicehash.com:3337
... etc.

And for USA (aka WestHash) location, replace:

Code:

stratum.westhash.com:3333
stratum.westhash.com:3334
stratum.westhash.com:3336
stratum.westhash.com:3337
... etc.

with

Code:

scrypt.usa.nicehash.com:3333
sha256.usa.nicehash.com:3334
x11.usa.nicehash.com:3336
x13.usa.nicehash.com:3337
... etc.

We HIGHLY RECOMMEND you to use the copy-paste (Ctrl+C, Ctrl+V) function for replacing individual strings instead of typing it manually to avoid typing mistakes - keep in mind that incorrectly typed address will result into dead/inactive pool connection.

And we kindly ask you to make these changes until June 15th, 2015. After this date the old naming of stratum servers will be deprecated.

Thank you for using our service and hopefully these changes won't cause you too many troubles. If you have any additional questions or troubles with making the required changes, please let us know to support@nicehash.com.

Thank you for using our service!


--
Kind regards,
NiceHash.com

[chrysophylax]

seems like a damn good move ...

will we be hearing from support for whitelisting our ips as well? ...

or at least have some whitelist application facility? ...

its only a few ips that we will require - and now with this new ( er ) structure - this whould make it a lot easier to implement in the ( now ) unique and singular backend ...

job well done guys ...

#crysx

[NiceHashSupport]

seems like a damn good move ...

will we be hearing from support for whitelisting our ips as well? ...

or at least have some whitelist application facility? ...

its only a few ips that we will require - and now with this new ( er ) structure - this whould make it a lot easier to implement in the ( now ) unique and singular backend ...

job well done guys ...

#crysx

Your provided IP has already been whitelisted.

[chrysophylax]

seems like a damn good move ...

will we be hearing from support for whitelisting our ips as well? ...

or at least have some whitelist application facility? ...

its only a few ips that we will require - and now with this new ( er ) structure - this whould make it a lot easier to implement in the ( now ) unique and singular backend ...

job well done guys ...

#crysx

Your provided IP has already been whitelisted.

fantastic guys ...

when i get back from my personal business on monday - i will have a look at testing and implementing a few connections via the ip - and if all works - will be in touch with the larger server ...

is it any wonder that nicehash / westhash is so damned popular? ... ...

#crysx