Post
Topic
Board Announcements (Altcoins)
Re: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Pearl
by
dooglus
on 16/05/2015, 04:47:04 UTC
Mac fag checking in.  Running 1.4.10 and smooth sailing so far.  Staking and all. 
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.

Does it go red for long periods at a time? Long enough that you can hover the mouse over it and tell me what pops up when it's red?

If you put:
debug=stake
in the clam.conf file in the same folder as your wallet.dat and restart, it will write stake-related stuff to debug.log in the same folder as it stakes.

You could "tail -f debug.log" in that folder and see whether anything looks different when it's red. Staking basically consists of hashing each of your staking outputs every 16 seconds and comparing the result with a target based on the network difficulty. If the output hashes lower than the target, you get to stake a block. "debug=stake" will cause these hashes that are being compared to be logged.

I couldn't find an existing one, so I created a clam.conf and added debug=stake.  I'm hoping I did it correctly.  I added a screengrab of data flow. http://imgur.com/Gmcfbf8 When I hover the cursor over the red icon, it sometimes says 0 weight.  And then other times it says not staking because I don't have mature coins.  But then I stake at least once a day. 

Hope this helps.  Thanks for everything! 

/s/

Same thing was happening to me on a previous version (1.4.7 i think)  and the 0 weight was also showing.
I haven't seen it happen to me again yet on this latest version.. but I'll watch for it.

It can stay red for up to one minute, i've seen it myself. When you hover over it says 'Not staking because you don't have mature coins'

It doesn't appear to affect staking in the long run, i always just put it down to new blocks being generated and that it was a normal thing.

I have the debug switch on at the moment so i'll try and upload the debug.log next time i see it happen.

So I forgot about this issue until whiskey brought it up again today in the Just-Dice chat. I don't use the QT interface myself, so it was easy to forget about.

I finally found and fixed the bug. It was just a display issue. See https://github.com/nochowderforyou/clams/issues/188 for details.

It will be fixed in the next release of the CLAM client.