utahjohn i hope ur pool dont find lot blocks 
if u write a posting for each here

This is an update on the development progress.

We will be releasing version 2.0.3.1 now, that includes the following changes:

- rejects connections from version 2.0.2.1. This will block both 2.0.2.1 and 2.0.2.2, the later being harmed because it identifies as 2.0.2.1. This is necessary, because this version permits communication with older versions, that do not understand the current PoS protocol, but could inject malformed blocks in the network.

- lowers the peer penalty for "not enough work" blocks received. Originally, the penalty is set to the maximum threshold to ban the peer node. This essentially means that once you get infected you can never talk to other nodes until you junk your block chain and sync again.

- makes small correction to the sync checkpoint protocol, which seeks to reduce/eliminate the chance of arriving at this "not enough work" situation.

All these chances do not fully resolve the issues, but provide for much faster network convergence. Version 2.0.3.1 is already running on the announced permanent nodes, which has resulted in the network withstanding few more attacks.

Please note version 2.0.3.1 is not a mandatory update. You use it to save yourself some headaches, eventually.

We have identified the reason(s) for the block index corruption. The code defect is present in most (all?) ppcoin descendants, but requires specific conditions to be triggered. It so happens that Diamond is a bit more susceptible to such bad block injection, because of past data in the block chain. Both the current data corruption and the original problem are being addressed, but since this requires very slow testing, we decided to release 2.0.3.1 now in order to help some users.

We also know what is causing the "not enough work" problem. This requires a bit more complex fix, and more testing. Again, the code deficiency is not unique to Diamond.

Windows -QT
http://sourceforge.net/projects/diamonddmd/files/diamond-qt-2.0.3.1.exe/download

Mac
http://sourceforge.net/projects/diamonddmd/files/diamond-qt-2.0.3.1.dmg/download

will be updated tomorrow

Congrats to dDzf6pvTV63wFFw3nTZyGv4ZysKitnySPZ for finding 4th block
I just received first payout 1st confirmed block from pool so I can verify that is working
payments sent to:
dETfZeUtj21VyKFDCQgJEJmYspVv5z1jU4: 0.456172 (unknown)
dP4Nd5jXyQyMEunf9iXnRxRKjxsenJaeY2: 0.532829 (myself)

I'm upping the payout threshold to 1 DMD in a few hours so transaction fees don't eat me up (Seeded pool wallet to make sure transaction fees covered).

guess u minted in the fork.....


try this:
help - debug window - console
and enter the command
repairwallet

@utahjohn:

Any clue why my Linux wallet doesn't sync? It's v1.0.0.0 as I followed the source code link at the OP. diamond.conf is set.

I know but I'm on Linux and the source on github is v1.0.0.0.