Quote from: almightyruler on February 18, 2015, 05:32:18 AM

Quote from: dooglus on February 18, 2015, 04:57:49 AM

Quote from: almightyruler on February 18, 2015, 03:43:25 AM

Yep. Not encrypted, and staking=true

Are you seeing any orphaned blocks, or just nothing at all?

That's the other odd thing - according to my transaction list, none of the blocks I've created have ever been orphaned. The list shows 256 "generate" transactions, all with nonzero confirmations (ie, they've been accepted by the network). No mention of the word "orphan" anywhere. I've mentioned this before, as it does seem unusual. I'm running the headless daemon compiled from source.

Are you on the same fork as the rest of us?

$ clamd getblockcount 345127 $ clamd getblockhash 345123 f15274ca7233f757707905afe235045d2fb2a7228049c82a6bc46b30769c47ee

The first command should give a slightly higher number for you, depending on how long elapses between me writing and you reading. The second should give the exact same output.

Quote from: almightyruler on February 18, 2015, 05:32:18 AM

Quote from: dooglus on February 18, 2015, 04:57:49 AM

You can expect to see each attempt take 0s if you only have a small number of outputs to check each 16 seconds, but the fact that you see it at all is proof that it is attempting to stake.

Looks like I just missed out on that change - updated a couple of days ago, and neither the debug log or source contain the phrase "stake took." I'll compile a newer version and see what happens.

I only made the change yesterday. It will be in v1.4.8, but no older version.

Quote from: almightyruler on February 18, 2015, 05:32:18 AM

Quote from: dooglus on February 18, 2015, 04:57:49 AM

Another thing to check is whether you have the client configured to hold your balance in "reserve". There's a setting where you can specify that you want to always keep a certain balance available, and that balance never attempts to stake. If you have it set to the same as your full balance you would see what you're seeing.

That's 'reservebalance' and as per my earlier message there is definitely none reserved.

OK.

Since you're building from source, I can push a change that logs exactly why each attempt at staking fails, have you build that, and get you to post some sample output. That will let us know for sure whether the client is really trying to stake and just being unlucky or not.

Would that be useful?