CCminer(SP-MOD) Modded GPU kernels.

[badgoes]

hi @ everyone

at first i must say that this work from this coders is really nice 

i would spend a bear to sp_


But i have a question

i startet to solo mine Vertcoin after the fork and this is the output from ccminer sp mod v60

http://i59.tinypic.com/v7tbn9.jpg

i asked because the djm34 ccminer report the actual block number

thanks for answer

[sp_]

hi @ everyone
at first i must say that this work from this coders is really nice 
i would spend a bear to sp_
But i have a question
i startet to solo mine Vertcoin after the fork and this is the output from ccminer sp mod v60

i asked because the djm34 ccminer report the actual block number
thanks for answer

These changes where made in another branch, and is not yet merged down to mine. I might do a refork of tpruvot's ccminer 1.6.5 and replace all the kernals, but this is borring work and not on my priority list.

[Zels]

Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ?

[djm34]

Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ?

--diff 2 (and no it isn't a good idea to make it as default... for reasons explained on vtc thread...)
(this is a never ending story)

[badgoes]

when i solo mine against the wallet can i control the ccminer that is mining correctly?
or can i see that in the debug.log from wallet?

[bathrobehero]

Wti h

Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ?

--diff 2 (and no it isn't a good idea to make it as default... for reasons explained on vtc thread...)
(this is a never ending story)

Diff 2 explains perfectly why verters (and probably a couple of other pools) is so bad at finding blocks compared to the reported hashrate thrown at it. Verters is using diff 1 but accepts diff 2 shares as well while it shouldn't. Meaning that miners using -diff 2 have twice the reported hashrate and get paid twice as much at the expense of diff 1 miners.

Meanwhile I'd guess nicehash is both working with and require diff 2 by default to be in sync with ccminer.

So as usual, different pools use different configs and most of them doesn't understand the implications of their difficulty setting but change them anyway.

Which is why serious miners should always do some calculations based on nethashrate and difficulty to estimate how many coins they should be earning and compare that to what the different pools are paying. Or people could just always solomine to keep things simple.

[zTheWolfz]

Wti h

Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ?

--diff 2 (and no it isn't a good idea to make it as default... for reasons explained on vtc thread...)
(this is a never ending story)

Diff 2 explains perfectly why verters (and probably a couple of other pools) is so bad at finding blocks compared to the reported hashrate thrown at it. Verters is using diff 1 but accepts diff 2 shares as well while it shouldn't. Meaning that miners using -diff 2 have twice the reported hashrate and get paid twice as much at the expense of diff 1 miners.

Meanwhile I'd guess nicehash is both working with and require diff 2 by default to be in sync with ccminer.

So as usual, different pools use different configs and most of them doesn't understand the implications of their difficulty setting but change them anyway.

Which is why serious miners should always do some calculations based on nethashrate and difficulty to estimate how many coins they should be earning and compare that to what the different pools are paying. Or people could just always solomine to keep things simple.

Just tested --diff 2 at Nicehash lots of rejects but --diff 1 no rejects. What does this mean?

[zTheWolfz]

when i solo mine against the wallet can i control the ccminer that is mining correctly?
or can i see that in the debug.log from wallet?

Not sure how your mining but you can use the 2>>log.txt flag and it will make a log.txt in th folder where the ccminer.exe is
that file that can be opened with notepad to see the out put of the miner. This is not something I use at a pool, only when I solo mining.
This was just a test to see if it worked with ccminer and it does.

.

[djm34]

Wti h

Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ?

--diff 2 (and no it isn't a good idea to make it as default... for reasons explained on vtc thread...)
(this is a never ending story)

Diff 2 explains perfectly why verters (and probably a couple of other pools) is so bad at finding blocks compared to the reported hashrate thrown at it. Verters is using diff 1 but accepts diff 2 shares as well while it shouldn't. Meaning that miners using -diff 2 have twice the reported hashrate and get paid twice as much at the expense of diff 1 miners.

Meanwhile I'd guess nicehash is both working with and require diff 2 by default to be in sync with ccminer.

So as usual, different pools use different configs and most of them doesn't understand the implications of their difficulty setting but change them anyway.

Which is why serious miners should always do some calculations based on nethashrate and difficulty to estimate how many coins they should be earning and compare that to what the different pools are paying. Or people could just always solomine to keep things simple.

Just tested --diff 2 at Nicehash lots of rejects but --diff 1 no rejects. What does this mean?

it means you should use diff 1 (not much to tune on ccminer)

[zTheWolfz]

Wti h

Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ?

--diff 2 (and no it isn't a good idea to make it as default... for reasons explained on vtc thread...)
(this is a never ending story)

Diff 2 explains perfectly why verters (and probably a couple of other pools) is so bad at finding blocks compared to the reported hashrate thrown at it. Verters is using diff 1 but accepts diff 2 shares as well while it shouldn't. Meaning that miners using -diff 2 have twice the reported hashrate and get paid twice as much at the expense of diff 1 miners.

Meanwhile I'd guess nicehash is both working with and require diff 2 by default to be in sync with ccminer.

So as usual, different pools use different configs and most of them doesn't understand the implications of their difficulty setting but change them anyway.

Which is why serious miners should always do some calculations based on nethashrate and difficulty to estimate how many coins they should be earning and compare that to what the different pools are paying. Or people could just always solomine to keep things simple.

Just tested --diff 2 at Nicehash lots of rejects but --diff 1 no rejects. What does this mean?

it means you should use diff 1 (not much to tune on ccminer)

Gotcha I had also been wondering why my hash rate showed one thing in the miner and much lower at the pool.
I don't or hadn't been using the -diff flag, actually using it seems to lower my hash rate shown in the miner software.
So I removed it. Was more or less just a test anyways.

[djm34]

Wti h

Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ?

--diff 2 (and no it isn't a good idea to make it as default... for reasons explained on vtc thread...)
(this is a never ending story)

Diff 2 explains perfectly why verters (and probably a couple of other pools) is so bad at finding blocks compared to the reported hashrate thrown at it. Verters is using diff 1 but accepts diff 2 shares as well while it shouldn't. Meaning that miners using -diff 2 have twice the reported hashrate and get paid twice as much at the expense of diff 1 miners.

the problem with verters is that if you use diff 1, the pool reports only half of the hashrate of the miner. So something is badly wrong in his setting... (could be the hashrate report as well....)

[djm34]

Wti h

Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ?

--diff 2 (and no it isn't a good idea to make it as default... for reasons explained on vtc thread...)
(this is a never ending story)

Diff 2 explains perfectly why verters (and probably a couple of other pools) is so bad at finding blocks compared to the reported hashrate thrown at it. Verters is using diff 1 but accepts diff 2 shares as well while it shouldn't. Meaning that miners using -diff 2 have twice the reported hashrate and get paid twice as much at the expense of diff 1 miners.

Meanwhile I'd guess nicehash is both working with and require diff 2 by default to be in sync with ccminer.

So as usual, different pools use different configs and most of them doesn't understand the implications of their difficulty setting but change them anyway.

Which is why serious miners should always do some calculations based on nethashrate and difficulty to estimate how many coins they should be earning and compare that to what the different pools are paying. Or people could just always solomine to keep things simple.

Just tested --diff 2 at Nicehash lots of rejects but --diff 1 no rejects. What does this mean?

it means you should use diff 1 (not much to tune on ccminer)

Gotcha I had also been wondering why my hash rate showed one thing in the miner and much lower at the pool.
I don't or hadn't been using the -diff flag, actually using it seems to lower my hash rate shown in the miner software.
So I removed it. Was more or less just a test anyways.

--diff 1 is the default, so it isn't necessary to keep it on the command line
but you need to check what hashrate you get, and if it is smaller by a factor 2 report to them

[zTheWolfz]

Wti h

Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ?

--diff 2 (and no it isn't a good idea to make it as default... for reasons explained on vtc thread...)
(this is a never ending story)

Diff 2 explains perfectly why verters (and probably a couple of other pools) is so bad at finding blocks compared to the reported hashrate thrown at it. Verters is using diff 1 but accepts diff 2 shares as well while it shouldn't. Meaning that miners using -diff 2 have twice the reported hashrate and get paid twice as much at the expense of diff 1 miners.

Meanwhile I'd guess nicehash is both working with and require diff 2 by default to be in sync with ccminer.

So as usual, different pools use different configs and most of them doesn't understand the implications of their difficulty setting but change them anyway.

Which is why serious miners should always do some calculations based on nethashrate and difficulty to estimate how many coins they should be earning and compare that to what the different pools are paying. Or people could just always solomine to keep things simple.

Just tested --diff 2 at Nicehash lots of rejects but --diff 1 no rejects. What does this mean?

it means you should use diff 1 (not much to tune on ccminer)

Gotcha I had also been wondering why my hash rate showed one thing in the miner and much lower at the pool.
I don't or hadn't been using the -diff flag, actually using it seems to lower my hash rate shown in the miner software.
So I removed it. Was more or less just a test anyways.

--diff 1 is the default, so it isn't necessary to keep it on the command line
but you need to check what hashrate you get, and if it is smaller by a factor 2 report to them

Well I must say I'm not the sharpest tack in the box lol and do not quite understand much of this hash readings vs the miner vs the pool
with nicehash. what I see there is this:
Speed accepted      
7.0990    0.0000 (0.00%)    0.02000000    8       
     

what the miner shows me is this:
  accepted: 160/160 (100.00%), 10103 khash/s yay!!!
  accepted: 161/161 (100.00%), 10109 khash/s yay!!!

Edit: now it showing this: 10.8020 at nicehash, this jumps around quite a bit from time to time.
Miner stays about the same most of the time give or take +10 -10

My AMD cards and sgminer are even more confusing lol
sgminer showing 1.55Mh/s per card w/ 2x AMD 270 non x cards nicehash showing  3.5210

[bensam1231]

I used Verters back when VTC was scryptn and switched from them. Pretty sure they skim coins. A lot of pools skim coins, but since most hashing has switched to multipool and nicehash, it's much harder to tell now days when people are doing this. Fees can be whatever they want, they don't need to tell you.

Is anyone having problems with the wallet at Cryptsy? The VTC wallet has been in maintenance mode for the last two days.

I believe coinfinders is one of the good guy, however it would be easy to spot if verters was skimming blocks (easy to check what goes to the pool wallet and compare with blocks reported on the front end

cryptsy has been in this state since the fork (but apparently vtc market is active...)

Yeah, it would... but do you do this? Especially over a 24hr period? Does anyone do this? I haven't heard of a site or program that checks the legitimacy of pools or compares them.

It's a lot of work, that's why no one does it and it's easy to get away with. It's also possible to trick such a system, it assumes you know the address for finding blocks. It's possible for a pool to mine from more then one address.

I wouldn't worry about small anomalies over a short period - it's quite easy to skim low amounts constantly from a pool you operate and have no sign of it occurring, really...

I wasn't talking about small amounts... Verters pays you like 10-20% less then you're supposed to receive (this is by the pool estimate and other sites). You can compare it to other pools as well. This sort of thing wasn't that uncommon a year ago when personal pools were a big deal.


Lots of trading happening at Cryptsy too, even though you can't send coins in or out.

[chrysophylax]

hi all ...

ive been quite ill for the last week and am still not very stable health wise - but enough to get some things done then back to bed ...

so ill continue to pop in and out of here - to try and keep up to date with what is happening ... and a LOT has happened in the last week ...

i have compiled the latest ccminer-spmod v60 - and set the miners running on the lyra2rev2 ... initailly on verters for a few hours - and now on nicehash ...

a few things popped out which seem to be issues ...

- hashrates are NEVER correct ... even after a few hours - --diff changes and paramters ... miners are showing more than 10 times the pool hashrates ...
- not all exchanges have caught on - and i guess they will soon enough ...
- the latest ccminer ( compiled earlier today ) have had some changes which are nice and some which are questionable ...

the yay! has been changed to a yes! ... yay for that - or not ...

but when the miner cannot connect to the pool - the message is far from standard ... a copy below ...

-------

*** ccminer 1.5.60-git(SP-MOD) for nVidia GPUs by sp-hash@github ***
        Built with the nVidia CUDA SDK 6.5

  Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
   CUDA support by Christian Buchner, Christian H. and DJM34
  Includes optimizations implemented by sp , klaust, tpruvot and tsiv.

[2015-08-13 13:12:03] Intensity set to 19.0, 524288 cuda threads
[2015-08-13 13:12:04] Starting Stratum on stratum+tcp://mining-ace.granitecoin.com:6001/
[2015-08-13 13:12:04] NVML GPU monitoring enabled.
[2015-08-13 13:12:04] Binding thread 1 to cpu 1 (mask 2)
1
[2015-08-13 13:12:04] Binding thread 3 to cpu 3 (mask
3
[2015-08-13 13:12:04] Binding thread 0 to cpu 0 (mask 1)
0
[2015-08-13 13:12:04] Binding thread 2 to cpu 2 (mask 4)
2
[2015-08-13 13:12:04] 5 miner threads started, using 'lyra2v2' algorithm.
[2015-08-13 13:12:04] Binding thread 4 to cpu 0 (mask 10)
[2015-08-13 13:12:04] Stratum difficulty set to 4
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] mining-ace.granitecoin.com:6001/ lyra2v2 block 348786
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck


-------

since when does 'pool fuck' denote a disconnection or issue with the pool? ...

for the private miner - thats one thing ... maybe even funny ...

but for a miner like us that show our machines to prospective investors or buyers - this is a little less tasteful ...

sp - is this part of ccminer now? ... or have i magically done something here in the compile that i didnt know about? ...

can that be removed please? ...

far be it of me to a prude - im no such thing - but to have that within the miner itself? ... <shrugs> ...

anyway - apart from that - x11 and quark have improved and are getting good hashrates ...

as i muster the strength to get things sorted and catch up with everything ive missed in the times that im up - the donation servers will be functional in the coming days ( as i could not work on them all week ) and we will be shooting some donation mining after that ...

tanx sp ...

#crysx

[sp_]

- hashrates are NEVER correct ... even after a few hours - --diff changes and paramters ... miners are showing more than 10 times the pool hashrates ...
- not all exchanges have caught on - and i guess they will soon enough ...
- the latest ccminer ( compiled earlier today ) have had some changes which are nice and some which are questionable ...

the yay! has been changed to a yes! ... yay for that - or not ...

but when the miner cannot connect to the pool - the message is far from standard ... a copy below ...

[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck

I submitted some debug output. not on purpose. I was getting half the hashrate on p2pool.pl so I changed the difficulty multiplier to 2 as default (hardcoded into the miner) The pool fuck comment. (fuck the currupt pools). has now been removed
and get a full hashrate displayed on the pool. I have now reverted it, because Nicehash doesn't work.

If you build between releases, you might get some bugs in your miner. When I flag a release number, it meens that the code is safe to buid,

for full hashrate on p2pool.pl use the --diff 2 parameter

[chrysophylax]

- hashrates are NEVER correct ... even after a few hours - --diff changes and paramters ... miners are showing more than 10 times the pool hashrates ...
- not all exchanges have caught on - and i guess they will soon enough ...
- the latest ccminer ( compiled earlier today ) have had some changes which are nice and some which are questionable ...

the yay! has been changed to a yes! ... yay for that - or not ...

but when the miner cannot connect to the pool - the message is far from standard ... a copy below ...

[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck
[2015-08-13 13:12:05] stratum_gen_work: pool fuck

I submitted some debug output. not on purpose. I was getting half the hashrate on p2pool.pl so I changed the difficulty multiplier to 2 as default (hardcoded into the miner) The pool fuck comment. (fuck the currupt pools). has now been removed
and get a full hashrate displayed on the pool. I have now reverted it, because Nicehash doesn't work.

If you build between releases, you might get some bugs in your miner. When I flag a release number, it meens that the code is safe to buid,

for full hashrate on p2pool.pl use the --diff 2 parameter

tanx sp ...

i totally agree with you when it comes to pools ripping the miner off ...

i just thought i would bring that part to your attention ...

i have just received word from yaamp that he is no longer able to build our multipool now - as he is so involved with the new projects he has his interest in ...

so we are now looking for someone that can do that for us - and with us ... if there is anyone interested - please pm me ... im happy to work with whoever is interested - in many many ways ... and there are a few prerequisites for our pool - as i have a few ideas that i would like to see implemented within the pool itself ... yaamp could do this - but as said earlier - is too busy with other projects ...

we want to build a fair and equitable multipool ( which was one of the backend projects i have on ) which the community can trust ... so im open to suggestion with whoever would like to work with me ...

as for lyra2rev2 - ive pulled the miners off mining that algo for now ... at least until i get a lot better than what i am now - so i can trouble shoot and 'play' with the miners ... at the moment - i just get up occasionally and check in here for a few minutes - then get back to bed ...

ill test your suggestion with p2pool.pl and the --diff 2 parameter a little later today ...

ive started working on the donation servers again ... if i keep going at this pace - they will be active by the weeks end ...

tanx again sp ...

#crysx

[sp_]

I have tested p2pool.pl. It took many hours to reach the correct hashrate, and payouts are small. The miner pool is changing the difficulty all the time and it leads to lost hashes. reject rate is pretty high.. I think solomining is the best option here.
predicted payout 1 750ti:
$1.43 per day for one 750ti @ 4.3 MHASH
actual payout: (8 hours mining (24h payout is estimated)

$0.3 per day

After 30 hours of mining I've got around 16($0.96) Vertcoins a day per 750ti (recalculated to 24h average))   (p2pool.pl with --diff 2

Nicehash is currently paying around $0.41 per 750ti per day.

So someone is renting your hashrate and make money...

Note that the difficulty has raised from around 230 to 282 (+10.9%) in 24 hours and the next payouts will be smaller.


Results 1 rig (6x750ti)

[sp_]

Another interesting thing. The global hashrate of lyra has dropped with the new algo and the botnets gone:


The new GPU miner is 600% faster than the old one... (on the 750ti)

[sp_]

as for lyra2rev2 - ive pulled the miners off mining that algo for now ... at least until i get a lot better than what i am now - so i can trouble shoot and 'play' with the miners ... at the moment - i just get up occasionally and check in here for a few minutes

Nicehash is currently only displaying half the reported hashrate in the miner when I run with default difficulty(as in the official djm34 release). If you change the diff, no accepted shares...

This meens that nicehash is only paying 25% of what you get on p2pool.pl and --diff 2 (sp-mod release 60) or when solomining...