[ANN][CACH] CACHeCoin released based on scrypt-jane

[bit_coin_genuis]

Can someoneplease explain why this keeps happening to me and how to fix it ....

When I mine after while some of my miners report they are going speeds in GH/s which is obviously impossible ... I don't know if this as affecting my mining bit I would like it to stop ... also this was the first time I got HW errors ....

See image to see what i mean.. the top 2 are reporting speeds in GH/s.

http://imgur.com/5eUjbX6

GPU 0:  Gigabyte r9 290 OC (windforce)
GPU 1: Sapphire Tri-x r9 290
GPU 2: Sapphire Tri-x r9 290
GPU 3:  Sapphire Tri-x r9 290


HEre is my PC info:

http://imgur.com/8B3AQ9n

This is my config file content:


{
"pools" : [
   {
      "name" : "qhor P2P",
      "url" : "http://q30.qhor.net:8336",
      "user" : "CZVP8n6MhNigMn7adbF8e8zqCC3fgQFEZR",
      "pass" : "xx",
      "pool-priority" : "0"
   },
   {
      "name" : "CaCHE p2cache.syware.de P2P",
      "url" : "http://p2cache.syware.de:8336",
      "user" : "CZVP8n6MhNigMn7adbF8e8zqCC3fgQFEZR",
      "pass" : "xx",
      "pool-priority" : "1"
   },
   {
      "name" : "p2p-miner.info(0)",
      "url" : "http://p2pool-miner.info:8336",
      "user" : "CZVP8n6MhNigMn7adbF8e8zqCC3fgQFEZR",
      "pass" : "xx",
      "pool-priority" : "2"
   }
],
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"failover-only" : true,
"fix-protocol" : true,
"kernel-path" : "/usr/local/bin",
"no-submit-stale" : true,
"queue" : "0",
"gpu-threads" : "1",
"gpu-engine" : "1040,1000,1000,1000",
"gpu-fan" : "70",
"gpu-platform" : "0",
"gpu-memclock" : "1500",
"gpu-powertune" : "20",
"intensity" : "20",
"temp-target" : "85",
"temp-overheat" : "92",
"temp-cutoff" : "94",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "2",
"shaders" : "0",
"thread-concurrency" : "30592",
"scrypt-jane" : true,
"sj-Nfmin" : "4",
"sj-Nfmax" : "30",
"sj-time" : "1388949883"
}


Thanks in advance for help!

Is this seriously not happening to anyone else ?  It keeps happening to me more often.. Basically the GPU is useless once this happens and does not submit any shares.. I keep having to reboot every 45 minutes this is really annoying.  Any help would be appreciated.

cheers,

[Walrusbonzo]

Can someoneplease explain why this keeps happening to me and how to fix it ....

When I mine after while some of my miners report they are going speeds in GH/s which is obviously impossible ... I don't know if this as affecting my mining bit I would like it to stop ... also this was the first time I got HW errors ....

See image to see what i mean.. the top 2 are reporting speeds in GH/s.

http://imgur.com/5eUjbX6

GPU 0:  Gigabyte r9 290 OC (windforce)
GPU 1: Sapphire Tri-x r9 290
GPU 2: Sapphire Tri-x r9 290
GPU 3:  Sapphire Tri-x r9 290


HEre is my PC info:

http://imgur.com/8B3AQ9n

This is my config file content:


{
"pools" : [
   {
      "name" : "qhor P2P",
      "url" : "http://q30.qhor.net:8336",
      "user" : "CZVP8n6MhNigMn7adbF8e8zqCC3fgQFEZR",
      "pass" : "xx",
      "pool-priority" : "0"
   },
   {
      "name" : "CaCHE p2cache.syware.de P2P",
      "url" : "http://p2cache.syware.de:8336",
      "user" : "CZVP8n6MhNigMn7adbF8e8zqCC3fgQFEZR",
      "pass" : "xx",
      "pool-priority" : "1"
   },
   {
      "name" : "p2p-miner.info(0)",
      "url" : "http://p2pool-miner.info:8336",
      "user" : "CZVP8n6MhNigMn7adbF8e8zqCC3fgQFEZR",
      "pass" : "xx",
      "pool-priority" : "2"
   }
],
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"failover-only" : true,
"fix-protocol" : true,
"kernel-path" : "/usr/local/bin",
"no-submit-stale" : true,
"queue" : "0",
"gpu-threads" : "1",
"gpu-engine" : "1040,1000,1000,1000",
"gpu-fan" : "70",
"gpu-platform" : "0",
"gpu-memclock" : "1500",
"gpu-powertune" : "20",
"intensity" : "20",
"temp-target" : "85",
"temp-overheat" : "92",
"temp-cutoff" : "94",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "2",
"shaders" : "0",
"thread-concurrency" : "30592",
"scrypt-jane" : true,
"sj-Nfmin" : "4",
"sj-Nfmax" : "30",
"sj-time" : "1388949883"
}


Thanks in advance for help!

Is this seriously not happening to anyone else ?  It keeps happening to me more often.. Basically the GPU is useless once this happens and does not submit any shares.. I keep having to reboot every 45 minutes this is really annoying.  Any help would be appreciated.

cheers,

For me, occasionally if a GPU crashes it will start reporting incorrectly GH/s. I'd suggest turning down your GPU clocks, or increasing the GPU voltage or increasing GPU cooling or maybe even two or all of them things.

[Sukarti]

Can someoneplease explain why this keeps happening to me and how to fix it ....

When I mine after while some of my miners report they are going speeds in GH/s which is obviously impossible ... I don't know if this as affecting my mining bit I would like it to stop ... also this was the first time I got HW errors ....

See image to see what i mean.. the top 2 are reporting speeds in GH/s.

http://imgur.com/5eUjbX6

GPU 0:  Gigabyte r9 290 OC (windforce)
GPU 1: Sapphire Tri-x r9 290
GPU 2: Sapphire Tri-x r9 290
GPU 3:  Sapphire Tri-x r9 290


HEre is my PC info:

http://imgur.com/8B3AQ9n

This is my config file content:


{
"pools" : [
   {
      "name" : "qhor P2P",
      "url" : "http://q30.qhor.net:8336",
      "user" : "CZVP8n6MhNigMn7adbF8e8zqCC3fgQFEZR",
      "pass" : "xx",
      "pool-priority" : "0"
   },
   {
      "name" : "CaCHE p2cache.syware.de P2P",
      "url" : "http://p2cache.syware.de:8336",
      "user" : "CZVP8n6MhNigMn7adbF8e8zqCC3fgQFEZR",
      "pass" : "xx",
      "pool-priority" : "1"
   },
   {
      "name" : "p2p-miner.info(0)",
      "url" : "http://p2pool-miner.info:8336",
      "user" : "CZVP8n6MhNigMn7adbF8e8zqCC3fgQFEZR",
      "pass" : "xx",
      "pool-priority" : "2"
   }
],
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"failover-only" : true,
"fix-protocol" : true,
"kernel-path" : "/usr/local/bin",
"no-submit-stale" : true,
"queue" : "0",
"gpu-threads" : "1",
"gpu-engine" : "1040,1000,1000,1000",
"gpu-fan" : "70",
"gpu-platform" : "0",
"gpu-memclock" : "1500",
"gpu-powertune" : "20",
"intensity" : "20",
"temp-target" : "85",
"temp-overheat" : "92",
"temp-cutoff" : "94",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "2",
"shaders" : "0",
"thread-concurrency" : "30592",
"scrypt-jane" : true,
"sj-Nfmin" : "4",
"sj-Nfmax" : "30",
"sj-time" : "1388949883"
}


Thanks in advance for help!

Is this seriously not happening to anyone else ?  It keeps happening to me more often.. Basically the GPU is useless once this happens and does not submit any shares.. I keep having to reboot every 45 minutes this is really annoying.  Any help would be appreciated.

cheers,

Try Intensity 19, if that works you may need to "re-tune" your cards to keep them at I 20.

[bit_coin_genuis]

Try Intensity 19, if that works you may need to "re-tune" your cards to keep them at I 20.

Thanks I will give that a try...  I have 4 different miners... this is the only one that does this.. although others have also been very unstable latetly, Crashing the Scrypt jane miner and requiring a re-boot very frequently !

I had been experimenting with my tuning during and found that I could clock down the memory to 800MHZ  from 1500 without a decrease in performance just an FYI for everyone out there !  Also powertune does not increase performance from 0 to +20 does not increase hashing performance.

Cheers,

[Sukarti]

Try Intensity 19, if that works you may need to "re-tune" your cards to keep them at I 20.

Thanks I will give that a try...  I have 4 different miners... this is the only one that does this.. although others have also been very unstable latetly, Crashing the Scrypt jane miner and requiring a re-boot very frequently !

I had been experimenting with my tuning during and found that I could clock down the memory to 800MHZ  from 1500 without a decrease in performance just an FYI for everyone out there !  Also powertune does not increase performance from 0 to +20 does not increase hashing performance.

Cheers,

I have noticed some oddities with tuning on the latest N-Factor as well.

Make sure you're submitting sufficient shares and getting proper WU still. Don't just assume a certain kh/s means everything is good  

If the miners are windows based make sure and try CGWatcher, lots of nice features to keep your miners hashing 24x7.

[bit_coin_genuis]

Try Intensity 19, if that works you may need to "re-tune" your cards to keep them at I 20.

Thanks I will give that a try...  I have 4 different miners... this is the only one that does this.. although others have also been very unstable latetly, Crashing the Scrypt jane miner and requiring a re-boot very frequently !

I had been experimenting with my tuning during and found that I could clock down the memory to 800MHZ  from 1500 without a decrease in performance just an FYI for everyone out there !  Also powertune does not increase performance from 0 to +20 does not increase hashing performance.

Cheers,

I have noticed some oddities with tuning on the latest N-Factor as well.

Make sure you're submitting sufficient shares and getting proper WU still. Don't just assume a certain kh/s means everything is good  

If the miners are windows based make sure and try CGWatcher, lots of nice features to keep your miners hashing 24x7.

Hi,

I have used CG watched since Day 1.  But when miner starts crashing simple mining restarts are not enough. When they restart they hash at very low rates ( i.e. 14 kh/s) and sometimes it just says 0.00kh/s.... sometimes it crahses the computer. Its quite annoying. 

I know there is an option to restart the computer in CGwatcher.. but if you use this of do you run these command lines:


setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

 before tha mining starts automatically ?

[Sukarti]

I use it to auto-restart my computers and cgwatcher reboots via the registry without issue.

I don't manually execute any commands, and mining commences without issue.

I believe once you issue those from a cmd or bat re-issuing is just redundant.

[bit_coin_genuis]

I use it to auto-restart my computers and cgwatcher reboots via the registry without issue.

I don't manually execute any commands, and mining commences without issue.

I believe once you issue those from a cmd or bat re-issuing is just redundant.

Redundant after a re-boot ?  I seriously doubt that ... If you shutdown/ restart your computer commands have to be re-entered... But I will try without I guess.

On a side note ... I am basically mining alone at http://pool.cachecoin.net,  someone come and join me ... 2 blocks found in the last 3 hours     Almost all the CACH to myself got very lucky !  But if one goes to 200% I will be mining for days !!! need more hash power !

I find the pool mining to be much more stable... When I mine P2P crashes are more frequent and I find the P2P nodes to be unreliable lately.  Miner is contstantly waiting for new work.

Cheers,

[Sukarti]

There are plenty of persistent windows commands, issuing them once is sufficient.

setx is just editing system environment variables. Go to System Properties > Advanced > Environment Variables > User Variables

There's your 2 parameters.

So doubt or not, it works 

P2P (P2Pool.cachecoin.org) has been extremely stable for me, maybe it's your latency to the node? 1-2% rejects on 280x. 4.5% rejects on my 290's

I solo mine once hash drops back below 100MH/s.

Either way, good luck mining!

[bit_coin_genuis]

another things I was wondering ...

To get PoS for CACHE, do you your wallet need to be open ?  How do I remove encryption from my wallet if I have encrypted it ... ( not the command line) I just want to remove it altogether so I don't have to remember to enter it so that I can PoS coins .

also.. When exactly is the N factor Going up today ?

Cheers,

[BlueGreen]

So, I literally just started mining CACHeCoins about an hour ago. My R9 270s, on normal Scrypt, get a nice stable 480 or so, but I'm no where near that when I'm mining Cache.

I've been playing with settings in CGMiner, and I can't break 160 Kh/s per card. And weirdly, it doesn't seem to matter what I do, it's always 160. Intensity can be anywhere from 13 to 19, TC can be 8192 up to 12736, GPU Engine from 950 to 1070, I can even set the Mem clock between 800 and 1500 with no apparent hash rate changes.

Am I missing something? Shouldn't I be getting higher hash rates? I'm running SMOS with rmDavidson's version of CGminer. I didn't update the Catalyst drivers when I compiled, could that be it?

I'm starting off the command line like this: /opt/miners/cgminer/cgminer --scrypt-jane -I 15 --temp-target 70 --temp-overheat 80 --temp-cutoff 85 -g 2 -w 256 --thread-concurrency 8192 --gpu-engine 1000 --gpu-memclock 800 --gpu-powertune 0 --gpu-threads 2 --expiry 1 --queue 0 --lookup-gap 2 --gpu-fan 75 --sj-nfmin 4 --sj-nfmax 30 --sj-time 1388949883 -o stratum+tcp://east1.us.stratum.dedicatedpool.com:3364 -u ********** -p ***********

Or is this just the expected hash rate after the nFactor change? 160 is pretty sad...

[Sy]

So, I literally just started mining CACHeCoins about an hour ago. My R9 270s, on normal Scrypt, get a nice stable 480 or so, but I'm no where near that when I'm mining Cache.

I've been playing with settings in CGMiner, and I can't break 160 Kh/s per card. And weirdly, it doesn't seem to matter what I do, it's always 160. Intensity can be anywhere from 13 to 19, TC can be 8192 up to 12736, GPU Engine from 950 to 1070, I can even set the Mem clock between 800 and 1500 with no apparent hash rate changes.

Am I missing something? Shouldn't I be getting higher hash rates? I'm running SMOS with rmDavidson's version of CGminer. I didn't update the Catalyst drivers when I compiled, could that be it?

I'm starting off the command line like this: /opt/miners/cgminer/cgminer --scrypt-jane -I 15 --temp-target 70 --temp-overheat 80 --temp-cutoff 85 -g 2 -w 256 --thread-concurrency 8192 --gpu-engine 1000 --gpu-memclock 800 --gpu-powertune 0 --gpu-threads 2 --expiry 1 --queue 0 --lookup-gap 2 --gpu-fan 75 --sj-nfmin 4 --sj-nfmax 30 --sj-time 1388949883 -o stratum+tcp://east1.us.stratum.dedicatedpool.com:3364 -u ********** -p ***********

Or is this just the expected hash rate after the nFactor change? 160 is pretty sad...

Seems about right...

[r05]

another things I was wondering ...

To get PoS for CACHE, do you your wallet need to be open ?  How do I remove encryption from my wallet if I have encrypted it ... ( not the command line) I just want to remove it altogether so I don't have to remember to enter it so that I can PoS coins .

also.. When exactly is the N factor Going up today ?

Cheers,

That is a very, very bad idea - no wallet should be kept unencrypted. To unlock for POS, run the command "walletpassphrase <passphrase> 99999999" in the debug console.

Regarding the PoS "not working", my CacheCoin wallet CPU usage is higher than my other wallets, I guess it's doing "something"?!?!?

POS doesn't require any significant CPU usage, so I daresay that isn't the cause of your high processor load.

[bit_coin_genuis]

another things I was wondering ...

To get PoS for CACHE, do you your wallet need to be open ?  How do I remove encryption from my wallet if I have encrypted it ... ( not the command line) I just want to remove it altogether so I don't have to remember to enter it so that I can PoS coins .

also.. When exactly is the N factor Going up today ?

Cheers,

That is a very, very bad idea - no wallet should be kept unencrypted. To unlock for POS, run the command "walletpassphrase <passphrase> 99999999" in the debug console.

Ok Noted ... but what about wallet being open .. i am guessing it has to be open and I have to have unlocked it in the debug console ... What happens if My wallet is open and unlcoked for 6 days ... then I reboot. or computer crashes as it is mining ... Will I lose those 6 days of coins sitting in my wallet for PoS ... Is there a PoS  for dummies FAQ or something out there ... I feel bad asking all these questions but there literally is no information out there I feel there should be.

[kalgecin]

another things I was wondering ...

To get PoS for CACHE, do you your wallet need to be open ?  How do I remove encryption from my wallet if I have encrypted it ... ( not the command line) I just want to remove it altogether so I don't have to remember to enter it so that I can PoS coins .

also.. When exactly is the N factor Going up today ?

Cheers,

That is a very, very bad idea - no wallet should be kept unencrypted. To unlock for POS, run the command "walletpassphrase <passphrase> 99999999" in the debug console.

Ok Noted ... but what about wallet being open .. i am guessing it has to be open and I have to have unlocked it in the debug console ... What happens if My wallet is open and unlcoked for 6 days ... then I reboot. or computer crashes as it is mining ... Will I lose those 6 days of coins sitting in my wallet for PoS ... Is there a PoS  for dummies FAQ or something out there ... I feel bad asking all these questions but there literally is no information out there I feel there should be.

You won't loose you "days". The PoS miner looks at how old the transaction is. Not how long it has been open

[vertoe]

Ok Noted ... but what about wallet being open .. i am guessing it has to be open and I have to have unlocked it in the debug console ... What happens if My wallet is open and unlcoked for 6 days ... then I reboot. or computer crashes as it is mining ... Will I lose those 6 days of coins sitting in my wallet for PoS ... Is there a PoS  for dummies FAQ or something out there ... I feel bad asking all these questions but there literally is no information out there I feel there should be.

Don't worry, you wont lose anything if your machine crashes. Just keep the wallet open and unlocked. If you recieve a block you get coins and if you dont ... well, then you dont. But it doesnt matter how long your wallet is open, you dont need to keep it open 7 days!!! Just the coin age is important!

Regarding the PoS "not working", my CacheCoin wallet CPU usage is higher than my other wallets, I guess it's doing "something"?!?!?

POS doesn't require any significant CPU usage, so I daresay that isn't the cause of your high processor load.

Validating the blockchain needs CPU, that's maybe why you see it. It stops doing that after a certain amount of time.

[r05]

Ok Noted ... but what about wallet being open .. i am guessing it has to be open and I have to have unlocked it in the debug console ... What happens if My wallet is open and unlcoked for 6 days ... then I reboot. or computer crashes as it is mining ... Will I lose those 6 days of coins sitting in my wallet for PoS ... Is there a PoS  for dummies FAQ or something out there ... I feel bad asking all these questions but there literally is no information out there I feel there should be.

Don't worry, you wont lose anything if your machine crashes. Just keep the wallet open and unlocked. If you recieve a block you get coins and if you dont ... well, then you dont. But it doesnt matter how long your wallet is open, you dont need to keep it open 7 days!!! Just the coin age is important!

Regarding the PoS "not working", my CacheCoin wallet CPU usage is higher than my other wallets, I guess it's doing "something"?!?!?

POS doesn't require any significant CPU usage, so I daresay that isn't the cause of your high processor load.

Validating the blockchain needs CPU, that's maybe why you see it. It stops doing that after a certain amount of time.

How many coins have you in your wallet for it to mint that amount? I have ~100 with a coin age of 7 days+ and I haven't seen any staked coins yet.

After having talked briefly on IRC, my scenario (~100 coins, 14 days old) can expect to stake 0.2-0.4 CACH and luck plays a significant part.

[simonhard]

http://www.reddit.com/r/CoinedUp/comments/1zsi0e/please_add_cachecoin_cach/

Please support.

[vaskomobile]

Hello , about hour ago , in my miner i start to see a lot of HW , they only disappear  if i reduce tc , and with reduced tc i only get 200kh. (before was 1500)

Is this normal ? or ?

[r05]

Hello , about hour ago , in my miner i start to see a lot of HW , they only disappear  if i reduce tc , and with reduced tc i only get 200kh. (before was 1500)

Is this normal ? or ?

It could be the nFactor increase. You normally need to decrease the intensity (-i) when this happens to avoid HW errors.