Author

Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 1002. (Read 2347601 times)

full member
Activity: 231
Merit: 150
Wti h
Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ? Smiley
--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
legendary
Activity: 1400
Merit: 1050
Wti h
Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ? Smiley
--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
legendary
Activity: 1400
Merit: 1050
Wti h
Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ? Smiley
--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....)
full member
Activity: 231
Merit: 150
Wti h
Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ? Smiley
--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.
legendary
Activity: 1400
Merit: 1050
Wti h
Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ? Smiley
--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)
full member
Activity: 231
Merit: 150
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.

.
full member
Activity: 231
Merit: 150
Wti h
Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ? Smiley
--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?
legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
Wti h
Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ? Smiley
--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.
newbie
Activity: 29
Merit: 0
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?

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

Who's correct ? Smiley
--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)
full member
Activity: 203
Merit: 100
Lyra2rev2:
750ti:  4750kh/s reported by ccminer rlz60
But only 2500 - 2700 reported by nicehash after some hours

Who's correct ? Smiley
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
hi @ everyone
at first i must say that this work from this coders is really nice  Wink Wink
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.
newbie
Activity: 29
Merit: 0
hi @ everyone

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

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
legendary
Activity: 1764
Merit: 1024
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.
legendary
Activity: 1797
Merit: 1028
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.

BITTREX and VTC--

Bittrex moved the VTC wallets back into active status yesterday.  I was able to move some coins.

Sorry, don't know about Cryptsy, not my favorite.  I did upgrade my VTC-qt wallet; just dropped the new v10.0 binary into the program folder after renaming the v9.x binary to "vertcoin-qt.old".  Then I double clicked, it ran, and updated the blockchain in about an hour or so.       --scryptr
sr. member
Activity: 365
Merit: 250
?
Lyra2v2--

Currently, it is not the best paying algo by far.  Better to stack VTC and take them to market when they have fattened.  Around the begining of June they were trading at .002 BTC each, I was able to sell a few.  VTC is about .0002 BTC today.

I always keep my lame rig on VTC, the algo is low-energy and easy on GPUs.

I am glad that NiceHash added the algo, I thought that they were going to ignore Lyra2v2.       --scryptr
I didn't even notice it's rise to 0.002 (I thought it was upto 0.0014)
legendary
Activity: 1400
Merit: 1050
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...)
legendary
Activity: 1797
Merit: 1028
Verters are not particularily lucky or well set up because they need 160.24% shares on average for the last 24 hours to solve blocks (can be seen on "blocks" page).

On the other hand, nicehash added Lyra2Rev2 which should pay well.

Lyra2v2--

Currently, it is not the best paying algo by far.  Better to stack VTC and take them to market when they have fattened.  Around the begining of June they were trading at .002 BTC each, I was able to sell a few.  VTC is about .0002 BTC today.

I always keep my lame rig on VTC, the algo is low-energy and easy on GPUs.

I am glad that NiceHash added the algo, I thought that they were going to ignore Lyra2v2.       --scryptr
sr. member
Activity: 365
Merit: 250
?
VTC diff may rise to over 300 today.  Cheesy
More people move their miners to VTC and this may also increase the avg pay-rate of other coins.
legendary
Activity: 1764
Merit: 1024
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.
Jump to: