dooglus:

I'm definitely on the correct fork. Freshly compiled client is now logging information about staking...

2015-02-18 06:13:37 not tracking stake rewards yet
2015-02-18 06:13:56 not tracking stake rewards yet
2015-02-18 06:14:08 not tracking stake rewards yet
2015-02-18 06:15:45 stake took 0s
2015-02-18 06:16:01 stake took 0s
2015-02-18 06:16:17 stake took 0s
2015-02-18 06:16:33 stake took 0s
2015-02-18 06:16:49 stake took 0s
2015-02-18 06:17:05 stake took 0s
2015-02-18 06:17:21 stake took 0s
2015-02-18 06:17:37 stake took 0s
2015-02-18 06:17:41 not tracking stake rewards yet
2015-02-18 06:17:53 stake took 0s
2015-02-18 06:17:59 not tracking stake rewards yet
2015-02-18 06:18:09 stake took 0s
2015-02-18 06:18:25 stake took 0s
2015-02-18 06:18:42 stake took 0s
2015-02-18 06:18:58 stake took 0s
2015-02-18 06:19:14 stake took 0s
2015-02-18 06:19:30 stake took 0s

I guess that means each attempt is only taking a fraction of a second of CPU time, for each 16 second search interval? My wallet is fairly uncomplicated: 383 entries in total, and 2 unspent outputs (one dust). I'm used to seeing clients trying to stake consume double figure CPU percentage - sometimes even 100% - for an extended period of time.

Still doesn't explain why those attempts are not successful. The extra debugging info you mentioned would be appreciated.

BTW, can I PM you a small diff to ensure that clamd compiles cleanly under FreeBSD? I'm not familiar with git.