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

[Mattzees]

My CACHe wallet has stopped working.  I'm running the most recent version (5.0.0).

Symptoms: It syncs up to a point and then stops.  It seems to sync up to ~1 block left, then goes to ~257 blocks left, and sits there doing nothing.

Steps taken so far: I've tried deleting the database folder, .lock file, blk*.dat files, and peers.dat   
That seems to work at first, but then the same end result happens.

There are many orphaned blocks in my debug file.

Any advice?
 

[kalgecin]

Are we looking at another 5-6 days before difficulty drops to a better proportion with hashrate?

That hashrate spike really screws with the difficulty.

what wrong? mining goes on, confirmations take less than the targeted 15 minutes...... All is well as for as the protocol is concerned

Nothings wrong per se.

I was just curious how long it will take difficulty to actually reflect the current hashrate?

For example Feb 13 estimated hashrate was around 65MH/s and difficulty was 10.11 with 17 coins/block. (http://stats.cachecoin.org/charts.)

Today estimated hashrate from getmininginfo is 66MH and a difficulty of 53 with 12.8 coins/block

The difficulty has been dropping 10-12 per day since 500MH/s has dropped from the network.

Block time seems to be around 14.9 minutes in the past 16 hours so that aspect seems correct.

All is well regarding the protocol and network however, the people still mining the coin are "holding the bag" to solve blocks while difficulty adjusts back down for several days to a week. You are basically mining at ~75% the efficiency or less you were prior to the hashrate spike.

Am I incorrect with this data?

If we continually see huge increases in hash once things settle back down I feel like it hurts the long term viability of the coin somewhat.

Take this as an example. There was obviously a huge pump of the coin in terms of hash and difficulty the last few days. There is now around 1 week of less efficient or less profitable mining to be done before we're back to "normal". IF there is another huge pump what is the incentive to stick it out if the coin can be "easily" manipulated with profitability ebbing and flowing.

Isn't the purpose of this coins difficulty calculations to make mining as evenly profitable and fair at all times?

Should the difficulty deltas be adjusted slightly so the difficulty is more responsive to huge spikes in hashrate as well as huge drops hence making it more resilient to pump and dump miners?

How many prior blocks are referenced with calculating next difficulty? Or is there a cap on the net change in difficulty per block if it is recalculated every block.

Is there anywhere more information is available regarding block reward and difficulty adjustments for this coin?

Thanks for taking the time to read and answer.

I'm not trying to bash the coin, I just want to understand how it works under the hood a bit better.

The difficulty is recalculated on every block. Max diff can increase is by ~0.3% but it can drop by any % (according to how long it took the last block to be solved). You can find more info from src

[Schinder75]

Crazy, mining on cach.catcoin.cz and i got with 300 KHs only around 1 cachecoin per day for the last 5 days.

If I mine multicoins and trade them, I'm able to buy 1.5 cachecoins per day...

So for me its better to not mine the cachecoin to get more cachecoins...sounds crazy doesn't it?

[simonhard]

Crazy, mining on cach.catcoin.cz and i got with 300 KHs only around 1 cachecoin per day for the last 5 days.

If I mine multicoins and trade them, I'm able to buy 1.5 cachecoins per day...

So for me its better to not mine the cachecoin to get more cachecoins...sounds crazy doesn't it?

Most the time it's more efficient to mine Whatevercoin than Bitcoin to get more btc - crazy? no!

[Schinder75]

Crazy, mining on cach.catcoin.cz and i got with 300 KHs only around 1 cachecoin per day for the last 5 days.

If I mine multicoins and trade them, I'm able to buy 1.5 cachecoins per day...

So for me its better to not mine the cachecoin to get more cachecoins...sounds crazy doesn't it?

Most the time it's more efficient to mine Whatevercoin than Bitcoin to get more btc - crazy? no!

I was just surprised that a new coin after 2 months from release is so hard to mine. Thats all...
I battled my linux for 2 days just to get the cgminer with scrypt-jane compiled. Having compiled the stuff, set it up and got running, it is a little bit disappointing that all the work just ended in the result to better mine something else.

But I learned much about linux theses days ;-)

[kalgecin]

My CACHe wallet has stopped working.  I'm running the most recent version (5.0.0).

Symptoms: It syncs up to a point and then stops.  It seems to sync up to ~1 block left, then goes to ~257 blocks left, and sits there doing nothing.

Steps taken so far: I've tried deleting the database folder, .lock file, blk*.dat files, and peers.dat  
That seems to work at first, but then the same end result happens.

There are many orphaned blocks in my debug file.

Any advice?
 

please upload the log file for me to be able to help you

[Mattzees]

My CACHe wallet has stopped working.  I'm running the most recent version (5.0.0).

Symptoms: It syncs up to a point and then stops.  It seems to sync up to ~1 block left, then goes to ~257 blocks left, and sits there doing nothing.

Steps taken so far: I've tried deleting the database folder, .lock file, blk*.dat files, and peers.dat   
That seems to work at first, but then the same end result happens.

There are many orphaned blocks in my debug file.

Any advice?
 

In addition to the above problem, which I'm still having, my debug file mentions something about being logged into an IRC channel.  What is that about?

[Snard]

I compiled the latest version and included the logo in the splash screen.  Maybe give this version a  try and see if it helps:

http://www.chainbrowser.com/qt/CACHeCoin.zip

[kalgecin]

My CACHe wallet has stopped working.  I'm running the most recent version (5.0.0).

Symptoms: It syncs up to a point and then stops.  It seems to sync up to ~1 block left, then goes to ~257 blocks left, and sits there doing nothing.

Steps taken so far: I've tried deleting the database folder, .lock file, blk*.dat files, and peers.dat   
That seems to work at first, but then the same end result happens.

There are many orphaned blocks in my debug file.

Any advice?
 

In addition to the above problem, which I'm still having, my debug file mentions something about being logged into an IRC channel.  What is that about?

Could you guys please upload the log file instead of simply saying that "it says something like...". The coin uses IRC channel to find peers. Avoids having complicated conf files like some coins do. with loads of nodes

[vtbean79]

How many total coins?

[vertoe]

Since there are only 4 a day, I'd call that a success

4 blocks a day? Wrong coin? xD

P2Pool alone had 12 blocks in last 24 hours.
http://q30.qhor.net:8336/static/

Block   Time   Luck   Value (CACH)
10111   Tue, 25 Feb 2014 15:15:53 GMT   375.4%   0.000
10097   Tue, 25 Feb 2014 10:59:30 GMT   6.7%   0.000
10095   Tue, 25 Feb 2014 10:54:55 GMT   98.1%   0.000
10092   Tue, 25 Feb 2014 09:47:55 GMT   11.7%   0.000
10091   Tue, 25 Feb 2014 09:39:57 GMT   7.6%   0.000
10089   Tue, 25 Feb 2014 09:34:44 GMT   103.8%   0.000
10085   Tue, 25 Feb 2014 08:23:50 GMT   8.2%   0.000
10084   Tue, 25 Feb 2014 08:18:12 GMT   343.2%   0.000
10071   Tue, 25 Feb 2014 04:23:51 GMT   106.3%   0.000
10063   Tue, 25 Feb 2014 03:11:17 GMT   287.1%   0.000
10049   Mon, 24 Feb 2014 23:55:12 GMT   8.7%   0.000
10048   Mon, 24 Feb 2014 23:49:15 GMT   34.0%   0.000
10047   Mon, 24 Feb 2014 23:26:03 GMT   46.8%   0.000
10046   Mon, 24 Feb 2014 22:54:06 GMT   107.4%   0.000
10040   Mon, 24 Feb 2014 21:40:47 GMT   236.6%   0.000
10028   Mon, 24 Feb 2014 18:59:11 GMT   0.0%   0.000
block value all 0..what happen??..
no coin pay out??

I'm too lazy to find a good source to display the actual block value and in addition this would slow down the java script. just ignore the value. click on the block id and see the transaction including the payouts.

Since there are only 4 a day, I'd call that a success

4 blocks a day? Wrong coin? xD

P2Pool alone had 12 blocks in last 24 hours.
http://q30.qhor.net:8336/static/

XD

By the way, I'm diggin your p2pool node friend. Just switched to it from a regular pool, the stats are so much better and I love that its straight to my wallet .

*thumbs up* - p2pool ist the way to go for CACHe - cryptoprojects.eu:8336 as backup is also good ;-)

got only 3 transactions over the last ~35-40 hours in p2pool ... (~1 CACH all together) ... that is quite low imho ?!?!
1.2 mh/s

with 1.2 mh/s you should get more than 3 tx per day. whats your address and which node are you using?

Are we looking at another 5-6 days before difficulty drops to a better proportion with hashrate?

That hashrate spike really screws with the difficulty.

what wrong? mining goes on, confirmations take less than the targeted 15 minutes...... All is well as for as the protocol is concerned

Nothings wrong per se.

I was just curious how long it will take difficulty to actually reflect the current hashrate?

For example Feb 13 estimated hashrate was around 65MH/s and difficulty was 10.11 with 17 coins/block. (http://stats.cachecoin.org/charts.)

Today estimated hashrate from getmininginfo is 66MH and a difficulty of 53 with 12.8 coins/block

The difficulty has been dropping 10-12 per day since 500MH/s has dropped from the network.

Block time seems to be around 14.9 minutes in the past 16 hours so that aspect seems correct.

All is well regarding the protocol and network however, the people still mining the coin are "holding the bag" to solve blocks while difficulty adjusts back down for several days to a week. You are basically mining at ~75% the efficiency or less you were prior to the hashrate spike.

[...]

That's why I suggest that PoS blocks should also adjust PoW difficulty and vice versa.

My CACHe wallet has stopped working.  I'm running the most recent version (5.0.0).

Symptoms: It syncs up to a point and then stops.  It seems to sync up to ~1 block left, then goes to ~257 blocks left, and sits there doing nothing.

Steps taken so far: I've tried deleting the database folder, .lock file, blk*.dat files, and peers.dat   
That seems to work at first, but then the same end result happens.

There are many orphaned blocks in my debug file.

Any advice?
 

In addition to the above problem, which I'm still having, my debug file mentions something about being logged into an IRC channel.  What is that about?

Could you guys please upload the log file instead of simply saying that "it says something like...". The coin uses IRC channel to find peers. Avoids having complicated conf files like some coins do. with loads of nodes

Curious, which one is it?

How many total coins?

No limit but fees will be destroyed.

[ammi84]

Hi,

i used this ...

{
      "url" : "http://p2cache.syware.de:8336",
      "user" : "CT9QhDM3sZQTTPhVvZ4Hx95T7BjzTcetE5",
      "pass" : "x"
   },

today i got some transactions in my wallet ... but i couldn't see them in the blockchain for a long while?!?!?

[r05]

My CACHe wallet has stopped working.  I'm running the most recent version (5.0.0).

Symptoms: It syncs up to a point and then stops.  It seems to sync up to ~1 block left, then goes to ~257 blocks left, and sits there doing nothing.

Steps taken so far: I've tried deleting the database folder, .lock file, blk*.dat files, and peers.dat   
That seems to work at first, but then the same end result happens.

There are many orphaned blocks in my debug file.

Any advice?
 

In addition to the above problem, which I'm still having, my debug file mentions something about being logged into an IRC channel.  What is that about?

Upload the debug file. Nobody is going to help you unless you can follow simple instructions.

[Sukarti]

Are we looking at another 5-6 days before difficulty drops to a better proportion with hashrate?

That hashrate spike really screws with the difficulty.

what wrong? mining goes on, confirmations take less than the targeted 15 minutes...... All is well as for as the protocol is concerned

Nothings wrong per se.

I was just curious how long it will take difficulty to actually reflect the current hashrate?

For example Feb 13 estimated hashrate was around 65MH/s and difficulty was 10.11 with 17 coins/block. (http://stats.cachecoin.org/charts.)

Today estimated hashrate from getmininginfo is 66MH and a difficulty of 53 with 12.8 coins/block

The difficulty has been dropping 10-12 per day since 500MH/s has dropped from the network.

Block time seems to be around 14.9 minutes in the past 16 hours so that aspect seems correct.

All is well regarding the protocol and network however, the people still mining the coin are "holding the bag" to solve blocks while difficulty adjusts back down for several days to a week. You are basically mining at ~75% the efficiency or less you were prior to the hashrate spike.

Am I incorrect with this data?

If we continually see huge increases in hash once things settle back down I feel like it hurts the long term viability of the coin somewhat.

Take this as an example. There was obviously a huge pump of the coin in terms of hash and difficulty the last few days. There is now around 1 week of less efficient or less profitable mining to be done before we're back to "normal". IF there is another huge pump what is the incentive to stick it out if the coin can be "easily" manipulated with profitability ebbing and flowing.

Isn't the purpose of this coins difficulty calculations to make mining as evenly profitable and fair at all times?

Should the difficulty deltas be adjusted slightly so the difficulty is more responsive to huge spikes in hashrate as well as huge drops hence making it more resilient to pump and dump miners?

How many prior blocks are referenced with calculating next difficulty? Or is there a cap on the net change in difficulty per block if it is recalculated every block.

Is there anywhere more information is available regarding block reward and difficulty adjustments for this coin?

Thanks for taking the time to read and answer.

I'm not trying to bash the coin, I just want to understand how it works under the hood a bit better.

The difficulty is recalculated on every block. Max diff can increase is by ~0.3% but it can drop by any % (according to how long it took the last block to be solved). You can find more info from src

That's a misleading statement. Like vertoe mentioned difficulty is not recalculated every block. PoW difficulty has been stuck for 6+ hours even though there have been around 12 PoS blocks found.

Only 22 PoW blocks in 24 hours. If difficulty can adjust to any percent when decreasing then why is it dropping so slowly?

There's ~9% of the hashrate (585 vs 55) running from Feb 19 while difficulty remains at 75% from Feb 19 (68.64 vs 51.96)

Not as dynamic as advertised I guess.

[arbuzzinho]

Guys, can you tell me whether my hashrates are OK? Im using cgminer that supports scrypt-jane algorithm. I've read somewhere on the internet, that scrypt-jane hashrate should be something like 75% of scrypt hashrate. In my case, it is not . I'm not getting any HW errors at all.

radeon 7970
265 kH/s (WU: 220 kH/s) -- scrypt-jane
760 kH/s (WU: 690 kH/s) -- scrypt

radeon 270x
186 kH/s (WU: 195 kH/s) -- scrypt-jane
465 kH/s (WU: 410 kH/s) -- scrypt

my configs: (I'm ofcourse executing both cgminers with additional "--scrypt-jane" param)
7970's config:

Code:

"sj-nfmin" : "4",
"sj-nfmax" : "30",
"sj-time" : "1388361600",
"gpu-threads" : "2",
"worksize" : "256",
"intensity" : "12",
"gpu-engine" : "1084,1095,1095",
"gpu-memclock" : "1500,1500,1500",
"gpu-powertune" : "20",
"thread-concurrency" : "8192",
"vectors" : "1",
"lookup-gap" : "0",
"gpu-memdiff" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-listen" : true,
"api-port" : "4028",
"expiry" : "120",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"

270x's config:

Code:

"sj-nfmin" : "4",
"sj-nfmax" : "30",
"sj-time" : "1388949883",
"gpu-threads" : "1",
"worksize" : "256",
"intensity" : "18",
"gpu-engine" : "1120",
"gpu-memclock" : "1500",
"gpu-powertune" : "10",
"thread-concurrency" : "15200",
"vectors" : "1",
"lookup-gap" : "0",
"gpu-memdiff" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-listen" : true,
"api-port" : "4028",
"expiry" : "120",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"

[Sukarti]

Guys, can you tell me whether my hashrates are OK? Im using cgminer that supports scrypt-jane algorithm. I've read somewhere on the internet, that scrypt-jane hashrate should be something like 75% of scrypt hashrate. In my case, it is not . I'm not getting any HW errors at all.

radeon 7970
265 kH/s (WU: 220 kH/s) -- scrypt-jane
760 kH/s (WU: 690 kH/s) -- scrypt

radeon 270x
186 kH/s (WU: 195 kH/s) -- scrypt-jane
465 kH/s (WU: 410 kH/s) -- scrypt

my configs: (I'm ofcourse executing both cgminers with additional "--scrypt-jane" param)
7970's config:

Code:

"sj-nfmin" : "4",
"sj-nfmax" : "30",
"sj-time" : "1388361600",
"gpu-threads" : "2",
"worksize" : "256",
"intensity" : "12",
"gpu-engine" : "1084,1095,1095",
"gpu-memclock" : "1500,1500,1500",
"gpu-powertune" : "20",
"thread-concurrency" : "8192",
"vectors" : "1",
"lookup-gap" : "0",
"gpu-memdiff" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-listen" : true,
"api-port" : "4028",
"expiry" : "120",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"

270x's config:

Code:

"sj-nfmin" : "4",
"sj-nfmax" : "30",
"sj-time" : "1388949883",
"gpu-threads" : "1",
"worksize" : "256",
"intensity" : "18",
"gpu-engine" : "1120",
"gpu-memclock" : "1500",
"gpu-powertune" : "10",
"thread-concurrency" : "15200",
"vectors" : "1",
"lookup-gap" : "0",
"gpu-memdiff" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-listen" : true,
"api-port" : "4028",
"expiry" : "120",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"

Hashrate depends on N factor. Current NFactor is 10. I personally get 300KH on my 280x's and 340KH on my 290's. You should be able to use the same parameters as scrypt other than a possible reduction in Intensity.

[MinermanNC]

Guys, can you tell me whether my hashrates are OK? Im using cgminer that supports scrypt-jane algorithm. I've read somewhere on the internet, that scrypt-jane hashrate should be something like 75% of scrypt hashrate. In my case, it is not . I'm not getting any HW errors at all.

radeon 7970
265 kH/s (WU: 220 kH/s) -- scrypt-jane
760 kH/s (WU: 690 kH/s) -- scrypt

radeon 270x
186 kH/s (WU: 195 kH/s) -- scrypt-jane
465 kH/s (WU: 410 kH/s) -- scrypt

my configs: (I'm ofcourse executing both cgminers with additional "--scrypt-jane" param)
7970's config:

Code:

"sj-nfmin" : "4",
"sj-nfmax" : "30",
"sj-time" : "1388361600",
"gpu-threads" : "2",
"worksize" : "256",
"intensity" : "12",
"gpu-engine" : "1084,1095,1095",
"gpu-memclock" : "1500,1500,1500",
"gpu-powertune" : "20",
"thread-concurrency" : "8192",
"vectors" : "1",
"lookup-gap" : "0",
"gpu-memdiff" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-listen" : true,
"api-port" : "4028",
"expiry" : "120",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"

270x's config:

Code:

"sj-nfmin" : "4",
"sj-nfmax" : "30",
"sj-time" : "1388949883",
"gpu-threads" : "1",
"worksize" : "256",
"intensity" : "18",
"gpu-engine" : "1120",
"gpu-memclock" : "1500",
"gpu-powertune" : "10",
"thread-concurrency" : "15200",
"vectors" : "1",
"lookup-gap" : "0",
"gpu-memdiff" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-listen" : true,
"api-port" : "4028",
"expiry" : "120",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"

Hashrate depends on N factor. Current NFactor is 10. I personally get 300KH on my 280x's and 340KH on my 290's. You should be able to use the same parameters as scrypt other than a possible reduction in Intensity.

Basically this is the same problem I am seeing using scrypt jane,,its hashing, but the hashing ratio difference is about what you are seeing  with your cards.... jane vs scrypt

[kalgecin]

Are we looking at another 5-6 days before difficulty drops to a better proportion with hashrate?

That hashrate spike really screws with the difficulty.

what wrong? mining goes on, confirmations take less than the targeted 15 minutes...... All is well as for as the protocol is concerned

Nothings wrong per se.

I was just curious how long it will take difficulty to actually reflect the current hashrate?

For example Feb 13 estimated hashrate was around 65MH/s and difficulty was 10.11 with 17 coins/block. (http://stats.cachecoin.org/charts.)

Today estimated hashrate from getmininginfo is 66MH and a difficulty of 53 with 12.8 coins/block

The difficulty has been dropping 10-12 per day since 500MH/s has dropped from the network.

Block time seems to be around 14.9 minutes in the past 16 hours so that aspect seems correct.

All is well regarding the protocol and network however, the people still mining the coin are "holding the bag" to solve blocks while difficulty adjusts back down for several days to a week. You are basically mining at ~75% the efficiency or less you were prior to the hashrate spike.

Am I incorrect with this data?

If we continually see huge increases in hash once things settle back down I feel like it hurts the long term viability of the coin somewhat.

Take this as an example. There was obviously a huge pump of the coin in terms of hash and difficulty the last few days. There is now around 1 week of less efficient or less profitable mining to be done before we're back to "normal". IF there is another huge pump what is the incentive to stick it out if the coin can be "easily" manipulated with profitability ebbing and flowing.

Isn't the purpose of this coins difficulty calculations to make mining as evenly profitable and fair at all times?

Should the difficulty deltas be adjusted slightly so the difficulty is more responsive to huge spikes in hashrate as well as huge drops hence making it more resilient to pump and dump miners?

How many prior blocks are referenced with calculating next difficulty? Or is there a cap on the net change in difficulty per block if it is recalculated every block.

Is there anywhere more information is available regarding block reward and difficulty adjustments for this coin?

Thanks for taking the time to read and answer.

I'm not trying to bash the coin, I just want to understand how it works under the hood a bit better.

The difficulty is recalculated on every block. Max diff can increase is by ~0.3% but it can drop by any % (according to how long it took the last block to be solved). You can find more info from src

That's a misleading statement. Like vertoe mentioned difficulty is not recalculated every block. PoW difficulty has been stuck for 6+ hours even though there have been around 12 PoS blocks found.

Only 22 PoW blocks in 24 hours. If difficulty can adjust to any percent when decreasing then why is it dropping so slowly?

There's ~9% of the hashrate (585 vs 55) running from Feb 19 while difficulty remains at 75% from Feb 19 (68.64 vs 51.96)

Not as dynamic as advertised I guess.

The diff is recalculated on every block. But previous blocks are not considered in the equation. I have already explained this.

[mr.pj]

Kal better to explain that every block recalculates their own difficulty
Meaning: PoS only recalculate PoS difficulty and PoW Blocks only PoW difficulty

But it would be an idea for a future release to stop mining beeing so hard, that PoS Blocks can also recalculate the difficulty for PoW Blocks so hashrate spikes are evened out faster.


For anyone wanting to mine cachecoin - check out http://cachepool.cryptoprojects.eu:8336/static/

Running smooth

[r05]

Poloniex is a bit concerning these past few days..