Pages:
Author

Topic: [ANN] Stratum support for scrypt mining has been added for cgminer/reaper (Read 5075 times)

legendary
Activity: 1484
Merit: 1005
http://mining.bitcoin.cz/stratum-mining

It's a new low bandwidth network implementation for mining.  It also reduces stales as it takes way less time for work to be sent to mining nodes.  One of the problems with the litecoin network over the old JSON protocol is the time it takes to send new work to mining clients when a new block is found.  The protocol was designed to facilitate high throughput mining operations on the bitcoin network but works well for the litecoin network too.
legendary
Activity: 1820
Merit: 1001
Updated cgminer and tested it successfully mining on the only stratum ltc pool:
https://bitcointalksearch.org/topic/m.1419834
(lots of other new scrypt goodies in this release too).



2.10.3 working fine on here and what is statum anyway care to alterable on this more ?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Updated cgminer and tested it successfully mining on the only stratum ltc pool:
https://bitcointalksearch.org/topic/m.1419834
(lots of other new scrypt goodies in this release too).

legendary
Activity: 3108
Merit: 1359
high stales
It's not a stales. It's just an invalid shares. Roll Eyes
legendary
Activity: 1484
Merit: 1005
Updating the mining guide with more information on how to run stratum correctly with ltcmine.ru

if you are getting high stales make sure you are using the mining proxy!
legendary
Activity: 976
Merit: 1003
Yes that makes sense thanks. I shall fix it.
Using cgminer 2.10.2 with fix on ltcmine.ru, work stable, but:
I haven't posted a release with the fixes yet so not sure what you're using. Only one part of the fix has even made it into git. Other changes need to follow.
I mean that fix. Waiting for new release.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Yes that makes sense thanks. I shall fix it.
Using cgminer 2.10.2 with fix on ltcmine.ru, work stable, but:
I haven't posted a release with the fixes yet so not sure what you're using. Only one part of the fix has even made it into git. Other changes need to follow.
legendary
Activity: 976
Merit: 1003
Yes that makes sense thanks. I shall fix it.
Using cgminer 2.10.2 with fix on ltcmine.ru, work stable, but:
What is it?
Code:
 [2012-12-22 22:44:09] Accepted a911f93f Diff 1/24 GPU 0
 [2012-12-22 22:44:12] Accepted cfd9062f Diff 1/24 GPU 0
 [2012-12-22 22:44:16] Accepted d3ceed4f Diff 1/24 GPU 0
 [2012-12-22 22:44:33] Accepted b5941bf1 Diff 1/65 GPU 0
 [2012-12-22 22:44:45] Accepted b6b60279 Diff 1/65 GPU 0
 [2012-12-22 22:44:59] Accepted 64c15c24 Diff 2/65 GPU 0
 [2012-12-22 22:45:15] Accepted c6d03f24 Diff 1/65 GPU 0
 [2012-12-22 22:45:23] Accepted 55554a31 Diff 2/65 GPU 0
 [2012-12-22 22:45:28] Accepted a686d6ba Diff 1/65 GPU 0
 [2012-12-22 22:45:48] Accepted 6af3a579 Diff 2/65 GPU 0
