Pages:
Author

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

member
Activity: 66
Merit: 10
Meanwhile I got a deposit address and sent some coins for testing. It tooks a while now, still not visible after 30min, but I'm patient.
full member
Activity: 168
Merit: 100
I think there's still an issue generating a deposit address on cryptsy..
also id be surprised if deposits would actually be available today. usually it takes a few days before they allow deposits to go through
hero member
Activity: 518
Merit: 505
Unlock means, disable password/encryption?
yes

how can i unlock it?
i secured my wallet with a password ... when i want to send coins i have to enter the password but imho thats only temporaly?

Help > Debug > Console > Enter:
Code:
walletpassphrase  9999999

This will unlock your wallet for 9999999 seconds (>100 days) or until you restart the client.

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?
Yes thats all.

Seems simple enough...however I've done that and I still don't see any coins under "Stake" in my wallet, and the coins are more than 7 days old. I'm not sure what I'm doing wrong.
Patience young padawan.

CACHeCoin has been added to cryptsy! Smiley

Cheesy

https://www.cryptsy.com/markets/view/154

Cheesy
sr. member
Activity: 336
Merit: 250
my wallet version says v0.5.0.0-g32a928e-cach-wm-alpha
but, I couldnt sync from yesterday.

Any ideas?
hero member
Activity: 742
Merit: 500
Its as easy as 0, 1, 1, 2, 3
sr. member
Activity: 406
Merit: 250
Can somone 1 tell me the total supply? 2 billion?
newbie
Activity: 53
Merit: 0
CACHeCoin has been added to cryptsy! Smiley

Should be interesting.
hero member
Activity: 742
Merit: 500
Its as easy as 0, 1, 1, 2, 3
member
Activity: 66
Merit: 10
CACHeCoin has been added to cryptsy! Smiley
newbie
Activity: 53
Merit: 0
I couldn't get it to sync even after upgrading to 5.0 - blockchain would just get stuck.

Backed up wallet.dat & renamed %appdata%\cachecoin, and launched 5.0 again to load the blockchain fresh.  Synced fine & restored wallet.dat - all OK.

Cheers

I had to restart the wallet a few times to get it to sync after upgrade to 5.0. Not sure why but it worked after a few attempts. I did not have to re-download the block-chain though.
full member
Activity: 184
Merit: 100
I couldn't get it to sync even after upgrading to 5.0 - blockchain would just get stuck.

Backed up wallet.dat & renamed %appdata%\cachecoin, and launched 5.0 again to load the blockchain fresh.  Synced fine & restored wallet.dat - all OK.

Cheers
full member
Activity: 196
Merit: 100
Unlock means, disable password/encryption?
yes

how can i unlock it?
i secured my wallet with a password ... when i want to send coins i have to enter the password but imho thats only temporaly?

Help > Debug > Console > Enter:
Code:
walletpassphrase 9999999

This will unlock your wallet for 9999999 seconds (>100 days) or until you restart the client.

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?
Yes thats all.

Seems simple enough...however I've done that and I still don't see any coins under "Stake" in my wallet, and the coins are more than 7 days old. I'm not sure what I'm doing wrong.
sr. member
Activity: 462
Merit: 251
Strange, i'm that only user on p2pool-miner.info and my personal stats shows stale 0.539%

When I look at http://p2pool-miner.info:8336/static/ it shows "Local Node: 1.43MH/s (Stale: 17%) from 1 users"
And when I look at local user summary there, the only line is: "Ce9hvb5QAYvD1wpHa1hj5Hqc3cDceojJpF   1.41MH/s   0.194%"
So it seems at least one of these statistics is reported badly - if the pool reports 0.194% stale for single user but 17% stale for local node (comprising of that single user), it is strange. Either one of these two numbers is plain wrong, or they are different numbers with different meaning (one of them is stales between user and local node, the other stales between local node and rest of the network?). Can someone with more insight into that pool's frontend tell which number is correct, or explain how to interpret these numbers?
hero member
Activity: 585
Merit: 500
Quote from: singula
That is not what I see when looking at the stats:
q30.qhor.net: 3.53MH/s (Stale: 14%) from 13 users
cach.cryptoprojects.eu: 3.94 MH/s (DOA NaN H/s / NaN%) - local DOA stats does not work ...
p2cache.syware.de:11.2MH/s (Stale: 11%) from 15 users
185.8.164.16: 0.00H/s (NaN% DOA) - this one is empty
p2pool.cachecoin.org: 1.12MH/s (0.16% DOA) - this one has smallest DOA rate from all the non-empty pools.
p2pool-miner.info: 1.40MH/s (Stale: 17%) from 1 users
46.4.96.166: 6.99kH/s (0.0% DOA) - almost empty

Strange, i'm that only user on p2pool-miner.info and my personal stats shows stale 0.539%
sr. member
Activity: 462
Merit: 251
Also, as the hashrate at the first pool (http://cach.catcoin.cz) is less than about 10% of the network hashrate (the network hashrate may be wrong, but anyway the pol hashrate is still less than 1/3 of p2pool hashrate, so it is very unlikely to be over 20% of real hashrate), the registrations are open on both pools (http://cach.catcoin.cz and http://pool.cachecoin.net).

kalgecin: Can you update first post?
sr. member
Activity: 462
Merit: 251
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.

Someone using obsolete/misconfigured p2pool nodes?

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%.

That is not what I see when looking at the stats:
q30.qhor.net: 3.53MH/s (Stale: 14%) from 13 users
cach.cryptoprojects.eu: 3.94 MH/s (DOA NaN H/s / NaN%) - local DOA stats does not work ...
p2cache.syware.de:11.2MH/s (Stale: 11%) from 15 users
185.8.164.16: 0.00H/s (NaN% DOA) - this one is empty
p2pool.cachecoin.org: 1.12MH/s (0.16% DOA) - this one has smallest DOA rate from all the non-empty pools.
p2pool-miner.info: 1.40MH/s (Stale: 17%) from 1 users
46.4.96.166: 6.99kH/s (0.0% DOA) - almost empty

seems some small pools have DOA under 1 %, but the largest pool has 11% stales and from the 7 public pools, 3 of them have stales over 10% (and one unknown)

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.

Whoever finds the block has advantage for the next block, as he can begin computations on the next block immediately, but rest of the network need to wait for that block to be received by the network. This gives few seconds advantage to the block submitter and may be quite noticable on coins with less than a minute blocks, but with the block time increasing, the significance of this advantage decreases and for block times around 15 minutes it is quite insignificant (less than 1% advantage for pool nearing 100% of the hashrate).

As for PPLNS vs. PROP:
Vardiff on both my pools is set up so that one share is submitted every 45 (first pool) or 25 (second pool) seconds. This means that shares are coming (approximately) at the same rate from everybody, though share from someone with 10Mh/s has bigger value and in average block time a miner should submit (in average) 20 or 36 shares (1st/2nd pool) - therefore risk of miner not finding a share in the duration of a block (so he would be left from payout on it) is very low with current configuration.

I can easily switch one or both pools to PPLNS too (this would be a simple configuration change), if I'd believe it will help something, but I think PROP is better, so I'm keeping it as it is now Smiley
sr. member
Activity: 462
Merit: 251
what is wrong?
i downloaded the latest qt-version but it won't sync ...

jumps from 43 block, 3 blocks to 23 blocks remaining etc ... ?! Sad
newbie
Activity: 14
Merit: 0
I Like coin CacheCoin  Grin

CVphnqPLLRuBGzuRytgDMGjXqDo9c4MfP9   Wink Wink
hero member
Activity: 819
Merit: 1000
Yes, NFactor increased, gpu mining was expected to be hit hard. Some cards with low amount of ram or low ram speed are estimated to be unprofitable for mining at the moment. Amount of hashrate reduced from gpu depends on the gpu, it's different for most.
newbie
Activity: 53
Merit: 0
Thanks for the explanations PJ.

I'll work on tuning, dropping the Intensity was just to temporarily remove the HW errors being generated.
Pages:
Jump to: