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

[xiaolin1579]

Any plans for supporting LBRY coin and Sia Coin ?

[1715031096]

1715031096

[1715031096]

1715031096

[1715031096]

1715031096

[nicehash]

Any plans for supporting LBRY coin and Sia Coin ?

Yes, we're also working on this. Sia is a bit problematic since they again re-invented stratum protocol (https://siamining.com/stratum) and we have to adjust our service to this ... this is why it is taking a bit longer. Stay tuned on Twitter @NiceHashMining for updates.

Best regards,
NiceHash team.

[xiaolin1579]

Any plans for supporting LBRY coin and Sia Coin ?

Yes, we're also working on this. Sia is a bit problematic since they again re-invented stratum protocol (https://siamining.com/stratum) and we have to adjust our service to this ... this is why it is taking a bit longer. Stay tuned on Twitter @NiceHashMining for updates.

Best regards,
NiceHash team.

will be waiting   
Thank you very much.

[_Django05_]

Dear miners,

We are introducing the immediate availability for buying and selling hashing power with CryptoNight algorithm: https://www.nicehash.com/index.jsp?p=news&id=99

Thank you for using our service!

Best regards,
NiceHash team.

Finally, cryptonight has been listed. waiting for hash power to go up so i can rent some.
Thanks.

[SLBitmania]

Hey anybody know why is this
"104.194.28.194:3333   Connecting to remote pool.   0   0.0000   0.00000000"
my pool is Kano CKPool now past 7Hrs its like this (dead)
pls anyone know about this help me
Thanks

[xiaolin1579]

Dear miners,

We are introducing the immediate availability for buying and selling hashing power with CryptoNight algorithm: https://www.nicehash.com/index.jsp?p=news&id=99

Thank you for using our service!

Best regards,
NiceHash team.

I have tried using mining Claymore CryptoNote GPU Miner mining, but then encountered some problems.

Code:

	ษออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออป
	บ            Claymore CryptoNote GPU Miner  v9.3 Beta            บ
	ศออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออผ
	
        Cards available: 1 
	GPU #0: name: Pitcairn, 2048 MB available, 16 units 
	Total cards: 1 
	Initializing...

	card 0, m1 2048, m2 1792 w 128
	0 m = 2
	GPU #0: HashCnt = 512
	POOL version
	b135
	GPU #0: -a 1 mode selected
	4 pools specified.
	Press "m" key for tune mode.
	Stratum - connecting to 'cryptonight.jp.nicehash.com' <198.11.195.136> port 3355
	Stratum - connecting to 'cryptonight.jp.nicehash.com' <198.11.195.136> port 3355
	Stratum - Connected
	Stratum - Connected
	got 304 bytes
	buf: {"jsonrpc":"2.0","id":1,"error":null,"result":{"id":"252249871424638","status":"OK","job":{"job_id":"00000005402d311b","blob":"0203fcfef9bd058e6dbc1f97b3ad3bfa8fa19819fb689a4df10ff3f25e9d3aee9f55482f2533ec00000023097dad49f0a4e20994044743519cc9c7c61ac3bfe753bd45bc7361cd3df2943701","target":"b88d0600"}}}

	parse packet: 304
	new buf size: 0
	Pool Diff 10000
	df has same pool, skip
	got 79 bytes
	buf: {"jsonrpc":"2.0","id":1,"error":{"code":24,"message":"Incorrect BTC address"}}

	parse packet: 77
	Error in server response
: {"jsonrpc":"2.0","id":1,"error":{"code":24,"message":"IncorrectBTCaddress"}}
	buf was cleared
	Round
	GPU 0: HashCnt = 512, time = 1090 ms, hashrate = 469 h/s 
	Round
	GPU 0: HashCnt = 512, time = 1020 ms, hashrate = 501 h/s 
	round found 1 shares
	Round
	08/25/16-12:19:07 - SHARE FOUND (target 10000) - (GPU 0 of 1)
	got 63 bytes
	buf: {"jsonrpc":"2.0","id":1,"error":null,"result":{"status":"OK"}}

	parse packet: 63
	Share accepted
	new buf size: 0
	GPU 0: HashCnt = 512, time = 1033 ms, hashrate = 495 h/s 

[thedreamer]

How about increasing the uptick price of nicehashbot in the update? at 0.0001 intervals it can NOT keep up with moving prices.
Also the 0.0001 downtick every 10minutes is just an insulting way to make sure after a price hike people keep paying the inflated prices. This is all fake and screwing tons of renters from nicehash/westhash.

Make all these price ticks (up and down) adjustable by the renter and you will have a MUCH better business..

[golden0707]

Hello! Nicehash, could you please add a row in worker tab with info of duration of continious mining in pda version ?
Using PC its displayed , using smartphone its only

XnSub   Worker    Speed (accepted)
                worker1   97.35 MH/s

Thank you

[fr4nkthetank]

How about increasing the uptick price of nicehashbot in the update? at 0.0001 intervals it can NOT keep up with moving prices.
Also the 0.0001 downtick every 10minutes is just an insulting way to make sure after a price hike people keep paying the inflated prices. This is all fake and screwing tons of renters from nicehash/westhash.

Make all these price ticks (up and down) adjustable by the renter and you will have a MUCH better business..

You can change the way it behaves yourself in visual basic (pretty sure about this).  You dont need coding knowledge, just poke around and change some values here and there   I think its more fun and you'll get better results than waiting for nicehash to update it...

[smilodon]

my gtx 750 ti not workin in cryptonight algo.


C:\Users\nvidia\Desktop\ccminer-cryptonight-windows-new\ccminer-cryptonight-wind
ows>ccminer.exe -o stratum+tcp://cryptonight.eu.nicehash.com:3355 -u 15TZv5B7Bq6
G9keCBYR6tTD7vvTbwtnhEY.nvidia -p d=5000
    *** ccminer-cryptonight for nVidia GPUs by tsiv ***
 based on ccMiner by Christian Buchner and Christian H.
 based on cpuminer-multi by LucasJones
 based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler
    BTC donation address: 1JHDKp59t1RhHFXsTw2UQpR3F9BBz3R3cs
    DRK donation address: XrHp267JNTVdw5P3dsBpqYfgTpWnzoESPQ
    JPC donation address: Jb9hFeBgakCXvM5u27rTZoYR9j13JGmuc2
    VTC donation address: VwYsZFPb6KMeWuP4voiS9H1kqxcU9kGbsw
    XMR donation address:
      (man these are long... single address, split on two lines)
      42uasNqYPnSaG3TwRtTeVbQ4aRY3n9jY6VXX3mfgerWt4ohD
      QLVaBPv3cYGKDXasTUVuLvhxetcuS16ynt85czQ48mbSrWX
-----------------------------------------------------------------
[2016-08-28 04:30:23] Using JSON-RPC 2.0
[2016-08-28 04:30:23] 1 miner threads started, using 'cryptonight' algorithm.
[2016-08-28 04:30:23] Starting Stratum on stratum+tcp://cryptonight.eu.nicehash.
com:3355
[2016-08-28 04:30:23] GPU #0: GeForce GTX 750 Ti, using 40 blocks of 8 threads
[2016-08-28 04:30:23] Pool set diff to 5000
[2016-08-28 04:30:23] Stratum detected new block
[2016-08-28 04:30:25] GPU #0: GeForce GTX 750 Ti, 135.18 H/s
[2016-08-28 04:30:34] Stratum detected new block
[2016-08-28 04:30:34] GPU #0: GeForce GTX 750 Ti, 274.45 H/s
[2016-08-28 04:31:06] GPU #0: GeForce GTX 750 Ti, 270.69 H/s
[2016-08-28 04:31:07] stratum_recv_line failed
[2016-08-28 04:31:07] Stratum connection interrupted
[2016-08-28 04:31:07] Stratum detected new block
[2016-08-28 04:31:08] GPU #0: GeForce GTX 750 Ti, 263.97 H/s
[2016-08-28 04:31:16] GPU #0: GeForce GTX 750 Ti, 234.16 H/s
[2016-08-28 04:31:17] stratum_recv_line failed
[2016-08-28 04:31:17] Stratum connection interrupted
[2016-08-28 04:31:17] Stratum detected new block
[2016-08-28 04:31:17] GPU #0: GeForce GTX 750 Ti, 263.53 H/s
[2016-08-28 04:31:39] Stratum detected new block
[2016-08-28 04:31:39] GPU #0: GeForce GTX 750 Ti, 274.54 H/s
[2016-08-28 04:31:41] GPU #0: GeForce GTX 750 Ti, 30.38 H/s
[2016-08-28 04:31:41] stratum_recv_line failed
[2016-08-28 04:31:41] Stratum connection interrupted
[2016-08-28 04:31:42] Stratum detected new block
[2016-08-28 04:31:42] GPU #0: GeForce GTX 750 Ti, 258.23 H/s

[JarBinks]

How about increasing the uptick price of nicehashbot in the update? at 0.0001 intervals it can NOT keep up with moving prices.
Also the 0.0001 downtick every 10minutes is just an insulting way to make sure after a price hike people keep paying the inflated prices. This is all fake and screwing tons of renters from nicehash/westhash.

Make all these price ticks (up and down) adjustable by the renter and you will have a MUCH better business..

You can change the way it behaves yourself in visual basic (pretty sure about this).  You dont need coding knowledge, just poke around and change some values here and there   I think its more fun and you'll get better results than waiting for nicehash to update it...

If I understand what is being talked about, then it cannot be changed in the code.
The amount an existing order can be decreased is a set amount, and time, from NH, you basically have no say in what the amount is. (Kinda like an easy button)
When you increase the price you can go to any amount but when decreasing you must step down one increment at a time.

Quote from NH site here: https://www.nicehash.com/index.jsp?p=faq#faqb6

You can also decrease price of your existing orders. To avoid manipulation, price decrease is only available within predefined price steps, can be applied only each 10 minutes and resets your position to the bottom of sub-list of same-priced orders. The predefined value of price decrease is displayed on Decrease price button. Of course, once you decrease price you can always later increase it without any limitation.

When I first started using NH I really didn't like this either but, now I am use to it. I guess they have wore me down.
Am I a lemming now?  What cliff?

[randayh]

Ξpool

Hello NiceHashers,

A new Nicehash Patch has been deployed. However, we would not recommend over 2GH per address at this time. It seems to be nice and steady at 1GH. You are welcome to try it out.

Thanks again,

http://epool.io
50% Fees donated to ETC Development Fund

[nicehash]

my gtx 750 ti not workin in cryptonight algo.
8-28 04:31:42] GPU #0: GeForce GTX 750 Ti, 258.23 H/s

Did you download our patched ccminer? See here: https://www.nicehash.com/index.jsp?p=news&id=99

Best regards,
NiceHash team.

[thedreamer]

If I understand what is being talked about, then it cannot be changed in the code.
The amount an existing order can be decreased is a set amount, and time, from NH, you basically have no say in what the amount is. (Kinda like an easy button)
When you increase the price you can go to any amount but when decreasing you must step down one increment at a time.

Quote from NH site here: https://www.nicehash.com/index.jsp?p=faq#faqb6

You can also decrease price of your existing orders. To avoid manipulation, price decrease is only available within predefined price steps, can be applied only each 10 minutes and resets your position to the bottom of sub-list of same-priced orders. The predefined value of price decrease is displayed on Decrease price button. Of course, once you decrease price you can always later increase it without any limitation.

When I first started using NH I really didn't like this either but, now I am use to it. I guess they have wore me down.
Am I a lemming now?  What cliff?

Funny how they say "...To avoid manipulation.....". This is exactly what they are doing though and what is going on. Someone pops in with a crazy high paying order, ups the prices by 20-30-40% or more for a short while. Then all the people using nicehashbot are stuck spending a ton more in BTC as it will take them hours or days to get back to normal levels (in which case the price manipulation happens again). I've seen this many times lately since nicehash's system 'update'.

So instead of combating it by allowing either a user-defined drop price amount, or increasing it to something more than the miniscule amount every 10 minutes, they limited it even more, screwing renters. It makes them earn a ton more in fees though.

I'm surprised anyone still uses them. MRR is much better even, although there you have to deal with renters who have no clue to hwo properly configure a pool.


Also, notice how nicehash never replies to actual concerns that MATTER on here?

[JarBinks]

If I understand what is being talked about, then it cannot be changed in the code.
The amount an existing order can be decreased is a set amount, and time, from NH, you basically have no say in what the amount is. (Kinda like an easy button)
When you increase the price you can go to any amount but when decreasing you must step down one increment at a time.

Quote from NH site here: https://www.nicehash.com/index.jsp?p=faq#faqb6

You can also decrease price of your existing orders. To avoid manipulation, price decrease is only available within predefined price steps, can be applied only each 10 minutes and resets your position to the bottom of sub-list of same-priced orders. The predefined value of price decrease is displayed on Decrease price button. Of course, once you decrease price you can always later increase it without any limitation.

When I first started using NH I really didn't like this either but, now I am use to it. I guess they have wore me down.
Am I a lemming now?  What cliff?

Funny how they say "...To avoid manipulation.....". This is exactly what they are doing though and what is going on. Someone pops in with a crazy high paying order, ups the prices by 20-30-40% or more for a short while. Then all the people using nicehashbot are stuck spending a ton more in BTC as it will take them hours or days to get back to normal levels (in which case the price manipulation happens again). I've seen this many times lately since nicehash's system 'update'.

So instead of combating it by allowing either a user-defined drop price amount, or increasing it to something more than the miniscule amount every 10 minutes, they limited it even more, screwing renters. It makes them earn a ton more in fees though.

I'm surprised anyone still uses them. MRR is much better even, although there you have to deal with renters who have no clue to hwo properly configure a pool.


Also, notice how nicehash never replies to actual concerns that MATTER on here?

I will agree that the system they use is skewed more toward providers than renters but without providers, renters are SOL.
You could always modify nicehashbot  to determine if it is worth it to cancel the order and submit a new one at the lower price.
I did something similar in my own code and it seems to mitigate some of the pain of price jumping.

I will say as a renter I wish I could change any order to be any price.
I will also say as a provider need some level of consistency in price.

[NiceHashSupport]

If I understand what is being talked about, then it cannot be changed in the code.
The amount an existing order can be decreased is a set amount, and time, from NH, you basically have no say in what the amount is. (Kinda like an easy button)
When you increase the price you can go to any amount but when decreasing you must step down one increment at a time.

Quote from NH site here: https://www.nicehash.com/index.jsp?p=faq#faqb6

You can also decrease price of your existing orders. To avoid manipulation, price decrease is only available within predefined price steps, can be applied only each 10 minutes and resets your position to the bottom of sub-list of same-priced orders. The predefined value of price decrease is displayed on Decrease price button. Of course, once you decrease price you can always later increase it without any limitation.

When I first started using NH I really didn't like this either but, now I am use to it. I guess they have wore me down.
Am I a lemming now?  What cliff?

Funny how they say "...To avoid manipulation.....". This is exactly what they are doing though and what is going on. Someone pops in with a crazy high paying order, ups the prices by 20-30-40% or more for a short while. Then all the people using nicehashbot are stuck spending a ton more in BTC as it will take them hours or days to get back to normal levels (in which case the price manipulation happens again). I've seen this many times lately since nicehash's system 'update'.

So instead of combating it by allowing either a user-defined drop price amount, or increasing it to something more than the miniscule amount every 10 minutes, they limited it even more, screwing renters. It makes them earn a ton more in fees though.

I'm surprised anyone still uses them. MRR is much better even, although there you have to deal with renters who have no clue to hwo properly configure a pool.


Also, notice how nicehash never replies to actual concerns that MATTER on here?

We explained several times already, why price dropping is not freely. Let me explain for you again;

Let's assume you mine SHA256.
If price drop was free, you could first set high enough price (1.5) to gather all miners (15 PH/s), then suddenly drop price to 0.0001. Since miners are being slowly reassigned to new orders by random time intervals, it would take several ten minutes before miners would be reassigned off your order to more profitable orders. Meanwhile, profit ratio for all SHA256 miners would drop near to 0.0001 and slowly rise up.

If we enabled free price drops, NiceHash would soon cease to exist, because all miners would rather mine elsewhere due to very low profitability on NiceHash.

Every rule we have there is for a good reason. We don't make rules just for fun or to annoy any party, but to prevent all kind of malicious activity that would either harm buyers or sellers.

[mo35]

Cryptonight with Claymore invalid bitcoin adress errors with config "GpuCNMiner.exe -o stratum+tcp://cryptonight.eu.nicehash.com:3355 -u btc-adress -p x" , goes on like following

08/29/16-21:22:48 - SHARE FOUND (target 10000) - (GPU 2 of 4)
21:22:48:288   d9c   got 63 bytes
21:22:48:288   d9c   buf: {"jsonrpc":"2.0","id":1,"error":null,"result":{"status":"OK"}}
21:22:48:288   d9c   parse packet: 63
21:22:48:288   d9c   Share accepted
21:22:48:288   d9c   new buf size: 0
21:22:48:663   7c0   GPU 3: HashCnt = 864, time = 1804 ms, hashrate = 478 h/s
21:22:48:694   7c0   Round
21:22:49:412   f04   GPU 0: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:49:412   da8   Stratum - Connected
21:22:49:427   f04   Round
21:22:49:443   ad0   GPU 1: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:49:458   f9c   GPU 2: HashCnt = 512, time = 1255 ms, hashrate = 407 h/s
21:22:49:458   ad0   Round
21:22:49:458   f9c   Round
21:22:49:490   da8   got 79 bytes
21:22:49:490   da8   buf: {"jsonrpc":"2.0","id":1,"error":{"code":24,"message":"Incorrect BTC address"}}
21:22:49:490   da8   parse packet: 77
21:22:49:490   da8   Error in server response : {"jsonrpc":"2.0","id":1,"error":{"code":24,"message":"IncorrectBTCaddress"}}
21:22:49:490   da8   buf was cleared
21:22:50:426   da4   GPU 3: HashCnt = 864, time = 1726 ms, hashrate = 500 h/s
21:22:50:457   da4   Round
21:22:50:691   5bc   GPU 0: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:50:706   5bc   Round
21:22:50:722   c80   GPU 1: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:50:738   c80   Round
21:22:50:753   e20   GPU 2: HashCnt = 512, time = 1255 ms, hashrate = 407 h/s
21:22:50:753   e20   Round
21:22:51:970   f04   GPU 0: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:51:986   f04   Round
21:22:52:017   ad0   GPU 1: HashCnt = 512, time = 1257 ms, hashrate = 407 h/s
21:22:52:017   ad0   round found 1 shares
21:22:52:017   ad0   Round
21:22:52:032   d9c   08/29/16-21:22:52 - SHARE FOUND (target 10000) - (GPU 1 of 4)
21:22:52:032   f9c   GPU 2: HashCnt = 512, time = 1255 ms, hashrate = 407 h/s
21:22:52:032   f9c   Round
21:22:52:126   d9c   got 63 bytes
21:22:52:126   d9c   buf: {"jsonrpc":"2.0","id":1,"error":null,"result":{"status":"OK"}}
21:22:52:126   d9c   parse packet: 63
21:22:52:126   d9c   Share accepted

[NiceHashSupport]

Cryptonight with Claymore invalid bitcoin adress errors with config "GpuCNMiner.exe -o stratum+tcp://cryptonight.eu.nicehash.com:3355 -u btc-adress -p x" , goes on like following

08/29/16-21:22:48 - SHARE FOUND (target 10000) - (GPU 2 of 4)
21:22:48:288   d9c   got 63 bytes
21:22:48:288   d9c   buf: {"jsonrpc":"2.0","id":1,"error":null,"result":{"status":"OK"}}
21:22:48:288   d9c   parse packet: 63
21:22:48:288   d9c   Share accepted
21:22:48:288   d9c   new buf size: 0
21:22:48:663   7c0   GPU 3: HashCnt = 864, time = 1804 ms, hashrate = 478 h/s
21:22:48:694   7c0   Round
21:22:49:412   f04   GPU 0: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:49:412   da8   Stratum - Connected
21:22:49:427   f04   Round
21:22:49:443   ad0   GPU 1: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:49:458   f9c   GPU 2: HashCnt = 512, time = 1255 ms, hashrate = 407 h/s
21:22:49:458   ad0   Round
21:22:49:458   f9c   Round
21:22:49:490   da8   got 79 bytes
21:22:49:490   da8   buf: {"jsonrpc":"2.0","id":1,"error":{"code":24,"message":"Incorrect BTC address"}}
21:22:49:490   da8   parse packet: 77
21:22:49:490   da8   Error in server response : {"jsonrpc":"2.0","id":1,"error":{"code":24,"message":"IncorrectBTCaddress"}}
21:22:49:490   da8   buf was cleared
21:22:50:426   da4   GPU 3: HashCnt = 864, time = 1726 ms, hashrate = 500 h/s
21:22:50:457   da4   Round
21:22:50:691   5bc   GPU 0: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:50:706   5bc   Round
21:22:50:722   c80   GPU 1: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:50:738   c80   Round
21:22:50:753   e20   GPU 2: HashCnt = 512, time = 1255 ms, hashrate = 407 h/s
21:22:50:753   e20   Round
21:22:51:970   f04   GPU 0: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:51:986   f04   Round
21:22:52:017   ad0   GPU 1: HashCnt = 512, time = 1257 ms, hashrate = 407 h/s
21:22:52:017   ad0   round found 1 shares
21:22:52:017   ad0   Round
21:22:52:032   d9c   08/29/16-21:22:52 - SHARE FOUND (target 10000) - (GPU 1 of 4)
21:22:52:032   f9c   GPU 2: HashCnt = 512, time = 1255 ms, hashrate = 407 h/s
21:22:52:032   f9c   Round
21:22:52:126   d9c   got 63 bytes
21:22:52:126   d9c   buf: {"jsonrpc":"2.0","id":1,"error":null,"result":{"status":"OK"}}
21:22:52:126   d9c   parse packet: 63
21:22:52:126   d9c   Share accepted

There are some changes needed in mining software to be compatible with NiceHash; check here for more details: https://github.com/nicehash/Specifications/blob/master/NiceHash_CryptoNight_modification_v1.0.txt

Also, we noticed that some mining software have a bug in submitting shares; sending '\r\n' which is not by the specs. This has to be fixed as well. Since claymore is closed source program, your best bet is to contact author regarding these issues.

[smilodon]

Cryptonight with Claymore invalid bitcoin adress errors with config "GpuCNMiner.exe -o stratum+tcp://cryptonight.eu.nicehash.com:3355 -u btc-adress -p x" , goes on like following

08/29/16-21:22:48 - SHARE FOUND (target 10000) - (GPU 2 of 4)
21:22:48:288   d9c   got 63 bytes
21:22:48:288   d9c   buf: {"jsonrpc":"2.0","id":1,"error":null,"result":{"status":"OK"}}
21:22:48:288   d9c   parse packet: 63
21:22:48:288   d9c   Share accepted
21:22:48:288   d9c   new buf size: 0
21:22:48:663   7c0   GPU 3: HashCnt = 864, time = 1804 ms, hashrate = 478 h/s
21:22:48:694   7c0   Round
21:22:49:412   f04   GPU 0: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:49:412   da8   Stratum - Connected
21:22:49:427   f04   Round
21:22:49:443   ad0   GPU 1: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:49:458   f9c   GPU 2: HashCnt = 512, time = 1255 ms, hashrate = 407 h/s
21:22:49:458   ad0   Round
21:22:49:458   f9c   Round
21:22:49:490   da8   got 79 bytes
21:22:49:490   da8   buf: {"jsonrpc":"2.0","id":1,"error":{"code":24,"message":"Incorrect BTC address"}}
21:22:49:490   da8   parse packet: 77
21:22:49:490   da8   Error in server response : {"jsonrpc":"2.0","id":1,"error":{"code":24,"message":"IncorrectBTCaddress"}}
21:22:49:490   da8   buf was cleared
21:22:50:426   da4   GPU 3: HashCnt = 864, time = 1726 ms, hashrate = 500 h/s
21:22:50:457   da4   Round
21:22:50:691   5bc   GPU 0: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:50:706   5bc   Round
21:22:50:722   c80   GPU 1: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:50:738   c80   Round
21:22:50:753   e20   GPU 2: HashCnt = 512, time = 1255 ms, hashrate = 407 h/s
21:22:50:753   e20   Round
21:22:51:970   f04   GPU 0: HashCnt = 512, time = 1258 ms, hashrate = 406 h/s
21:22:51:986   f04   Round
21:22:52:017   ad0   GPU 1: HashCnt = 512, time = 1257 ms, hashrate = 407 h/s
21:22:52:017   ad0   round found 1 shares
21:22:52:017   ad0   Round
21:22:52:032   d9c   08/29/16-21:22:52 - SHARE FOUND (target 10000) - (GPU 1 of 4)
21:22:52:032   f9c   GPU 2: HashCnt = 512, time = 1255 ms, hashrate = 407 h/s
21:22:52:032   f9c   Round
21:22:52:126   d9c   got 63 bytes
21:22:52:126   d9c   buf: {"jsonrpc":"2.0","id":1,"error":null,"result":{"status":"OK"}}
21:22:52:126   d9c   parse packet: 63
21:22:52:126   d9c   Share accepted

try syntax  NsGpuCNMiner.exe -nofee 1 -a 1 -u wallet -p x

[smilodon]

my gtx 750 ti not workin in cryptonight algo.
8-28 04:31:42] GPU #0: GeForce GTX 750 Ti, 258.23 H/s

Did you download our patched ccminer? See here: https://www.nicehash.com/index.jsp?p=news&id=99

Best regards,
NiceHash team.

I downloaded what you suggested and it still does not work. I tried different settings and again nothing.