&&
Code:
 [2012-12-22 18:42:09] Rejected 522c6400 Diff 3/49 GPU 0  (high-hash) 
 [2012-12-22 18:43:16] Rejected 74a2881b Diff 2/35 GPU 0  (non-hexadecimal number found
 [2012-12-22 18:47:12] Rejected 4c821275 Diff 3/48 GPU 0  (non-hexadecimal number found
 [2012-12-22 18:48:22] Rejected bb7fc4ba Diff 1/55 GPU 0  (non-hexadecimal number found
 [2012-12-22 18:49:51] Rejected d912b0f4 Diff 1/55 GPU 0  (high-hash)
 [2012-12-22 19:01:08] Rejected 1f5840db Diff 8/32 GPU 0  (non-hexadecimal number found
 [2012-12-22 19:02:10] Rejected d271655c Diff 1/64 GPU 0  (non-hexadecimal number found
 [2012-12-22 19:10:20] Rejected f98d9a24 Diff 1/38 GPU 0  (non-hexadecimal number found
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Tested cgminer 2.10.2, and it's doesn't work.
Care to explain why cgminer natively doesn't work? Is the problem in cgminer or the pool's stratum implementation?
I think that cgminer uses 0x00000000ffff0000000000000000000000000000000000000000000000000000 as the maximum target for LTC (instead of 0x0000ffff00000000000000000000000000000000000000000000000000000000) while current target calculation, but it's only my guess. If I'm right, then it's actually working, but sets unreally hard difficulty for shares... And as a result,  miner can't solve it.
Yes that makes sense thanks. I shall fix it.
sr. member
Activity: 288
Merit: 250
Unfortunately, I can't check this patch on my current machine, because it have no opencl support and cgminer can't mine scrypt on CPU.  Sad
Exactly my problem hehe
legendary
Activity: 3108
Merit: 1359
Unfortunately, I can't check this patch on my current machine, because it have no opencl support and cgminer can't mine scrypt on CPU.  Sad
sr. member
Activity: 288
Merit: 250
Tested cgminer 2.10.2, and it's doesn't work.
Care to explain why cgminer natively doesn't work? Is the problem in cgminer or the pool's stratum implementation?
I think that cgminer uses 0x00000000ffff0000000000000000000000000000000000000000000000000000 as the maximum target for LTC (instead of 0x0000ffff00000000000000000000000000000000000000000000000000000000) while current target calculation, but it's only my guess. If I'm right, then it's actually working, but sets unreally hard difficulty for shares... And as a result,  miner can't solve it.
Yep, here's my patch.
http://pastie.org/private/b5jve8ebgynaidu3yv22a
replace set_work_target in cgminer.c with that one, if someone could post a windows build with that it would be nice since I've only compiled this on linux and I have no AMD cards anymore.

It generates 0000000000000000000000000000000000000000000000f0ff0f000000000000 for diff-16 Shocked
Weird, i don't see the problem though
legendary
Activity: 3108
Merit: 1359
del

// checking in progress  Roll Eyes
sr. member
Activity: 288
Merit: 250
Tested cgminer 2.10.2, and it's doesn't work.
Care to explain why cgminer natively doesn't work? Is the problem in cgminer or the pool's stratum implementation?
I think that cgminer uses 0x00000000ffff0000000000000000000000000000000000000000000000000000 as the maximum target for LTC (instead of 0x0000ffff00000000000000000000000000000000000000000000000000000000) while current target calculation, but it's only my guess. If I'm right, then it's actually working, but sets unreally hard difficulty for shares... And as a result,  miner can't solve it.
Yep, here's my patch.
http://pastie.org/private/b5jve8ebgynaidu3yv22a
replace set_work_target in cgminer.c with that one, if someone could post a windows build with that it would be nice since I've only compiled this on linux and I have no AMD cards anymore.
legendary
Activity: 3108
Merit: 1359
Tested cgminer 2.10.2, and it's doesn't work.
Care to explain why cgminer natively doesn't work? Is the problem in cgminer or the pool's stratum implementation?
I think that cgminer uses 0x00000000ffff0000000000000000000000000000000000000000000000000000 as the maximum target for LTC (instead of 0x0000ffff00000000000000000000000000000000000000000000000000000000) while current target calculation, but it's only my guess. If I'm right, then it's actually working, but sets unreally hard difficulty for shares... And as a result,  miner can't solve it.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Tested cgminer 2.10.2, and it's doesn't work.
Care to explain why cgminer natively doesn't work? Is the problem in cgminer or the pool's stratum implementation?
legendary
Activity: 3108
Merit: 1359
Tested cgminer 2.10.2, and it's doesn't work. So, our mining-proxy is the only way to mine through stratum/ltc, for now.

P.S. I've planned some changes in LTC version of stratum protocol, to make it more correct and clear (in terms of difficulty, for example).
legendary
Activity: 3108
Merit: 1359
No, we are not using poolserverj for ltc pool.

Don't know about cgminer, but our stratum-mining-proxy fork works fine.

There is a mistake in first post, our reaper fork doesn't support stratum for now, and i recommend to use it in combination with our proxy. But it's planned to implement native support.
legendary
Activity: 1484
Merit: 1005
Isn't poolserverj the backend for ltcmine.ru?  Unless I'm mistaken
sr. member
Activity: 288
Merit: 250
What ? As far as I know, the official poolserverj has no stratum support and scrypt support is still broken.
Pages:
Jump to: