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

[singula]

Could you have a look at the pool's transactions around the downtime? I think I'm missing payout for a day or two of mining, even though the down time was in the range of hours or so. I'll only have access to my miner in about a week, so can't really provide any details on this right now.

I checked transactions in your account and transactions in the wallet and I have found no discrepancy. The lower payout is probably caused by block 13875 - that block took 915% of estimated time to found (which was very unlucky and statistically should happen with probability 0.5^9.15 = once per about 568 blocks)

Since my pool is much smaller than current biggest (dedicatedpool), that block took slightly over 24 hours to find. If you look at dedicatedpool, they have similarly unlucky block near that time too (Block 13937 took them 787.82% of expected time to find), although at their higher hashrate, this extreme unluckiness resulted "only" in 4 hours without a block (for a pool that is way over 51% of network hashrate it is quite bad result ). Smaller pools have larger earning variance in the same time when compared to larger pools - this is unfortunately inevitable.

On the other hand, for last 24 hours, the time needed to find block on my pool was only 69.73% of time expected by the hashrate, so everybody earned about 43% more than what would be expected (the bad luck was somewhat compensated by following good luck). In the long term, the lucky and unlucky days average out and people will earn about what is expected for their hashrate.

And when you compare long term average, at my pool it is still under 100% of expected time to find the block (99.60%), while on dedicated it is 103.52%, so whoever mined at my pool in the past earned almost 4% more coins with the same hashrate

[myagui]

I checked transactions in your account and transactions in the wallet and I have found no discrepancy. The lower payout is probably caused by block 13875 - that block took 915% of estimated time to found (which was very unlucky and statistically should happen with probability 0.5^9.15 = once per about 568 blocks)

You are absolutely right singula. I had noticed that 'difficult' block when it was just a fraction over 900%, and completely forgot about it. I later noticed no payout for a relatively large duration, but didn't correlate the events! Completely my bad, thanks for clearing it up.

I'm clear on the matters of luck, variance and pool dominance.
It's not by accident that I'm mining with your pool   

Cheers,
~ Myagui

[singula]

Thanks for your answer. my 500 CACHs are sum of several transactions because I mined mostly from your pool. But still I mined from 06-03-2014 so at least I should have one stake transaction, right?
I can't open my wallet for 24/7 because I don't have stable internet but at least 12 hours / day. So I guess I just have my bad luck with CACH.

This should probably yield you some stakes, I guess probably more than just a single one.
Well, you can use debug commands in the wallet to diagnose the situation:

In the wallet, select Help -> Debug window

A console will appear. First, type "getinfo" command and press enter. Look for line with something like:

Code:

"unlocked_until" : 1711785161

If you find it, then your wallet is password protected, but it is correctly unlocked and staking should work

However, if the value is zero, like:

Code:

"unlocked_until" : 0

.. then your wallet is password protected and NOT unlocked and that is the cause of staking not working.
Use command

Code:

walletpassphrase [passphrase] [timeout]

to unlock it, replacing passphrase with your actual wallet passphrase and timeout is number of seconds for which the wallet will be unlocked (using something like 999999999 will unlock it for many years, or until you turn off the wallet :))

If there is no line with "unlocked_until" -> your wallet is not password protected and staking should work.


For estimating your staking chance, use command listunspent in the console.

If will list your unspent coin inputs. As staking works not on addresses, but on inputs, having your coins fragmented into many inputs will increase your chance for a stake, although the stake value will be smaller (stake value is certain percentage of input amount), as the inputs will be inevitably also smaller.

If you run the wallet 12 hours a day, then perhaps around 100 inputs will get you about 1 stake per day on average. If that command lists only few inputs (less than 5 or 10), than it may be just a very bad luck on your side. otherwise something is probably wrong :)

If all your 500 CACH will be in a single input, then a stake will yield over 2 CACHe, but will have small chance of appearing. If your money is in 20 equal smaller inputs, your stake reward from single input is only 20 times less, but there is about 20x more chance of some stake to actually occur.

Still holding CACH and wait for good news.

Regards,

I am holding all my CACH too ... I have some plans for services that may (or may not, but it is worth trying :) end up with increasing CACHe demand and therefore its value, but due to relative lack of time to implement them, it may take few weeks until I announce the results :)

[myagui]

From the PoS information & details found on the OP:

Code:

walletpassphrase [passphrase] [timeout]

For the purpose of staking, shouldn't one instead use:

Code:

walletpassphrase [passphrase] [timeout] true

As I recall, the 'true' at the end of that command would stand for the wallet unlocking for staking purposes *only*, and otherwise still require a password for any other transaction types to execute. Just pointing this out as the OP does not have the 'true' parameter in there.

Cheers,
~ Myagui

[kalgecin]

From the PoS information & details found on the OP:

Code:

walletpassphrase [passphrase] [timeout]

For the purpose of staking, shouldn't one instead use:

Code:

walletpassphrase [passphrase] [timeout] true

As I recall, the 'true' at the end of that command would stand for the wallet unlocking for staking purposes *only*, and otherwise still require a password for any other transaction types to execute. Just pointing this out as the OP does not have the 'true' parameter in there.

Cheers,
~ Myagui

Yes, you're quite right thanks. fixed

[Hyacin]

Block target is 15 minutes which equates roughly to 96 blocks per day. A majority of which are PoS, not PoW.

We're sitting at 1 mined block (PoW) in 14 hours. So your calculations are way off.

Yeah, I thought the block target applied to PoW only, didn't realize PoS was included in that.  I can't find any easy way to figure out how many PoW blocks to expect in a day so I just gave up, stopped calculating profitability for it, and stopped mining it ...

[gg234]

I am having 3 Asus R9 280x with the following batch file i am getting total 15K/H

cgminer --scrypt-jane --sj-nfmin 4 --sj-nfmax 30 --sj-time 1388949883 -o stratum+tcp://east1.us.stratum.dedicatedpool.com:3364 -u xxx -p xxx
 -w 256,256,256 -I 8,8,8 -g 2 --lookup-gap 2,2,2 --gpu-powertune -20,-20,-20 --temp-overheat 85,85,85 --temp-cutoff 90,90,90 --gpu-memclock 1500,1500,1500 --gpu-engine 1000,1000,1000 --thread-concurrency 8191,8191,8191

Can some one help me how to get proper hash on these cards

Thanks for your help

[Slipknot79]

I sent some coins to cryptsy. 1.5 hours past.

Info in wallet: Status: 0/offline, has not been successfully broadcast yet
What is this? Never have had this.

Transaction ID: e2a37ea6fdbf6a0badd3b12df2385955a085f910c45ae40abf6bd2c23cf8ec2a

[Walrusbonzo]

I am having 3 Asus R9 280x with the following batch file i am getting total 15K/H

cgminer --scrypt-jane --sj-nfmin 4 --sj-nfmax 30 --sj-time 1388949883 -o stratum+tcp://east1.us.stratum.dedicatedpool.com:3364 -u xxx -p xxx
 -w 256,256,256 -I 8,8,8 -g 2 --lookup-gap 2,2,2 --gpu-powertune -20,-20,-20 --temp-overheat 85,85,85 --temp-cutoff 90,90,90 --gpu-memclock 1500,1500,1500 --gpu-engine 1000,1000,1000 --thread-concurrency 8191,8191,8191

Can some one help me how to get proper hash on these cards

Thanks for your help

Try these settings :-

 -w 256,256,256 -I 12,12,12 -g 2 --lookup-gap 2,2,2 --gpu-powertune -20,-20,-20 --temp-overheat 85,85,85 --temp-cutoff 90,90,90 --gpu-memclock 1500,1500,1500 --gpu-engine 1044,1044,1044 --thread-concurrency 16384,16384,16384

They get me 137~140kh/s.

[kalgecin]

I sent some coins to cryptsy. 1.5 hours past.

Info in wallet: Status: 0/offline, has not been successfully broadcast yet
What is this? Never have had this.

Transaction ID: e2a37ea6fdbf6a0badd3b12df2385955a085f910c45ae40abf6bd2c23cf8ec2a

That means your wallet is offline

[Slipknot79]

I sent some coins to cryptsy. 1.5 hours past.

Info in wallet: Status: 0/offline, has not been successfully broadcast yet
What is this? Never have had this.

Transaction ID: e2a37ea6fdbf6a0badd3b12df2385955a085f910c45ae40abf6bd2c23cf8ec2a

That means your wallet is offline

And how can i solve this? I never "touched this running system", means, i didnt change anything and suddenly its offline?

[kalgecin]

I sent some coins to cryptsy. 1.5 hours past.

Info in wallet: Status: 0/offline, has not been successfully broadcast yet
What is this? Never have had this.

Transaction ID: e2a37ea6fdbf6a0badd3b12df2385955a085f910c45ae40abf6bd2c23cf8ec2a

That means your wallet is offline

And how can i solve this? I never "touched this running system", means, i didnt change anything and suddenly its offline?

check the number of connections you have. maybe your router? That tx hasn't been broadcasted

[vertoe]

From the PoS information & details found on the OP:

Code:

walletpassphrase [passphrase] [timeout]

For the purpose of staking, shouldn't one instead use:

Code:

walletpassphrase [passphrase] [timeout] true

As I recall, the 'true' at the end of that command would stand for the wallet unlocking for staking purposes *only*, and otherwise still require a password for any other transaction types to execute. Just pointing this out as the OP does not have the 'true' parameter in there.

Cheers,
~ Myagui

Ah, didnt know that either... thanks

[CoinAccel]

New exchange: https://coinaccel.com/#market/4

[instacalm]

CACHeCoin Wallet Update 5.0.2: including OpenSSL fix

For more info on the recently discovered OpenSSL flaw, click here.

http://www.mediafire.com/download/yb5vqln0pyj5np5/CACHeCoin-Qt-Windows-SSLfix-v5.0.2.zip

zip md5 = c73996ba17880f39fbbff0d6d27eb512




for tips, BTC:  13JWfmufBecYccXSfKquXJTMma8s3Kyxaf

Mac OS X update to be posted shortly.

[gentamicin]

hi !

can anybody share your settings for 290x sapphire tri-x OC version. i am running 3 mining cach on a pool.

[Slipknot79]

Slow death of CACH Oo, some1 sold 3600 CACH on cryptsy Oo

[hyeoam]

Charts here: http://crypto-prices.com/CACH

[myagui]

Slow death of CACH Oo, some1 sold 3600 CACH on cryptsy Oo

I'm choosing to read:
Strong trading of CACH Oo, some1 just bought cheap 3600 CACH on craptsy Oo

 

Happy Mining
~ Myagui

[1qaz]

why so fast rate falls ? 3.50 - 0.24 lose stability its bad   why