Pages:
Author

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

newbie
Activity: 5
Merit: 0
So I have a bunch (16) of new L3+'s split between litecoinpool and prohashing, and nicehash seems like a better way to sell the hashing power. For the life of me though, I can't find anywhere on your site which spells out what details to give to my co-lo.

Note: I've never even seen the machines themselves, they're delivered from Bitmain to the co-lo, so I'm not too familiar with the interface. From setting up for the other services though, it seems I use a stratum url, a username and a password. Here's what I think everything ought to be set to, I'd appreciate any input if I'm going wrong somewhere

  • The stratum URL should be set to stratum+tcp://scrypt.us.nicehash.com:3333#xnsub  - is this correct ? I can't find it stated anywhere if the L3+ units support #xnsub or not. If it's supported, is there a '/' like for BFG/KNC miner
  • The username should be a bitcoin address from my wallet
  • Do I set the password to an identifier for the individual worker ? I think I saw that this ought to be blank
I saw that you state you provide individual worker statistics, but I'm not clear on how that works. Do I provide a different bitcoin receiving address for each worker, is that it ?

Thanks

Hi Spaced.......assuming you are the same from the ltc forum
Your url looks correct and L3+ can use xnsub. For the wallet address add a worker name like btcaddy.worker, that way you can track each worker on one page. I use x for the password, but you can set a few parameters such as start diff in the password field. I don't find this very useful. Most pools will adjust quickly anyway.


Hey Xardas. Yep, same 'ole me Smiley

Thanks dude - I've been noticing that litecoinpool has been a bit wobbly recently, so looks like a move is on the cards.
hero member
Activity: 635
Merit: 500
So I have a bunch (16) of new L3+'s split between litecoinpool and prohashing, and nicehash seems like a better way to sell the hashing power. For the life of me though, I can't find anywhere on your site which spells out what details to give to my co-lo.

Note: I've never even seen the machines themselves, they're delivered from Bitmain to the co-lo, so I'm not too familiar with the interface. From setting up for the other services though, it seems I use a stratum url, a username and a password. Here's what I think everything ought to be set to, I'd appreciate any input if I'm going wrong somewhere

  • The stratum URL should be set to stratum+tcp://scrypt.us.nicehash.com:3333#xnsub  - is this correct ? I can't find it stated anywhere if the L3+ units support #xnsub or not. If it's supported, is there a '/' like for BFG/KNC miner
  • The username should be a bitcoin address from my wallet
  • Do I set the password to an identifier for the individual worker ? I think I saw that this ought to be blank
I saw that you state you provide individual worker statistics, but I'm not clear on how that works. Do I provide a different bitcoin receiving address for each worker, is that it ?

Thanks

Hi Spaced.......assuming you are the same from the ltc forum
Your url looks correct and L3+ can use xnsub. For the wallet address add a worker name like btcaddy.worker, that way you can track each worker on one page. I use x for the password, but you can set a few parameters such as start diff in the password field. I don't find this very useful. Most pools will adjust quickly anyway.
hero member
Activity: 635
Merit: 500
Would you please offer a "night mode" color scheme? The current scheme is way too bright

Same goes for bitcointalk
newbie
Activity: 5
Merit: 0
So I have a bunch (16) of new L3+'s split between litecoinpool and prohashing, and nicehash seems like a better way to sell the hashing power. For the life of me though, I can't find anywhere on your site which spells out what details to give to my co-lo.

Note: I've never even seen the machines themselves, they're delivered from Bitmain to the co-lo, so I'm not too familiar with the interface. From setting up for the other services though, it seems I use a stratum url, a username and a password. Here's what I think everything ought to be set to, I'd appreciate any input if I'm going wrong somewhere

  • The stratum URL should be set to stratum+tcp://scrypt.us.nicehash.com:3333#xnsub  - is this correct ? I can't find it stated anywhere if the L3+ units support #xnsub or not. If it's supported, is there a '/' like for BFG/KNC miner
  • The username should be a bitcoin address from my wallet
  • Do I set the password to an identifier for the individual worker ? I think I saw that this ought to be blank
I saw that you state you provide individual worker statistics, but I'm not clear on how that works. Do I provide a different bitcoin receiving address for each worker, is that it ?

Thanks
legendary
Activity: 885
Merit: 1006
NiceHash.com
Buyers: we are moving from GH to TH units for X11, Kecak, Quark and Qubit hashing power purchases

