Quote from: AmazingDreams on September 21, 2014, 08:10:55 AM

Hi all,

I'm the one who created this coin for the devs. I tested the following on a local testnet:

I mined some zero reward blocks and indeed the daemon did not tell me about these. They did not show up on the listtransactions list as either generate or immature transactions. Then I changed the 8000 blocks to some low value on this line to 20 or whatever blocks I already mined: https://github.com/Checkcoin/checkcoin/blob/master/src/main.cpp#L1327 Recompiled and rebooted the daemons and started mining again. This time transactions were showing up on the listtransactions list.
Anyone can repeat this test if you can change a number, compile your own wallet and run two instances as a different user. (Finding blocks is easy on testnet)

Here is what I personally think about this 'issue':
Transactions with a value of 0 are worthless, they can never ever be referenced as input transactions. Thus they are a waste of bits and are not stored in the wallet (but they are in the blockchain).

My test proves that the 'findblock' will work after block 8000. Perhaps the blocks currently found and registered in the pools are due to the nFees being some non-zero value. Mind that the transaction volume is so low that tx
fees are not necessary yet. Though I am interested in an example where zero reward blocks are showing up in a pool. This will help tell me whether this is because of something I changed myself or it is something much deeper in the wallet core that should not be touched anyway.

I suggested to the dev's changing the block reward to 1 satoshi until block 8000, so you guys know that it's all working properly.

Just to confirm. AmazingDreams is one of the developers working on Checkcoin.