CCminer(SP-MOD) Modded GPU kernels.

[pallas]

@_sp i'm not mining directly to you're adress atm, but will continue when the vtc/eth hype is over
at all devs, what you do for this community is mind blowing, so you definitely deserve a beer or two really appreciate it!

@ djm34:  .05 btc https://blockchain.info/en/tx/9a1522198e383355e5128a9c41eef8f4c3f40d35c61f234defa5ed81f3cc45bd
@ _sp:  .05 btc https://blockchain.info/en/tx/9a1522198e383355e5128a9c41eef8f4c3f40d35c61f234defa5ed81f3cc45bd
@ pallas:  .05 btc https://blockchain.info/en/tx/9a1522198e383355e5128a9c41eef8f4c3f40d35c61f234defa5ed81f3cc45bd

thank you guys again!

thanks very much! :-)
I see that nvidia miners don't want to end up like AMD with huge speed gap between public and private miners ;-)

[1714660520]

1714660520

[1714660520]

1714660520

[1714660520]

1714660520

[sambiohazard]

New ETH pool in alpha phase, if anyone is interested.

http://cryptomining-blog.com/5374-pooleum-a-new-ethereum-pool-in-pre-alpha-phase/

[Nubminer]

so I am trying to mine lyra2v2 at nicehash
ccminer is reporting
[2015-08-18 09:52:20] GPU #1: GeForce GTX 980, 11335
[2015-08-18 09:52:21] accepted: 171/171 (100.00%), 22814 kH/s yes!
[2015-08-18 09:52:27] GPU #1: GeForce GTX 980, 11394
[2015-08-18 09:52:27] accepted: 172/172 (100.00%), 22815 kH/s yes!
[2015-08-18 09:52:37] GPU #1: GeForce GTX 980, 11370
[2015-08-18 09:52:37] accepted: 173/173 (100.00%), 22813 kH/s yes!
[2015-08-18 09:52:39] GPU #1: GeForce GTX 980, 11428
[2015-08-18 09:52:39] accepted: 174/174 (100.00%), 22817 kH/s yes!

but Nicehash only credits me for

5 minute accepted speed MH/s   11.1850

is there anything I can do on my end to make these figures match.

I considered a different pool but then with pool fees, transfer fees and exchange fees it doesn't seem worth the trouble. (I am probably doing it wrong but such is life)

[scryptr]

so I am trying to mine lyra2v2 at nicehash
ccminer is reporting
[2015-08-18 09:52:20] GPU #1: GeForce GTX 980, 11335
[2015-08-18 09:52:21] accepted: 171/171 (100.00%), 22814 kH/s yes!
[2015-08-18 09:52:27] GPU #1: GeForce GTX 980, 11394
[2015-08-18 09:52:27] accepted: 172/172 (100.00%), 22815 kH/s yes!
[2015-08-18 09:52:37] GPU #1: GeForce GTX 980, 11370
[2015-08-18 09:52:37] accepted: 173/173 (100.00%), 22813 kH/s yes!
[2015-08-18 09:52:39] GPU #1: GeForce GTX 980, 11428
[2015-08-18 09:52:39] accepted: 174/174 (100.00%), 22817 kH/s yes!

but Nicehash only credits me for

5 minute accepted speed MH/s   11.1850

is there anything I can do on my end to make these figures match.

I considered a different pool but then with pool fees, transfer fees and exchange fees it doesn't seem worth the trouble. (I am probably doing it wrong but such is life)

DIFFICULTY MULTIPLIER--

Have you been reading in the thread?  The difficulty multiplier "--diff 2" or "--diff 0.5" may need to be set, depending on precisely which version of ccminer you are using.

Basicially, there is a hard-coded difficulty value in the ccminer code.  If that value does not match the value set in the POOL's code, then the MINER needs to adjust his ccminer with the proper "-diff" value for agreement with hashing values at the pool, and locally.       --scryptr

[Nubminer]

DIFFICULTY MULTIPLIER--

Have you been reading in the thread?  The difficulty multiplier "--diff 2" or "--diff 0.5" may need to be set, depending on precisely which version of ccminer you are using.

Basicially, there is a hard-coded difficulty value in the ccminer code.  If that value does not match the value set in the POOL's code, then the MINER needs to adjust his ccminer with the proper "-diff" value for agreement with hashing values at the pool, and locally.       --scryptr

I was under the impression that was fixed with rel_60  I must have gotten it confused with djm version sorry for getting so uptight..
sometimes this thead seems like its being hijacked and I am reading info for one ccminer and applying it to another. I seriously have dyslexia so it takes me some time to figure it out

[Nubminer]

well I adjusted it and now nicehash web frontend is down.. so I waits

[scryptr]

DIFFICULTY MULTIPLIER--

Have you been reading in the thread?  The difficulty multiplier "--diff 2" or "--diff 0.5" may need to be set, depending on precisely which version of ccminer you are using.

Basicially, there is a hard-coded difficulty value in the ccminer code.  If that value does not match the value set in the POOL's code, then the MINER needs to adjust his ccminer with the proper "-diff" value for agreement with hashing values at the pool, and locally.       --scryptr

I was under the impression that was fixed with rel_60  I must have gotten it confused with djm version sorry for getting so uptight..
sometimes this thead seems like its being hijacked and I am reading info for one ccminer and applying it to another. I seriously have dyslexia so it takes me some time to figure it out

SORRY--

Didn't mean to sound cruel.  I don't know which version will be which right now.  I mine with SP_ release dot 60, and not an incremental build.  I have to use "--diff 2" at NiceHash.  But, mining straight VTC is better value just now, so I mine at GMC.       --scryptr

[bensam1231]

@_sp i'm not mining directly to you're adress atm, but will continue when the vtc/eth hype is over
at all devs, what you do for this community is mind blowing, so you definitely deserve a beer or two really appreciate it!

@ djm34:  .05 btc https://blockchain.info/en/tx/9a1522198e383355e5128a9c41eef8f4c3f40d35c61f234defa5ed81f3cc45bd
@ _sp:  .05 btc https://blockchain.info/en/tx/9a1522198e383355e5128a9c41eef8f4c3f40d35c61f234defa5ed81f3cc45bd
@ pallas:  .05 btc https://blockchain.info/en/tx/9a1522198e383355e5128a9c41eef8f4c3f40d35c61f234defa5ed81f3cc45bd

thank you guys again!

thanks very much! :-)
I see that nvidia miners don't want to end up like AMD with huge speed gap between public and private miners ;-)

As a Ex AMD miner that is something I never want to experience again.

[flipclip]

DIFFICULTY MULTIPLIER--

Have you been reading in the thread?  The difficulty multiplier "--diff 2" or "--diff 0.5" may need to be set, depending on precisely which version of ccminer you are using.

Basicially, there is a hard-coded difficulty value in the ccminer code.  If that value does not match the value set in the POOL's code, then the MINER needs to adjust his ccminer with the proper "-diff" value for agreement with hashing values at the pool, and locally.       --scryptr

I was under the impression that was fixed with rel_60  I must have gotten it confused with djm version sorry for getting so uptight..
sometimes this thead seems like its being hijacked and I am reading info for one ccminer and applying it to another. I seriously have dyslexia so it takes me some time to figure it out

sp_ submitted the fix yesterday (https://github.com/sp-hash/ccminer/commit/377a6c8dd0ec7b72b4c91babbaf12da4b5ec28e4) so if you compile from an up-to-date git pull, you do not need to use --diff 2 when using nicehash.  If you are using release 60, you will need to use --diff 2 in the command line if mining on nicehash.
The thread can certainly get confusing (by the way you can't mine ETH with sp_'s ccminer, given that recent thread jacking  ).

[antonio8]

DIFFICULTY MULTIPLIER--

Have you been reading in the thread?  The difficulty multiplier "--diff 2" or "--diff 0.5" may need to be set, depending on precisely which version of ccminer you are using.

Basicially, there is a hard-coded difficulty value in the ccminer code.  If that value does not match the value set in the POOL's code, then the MINER needs to adjust his ccminer with the proper "-diff" value for agreement with hashing values at the pool, and locally.       --scryptr

I was under the impression that was fixed with rel_60  I must have gotten it confused with djm version sorry for getting so uptight..
sometimes this thead seems like its being hijacked and I am reading info for one ccminer and applying it to another. I seriously have dyslexia so it takes me some time to figure it out

sp_ submitted the fix yesterday (https://github.com/sp-hash/ccminer/commit/377a6c8dd0ec7b72b4c91babbaf12da4b5ec28e4) so if you compile from an up-to-date git pull, you do not need to use --diff 2 when using nicehash.  If you are using release 60, you will need to use --diff 2 in the command line if mining on nicehash.
The thread can certainly get confusing (by the way you can't mine ETH with sp_'s ccminer, given that recent thread jacking  ).

Don't think of it as thread jacking. Instead think of it as an exchange. The more people talk about a coin and show interest then the more likely an exchange might add it.

Maybe sp_ was unaware of that other coin. If enough people show interest in that also maybe a dev might show interest and pick it up.

I am pretty sure they don't spend all day scouring the forums for new things that are out.

[Nubminer]

Don't think of it as thread jacking. Instead think of it as an exchange. The more people talk about a coin and show interest then the more likely an exchange might add it.

Maybe sp_ was unaware of that other coin. If enough people show interest in that also maybe a dev might show interest and pick it up.

I am pretty sure they don't spend all day scouring the forums for new things that are out.

An Exchange... Sounds good to me.


I was not insinuating djm was hijacking because i am pretty sure he/she works well with sp to develop this..  I was just thinking out loud is all.

[djm34]

Don't think of it as thread jacking. Instead think of it as an exchange. The more people talk about a coin and show interest then the more likely an exchange might add it.

Maybe sp_ was unaware of that other coin. If enough people show interest in that also maybe a dev might show interest and pick it up.

I am pretty sure they don't spend all day scouring the forums for new things that are out.

An Exchange... Sounds good to me.


I was not insinuating djm was hijacking because i am pretty sure he/she works well with sp to develop this..  I was just thinking out loud is all.

he's not hijacking the thread, he is just transmitting the info from another thread (warp shuffle with vtc thread   )... so to make sure every releases use the same setting....

[hashbrown9000]

 i see quark algo payments have perked up a bit on nicehash. but for me, it has to be above 0.4 to be worth it to mine.

[tbearhere]

A cudaminer post from bigjme  account hacked ..now her name is bigjme-real

https://bitcointalk.org/index.php?topic=167229.msg12175879#msg12175879

It would be nice if bigjme could keep this going for all nvidia releases.

[scryptr]

A cudaminer post from bigjme  account hacked ..now her name is bigjme-real

https://bitcointalk.org/index.php?topic=167229.msg12175879#msg12175879

It would be nice if bigjme could keep this going for all nvidia releases.

ACCOUNT RECOVERED--

The mods were able to sort it out.  It is an interesting story, but she did say she quit crypto, though.  If you want anything from cudamining.co.uk, she is going to let the domain expire next August.  Some of the mining builds on the site are compatible with older GPU cards.       --scryptr

[sambiohazard]

Today's share sent

djm34: b9af5b27577edba9bfc628d120a46e9eb828f16e57597b6f05887f0f27a205cc
pallas: ce9134064c8e3b46ea63c972874bde5099eff262a289e71b62cda6417ec95b72
sp_: 220787012ecf4d2ed907ad059d37731c855e17a5ac3bc1ebf322b4e1f84a7f75

[sp_]

Today's share sent
djm34: b9af5b27577edba9bfc628d120a46e9eb828f16e57597b6f05887f0f27a205cc
pallas: ce9134064c8e3b46ea63c972874bde5099eff262a289e71b62cda6417ec95b72
sp_: 220787012ecf4d2ed907ad059d37731c855e17a5ac3bc1ebf322b4e1f84a7f75

Thanks.

[sp_]

Submitted a 200KHASH increase in the lyra2v2 on the gtx970. (2%)

No gain on the 750ti

[scryptr]

Submitted a 200KHASH increase in the lyra2v2 on the gtx970. (2%)

No gain on the 750ti

BUILD 927--

I built commit 927 on my GTX 970 rig and began mining with it.  I found that mining on GMC required a "--diff 0.5" setting.  The cards are not running faster yet, but it is too early to tell.       --scryptr

[flipclip]

Submitted a 200KHASH increase in the lyra2v2 on the gtx970. (2%)

No gain on the 750ti

BUILD 927--

I built commit 927 on my GTX 970 rig and began mining with it.  I found that mining on GMC required a "--diff 0.5" setting.  The cards are not running faster yet, but it is too early to tell.       --scryptr

Unfortunately...

sp, and all other mining developers, I suggest you to watch development of this: https://bitcointalk.org/index.php?topic=895020.msg12164065#msg12164065

There has to be a census reached about Lyra2REv2 diff multiplicator.

ok, here the new release, for this one you don't need to use "-diff 2" anymore: https://github.com/djm34/ccminer-lyra/releases/tag/v0.5
sp_ please update your release as well (as far as I know all the pool now use a difficulty of 256, in case one isn't using it --diff 0.5 will be necessary  )

edit: careful if you are using give-me-coin, they still use a difficulty of 128, you'll need to use diff of 0.5
would have been nice if yopu had search for a consensus among the pool, before posting that