Network hashrate for some coins using algorithms X11, Kecak, Quark and Qubit has increased significantly in the past months, pushing up the difficulty and lowering BTC/GH/Day prices for hashing power purchase on these algorithms. In order to make bidding for hashing power on these algorithms more accurate and competitive, we'll be switching from GH to TH units for X11, Kecak, Quark and Qubit hashing power purchases.

Please see here for the full press release: https://new.nicehash.com/news/203


Best regards,
NiceHash team.
legendary
Activity: 885
Merit: 1006
NiceHash.com
Support for Skunk algorithm

We are introducing the immediate availability for buying and selling hashing power with Skunk algorithm. The currently very popular Signatum coin can be mined with the Skunk algorithm hashing power. You can place orders and point them to any of your preferred pools for mining coins, based on Skunk algorithm.

Take a look here for more information: https://new.nicehash.com/news/204


Best regards,
NiceHash team.
legendary
Activity: 885
Merit: 1006
NiceHash.com
Hello,

All August 8th payment transactions are now confirmed. Thank you for you patience and thank you for using our services!


Best regards,
NiceHash team.
hero member
Activity: 910
Merit: 501
My Tuesday payment just arrived.  So they are definitely coming people....
member
Activity: 89
Merit: 10
Finally it confirmed.

Quote
Unknown at this time.  Ask next Wednesday!   Cheesy

They will answer in a week.  Cool
hero member
Activity: 910
Merit: 501
Is this for the August 8 issue only? How about this coming August 15 are wre getting the same issue again?

Unknown at this time.  Ask next Wednesday!   Cheesy
full member
Activity: 406
Merit: 105
Chosŏn Minjujuŭi Inmin Konghwaguk
Since this payment problem started, has anyone received a payout from NH?
They are actually paying. That's not the problem.

The problem is the WAY they are paying. If you check any of the last transactions sent by NH to their users, you will see that all of them are being sent with a fee of 6.165 sat/B - which is way lower than the average. And because of that, transactions are taking days to get confirmed.

Some of them already got confirmed, but most are still pending.

34c7d957fce453406640898dc4aa25e1976c74fa0f05fc92883c60f46cc9cf0d - confirmed
34c7d957fce453406640898dc4aa25e1976c74fa0f05fc92883c60f46cc9cf0d - confirmed

If you guys start trying a little bit to research and read what Nicehash posted, instead of screaming "scam", you all would have seen this:

Quote
The issue was that the transaction fee, which is automatically determined by BitGo - our wallet provider, was set at optimal level accordingly to the bitcoin transaction fees market at the time of the transactions. However soon after transactions were created the spamming of Bitcoin network began once again and bitcoin transaction fees significantly increased – making the applied transaction fee too low for the payment transactions to be confirmed fast. This significantly increased the time, needed for particular transactions to get confirmed. At the moment of this press release only approximately 5% of the total number of August 8th payments transactions are still left unconfirmed.

Please note that we are working around the clock with BitGo as well as with some major Bitcoin pools to make sure that all transactions will get confirmed.
https://new.nicehash.com/news/201
There was never a time in bitcoin history when  6.165 sat/B was an acceptable fee to get a transaction confirmed.
newbie
Activity: 22
Merit: 0
Is this for the August 8 issue only? How about this coming August 15 are wre getting the same issue again?
legendary
Activity: 2758
Merit: 6830
Since this payment problem started, has anyone received a payout from NH?
They are actually paying. That's not the problem.

The problem is the WAY they are paying. If you check any of the last transactions sent by NH to their users, you will see that all of them are being sent with a fee of 6.165 sat/B - which is way lower than the average. And because of that, transactions are taking days to get confirmed.

Some of them already got confirmed, but most are still pending.

34c7d957fce453406640898dc4aa25e1976c74fa0f05fc92883c60f46cc9cf0d - confirmed
34c7d957fce453406640898dc4aa25e1976c74fa0f05fc92883c60f46cc9cf0d - confirmed

If you guys start trying a little bit to research and read what Nicehash posted, instead of screaming "scam", you all would have seen this:

Quote
The issue was that the transaction fee, which is automatically determined by BitGo - our wallet provider, was set at optimal level accordingly to the bitcoin transaction fees market at the time of the transactions. However soon after transactions were created the spamming of Bitcoin network began once again and bitcoin transaction fees significantly increased – making the applied transaction fee too low for the payment transactions to be confirmed fast. This significantly increased the time, needed for particular transactions to get confirmed. At the moment of this press release only approximately 5% of the total number of August 8th payments transactions are still left unconfirmed.

Please note that we are working around the clock with BitGo as well as with some major Bitcoin pools to make sure that all transactions will get confirmed.
https://new.nicehash.com/news/201
member
Activity: 115
Merit: 10
Since this payment problem started, has anyone received a payout from NH?
member
Activity: 89
Merit: 10
"We are white and fluffy". It was BitGo fault Undecided
legendary
Activity: 885
Merit: 1006
NiceHash.com
Dear, users.

Please bear with us as we are working around the clock to solve this frustrating situation with the stuck transactions. We would like to stress out that since NiceHash operates (more than tree years) we have paid out more than 95.000 bitcoins in tens thousands of transactions where each and every one was confirmed and we delivered each and every bitcoin to our miners. Therefore we kindly ask you not to be insulting and do not spread wrong information.

We will make sure that all transactions will be confirmed. Please be patient, for more information please see here: https://new.nicehash.com/news/201

Thank you for understanding and thank you for using our services.

Best regards,
NiceHash team.
newbie
Activity: 1
Merit: 0
i got incoming payment from nicehash since 8 august, but until now i havent got even 1 confirmation,its still at 0 confirmation for almost 5 days,please fix this.
newbie
Activity: 20
Merit: 0
nicescamhash scamed more than 22x61=1342 people

(+2)these transactions will not be confirmed in the near future with bold 6s/b fee:

1d6cfcfe22a6deb36fd17c2e79dd4510a6d51799bca351bb5bb07051bb2d0bed
9abc6d857a77fe103ac62ab3d2373fc9a964a37868f966947c26fbd61d58746b
8fe4986f3d403403d914da5f29133bf1855dd34b50d1fea6d46243e1363282e5
d02c6e1ae5a2c7665e0488ce17a9db217565f491e0b6b51901f246f0c4556ca8
7a00de2fe5a2bc5dfc20e1c64964056893a9ebe2fe537dec93a51b97895c2ce9
003387da94a053cb27823c29aa8cfb53b8a7cb7d96f11a6781164993347324f7
4bc61fc0ed9bd2dfb34e1fe67d8cdb7e0941dbd5bdb9bab03ebc736c1b99cc14
b16365236c42640339913a7bb0484a857442b626396ebf80dc3c620ba391cc53
9cfaa939bfb2b486118e693f949b02a1a5d70fef5337a65a47375a7133ba3f4a
fe23dfdd67772dd9dea40182dd98427bb9c551d30519598263e87852493cb73a
4267faf9e3c7d24be118c1a5547559a66d2161172e505fa643bfcbf3cacd261f
34c7d957fce453406640898dc4aa25e1976c74fa0f05fc92883c60f46cc9cf0d
fbba61649ff132392efd65d2c3c2d0232a4bf7a5fddde1333570aa7a69a52fa8
68af4d9b77f2f50a918a114ea9ff181daadd95589e2ba64e7636f2faeced0ac3
95c804d3d61e065d868ba8ba1fedba929afd9068439841019ddf715fb951eec8
12349717a216800d05e7717f597964a87d9d1e08f8882c6356cff1ed21225ff3
34c7d957fce453406640898dc4aa25e1976c74fa0f05fc92883c60f46cc9cf0d
77e8eb8aa7d6c8a947e9c1b60ac18777c137b46fbc18b59823041c38bb8fb1b1
eb3dc95736c52c01016bd87fd0152502d4cf18cbb100efd162532c35f0f629ff
fc27df630e0fa843b160751670fd8a66d39a2ea1ed748ccd7ed81145557e49ef
48a4f32c0a34220e6b417c76beb7d089f63f5b2c70130b29a509a947ff316c0b
5388592b213098106816f7f2c5cc29eb36a680c523392df1b21c31011b2fdf20

suggest you rename your company in "6f@ckingsatoshi"
full member
Activity: 406
Merit: 105
Chosŏn Minjujuŭi Inmin Konghwaguk
 When was that time when 6 sats per byte is enough for a tx fee? Why are you insulting everyones' intelligence?
I'm not blaming you for running a scam, I'm calling you incredibly petty and stingy for making miners wait unknown amount of time to get their earnings, they have expenses you know to keep their rigs running.
hero member
Activity: 588
Merit: 520
We will make sure they get confirmed. Working with BitGo to resolve this issue.
Don't be ridiculous. There is no issue, you're just to stingy to pay tx fees like everyone else does, nobody will confirm those transactions.

At the time these transactions were created, that TX fee was sufficient. The majority of transactions from that day was confirmed (same fee). But unfortunately, spam started after it. Unconfirmed transactions will either get confirmed or we will resend them. Nobody will loose money and nobody will get scammed.


I don't know where you took that transaction, but this is clearly not ours. We use multisig addresses.

Pages:
Jump to: