Topic: [ANN][CACH] CACHeCoin released based on scrypt-jane - page 85. (Read 224425 times)

Sukarti

please update your wallet - see https://bitcointalksearch.org/topic/m.5205666
then it will sync again - no more nodes needed - posted nodes are already up2date!

For Hashrate reduction: it was expected - finetuning your cards might lead to higher hashrate - but fine tuning goes below just decreasing intensity from 13 to 12. As I wrote earlier, there are different cgminer release that offer finer granularity for finetuning (but you gotta figure out this for yourself)

About the difficulty:
 it will decrease slowly and increase slowly to puffer for coin hopping multipools - around tomorrow we should be around the proper difficulty according to hashrate again. But keep in mind - it still fluctuates a lot since there are a lot of people jumping ship since this is not a pump&dump

About hashrate - the new clients shows the average hashrate of the last 10 blocks instead of the last one .. this will give you a  more accurate assumption on hashrate - but in all clients there is no 100% of knowing the network hashrate, they are all based on assumptions made by difficulty and time between blocks ...

Seems like the total network hashrate is a bit high still after the N adjustment?

It's still sitting at 450MH/s or is that because many miners are sending huge numbers of errors skewing the numbers?

Sorry for all the questions, curious how these N factor adjustments really affect the coin and mining.

Anyone have additional node lists other than the 2 on first posts?

N factor murdered my hash rates. Had to adjust down to eliminate hardware errors, most my miners crashed overnight.

280x dropped Intensity to 12 getting around 300-310 kh/s

290 no intensity change but dropped hash to 330-345 kh/s

290x no Intensity change but dropped hash to 330. (Not tuned very well, in a mixed rig)

Are wallet nodes also down? I can't seem to sync last 20 blocks.

Was a 50% hash rate reduction expected? Or do I need to re-tune all my cards?



Edit: Read back through some posts, it looks like 50% was to be expected, is every N factor adjustment a linear drop in hash rate?

Is there an estimate on how many blocks must be solved before we see proper diff adjustments?

Yes thats all.

New nFactor this morning, make sure your GPU has at least 2GB memory...

It already dropped by 10%.

Diff is dropping slowly.

Hashrates droped, why doesnt diff changing?

Diff down to 73. I'm wondering if many others have been caught out by the requirement to drop intensity.

It depends on the cards ram size - with enough and fast enough ram you would still be able to run at the same intensity. But for quite a few cards (including my 280x gigabyte cards) it is required to lower the intensity. As far as I know there are custom cgminers out there allowing you to tweak thread_concurrency and intensity (xintensity) even more detailed - but I am not sure if they have a scrypt-jane module included that would work with CACHeCoin.
But tweaking these settings might lead to a better usage of ram and higher hashrate

Singula that is not correct:

The Stale rate you see is also including nodes that are running not the right p2pool software. These nodes will still connect to the network but not provide proper shares. Yet the Stale rate is still accounted to the total rate of p2pool.

I've been observing this the past week, that all of a sudden a hashrate of 12mh appears with Stale/Dead on Arrival shares. Yet scanning over all the public pools revealed, that all nodes were running fine and local stale rate was below 1%.

So you can not generalize this - if in doubt - talk to me, vertoe or sy in irc - I can show you log files for these occurences.

In general though, if your hashrate is below a certain fraction of the general p2pool hashrate your stale rate might go up, since you can not provide shares fast enough compared to pool shares. (This should only happen to hashrates below 50kh/s at current nFactor)



That is also not correct - the amount of coins found depends on the amount of blocks found by the pool. In the past week users on your pools were observing a higher return since the pool rate was most of the networks rate and thus was finding more blocks than the average block time of 15minutes... since the hashrate of 1/3 to 2/3 favoring your pool during this low difficulty high hashrate period were in favor for your pool. (But leading to possible security threads on the coin)
The payout right now on p2pool and a traditional pool will be averageing over 24hours.

Since your pools run on prop, there might even be the chance that some miners would not get a payout for a block found. For exmaple in this scenario:
I have a hashrate of 300kh/s  - someone has a hashrate of 10 mh/s. A new round starts, the person with 10mh/s submits quite a lot of shares very fast in the beginning - the pool finds a block before the guy with 300kh/s can submit any share => No payout for the 300kh/s miner

P2pool runs on pplns - this would still pay the 300kh/s miner but would decrease the pplns share until the 300kh/s guy finds another share that will be counted towards the rounds.

That is why the payouts in p2pool fluctuate ... but over 24hours average out to a normal payout

me to had to lower I to get rid of HWs...
I went from 2.8 to 1.4 Mhs, that was somewhat expected because of new N, but having to lower I to get it to mine properly i didn't expect.

Same here.

Sooo if I'm understanding this correctly...all I need to do is leave my wallet open and unlocked for PoS mining to take place?? Or is there anything else I need to do? Like any console commands or anything?

I'm new to PoS mining.

Has NFactor just gone up or something???

I've been mining for days at 1.2mh/s absolutely fine. But noticed that at some point this morning my hashrate had halved and that I was now getting lots of HW errors.

I've had to drop the intensity from 13 to 12 to stop the HW errors.

I know it's not a hardware fault as other coins mine absolutely fine with the settings I've always used.

But diff didnt double. Current diff is 75. I cant remeber a diff-value of 35-40 oO

€dit: Yo, hashrate has been halved. Its 23th feb.

Also, p2pools are not the only option.
There are traditional pools too:

http://cach.catcoin.cz - The original pool - running well since 7th January. More than 25000 CACH mined there already.
http://pool.cachecoin.net - New, 2nd pool - currently smaller pool, but also with smaller fee. Slightly lower vardiff targets for more smooth mining, especially with low hashrates
Both pools use PROP payout and vardiff.

(based on another people requesting advice and assistance with setting up MPOS pool for CACH, I estimate we could have one or two more traditional pools available soon).

Traditional pool has its advantages and disadvantages over p2pools:
Advantages:
- lesser amount of dead/stale/orphan shares. With p2pools, these usually take between 5% and 15% based on current network state, luck, etc (If I look at stats on the biggest pool node right now, I see: P2Pool Total: 176MH/s (Stale: 12%) from 51 users). In traditional mpos pool, these are usually around 0.2% - 0.5%. This means less hash rate wasted.
- better statistics than p2pools

Disadvantages:
- payouts can be only done once you accumulated enough confirmed coins. This will introduce a delay, few hours or maybe a day, based on your hashrate and amount set up for automatic payment.

To sum it up - if you want coins fast (in both cases you won't have the coins sooner than before 520 confirmations though ...) and can cope with only 90% effectivity - go for p2pools.

If you want more coins, but if you are willing to wait perhaps extra day for them - join a traditional mpos pool: http://pool.cachecoin.net, http://cach.catcoin.cz

Total network hash has doubled last few days.

Yo im not really satisfied with my mining results oO

My rig runs at 5,6Mh/s.

Dats my stats:

02.19: 21.5 coins
02.20: 19.6 coins
02.21: 10.0 coins
02.22: 10.3 coins

Why dat drop? My rigs are running fine, diff has been more or less about 76-80. Pointed to p2pool (qhor), very low rejects, very low dead, no HW.

thanks :-)