Ok I see 13 of us are synced again, nice job!
So what we have to double check regarding this CPID signature feature :
1) That we have not introduced instability. Your node should not crash when syncing.
2) You should not be able to mine unless you have an active CPID on that node. You can type 'exec getboincinfo' - we use the cpid from the "CPID:" column to sign the block. That CPID also must be in the chain (in the 'exec listdccs' in column 1, that means the CPID is securely associated). If you can mine without a CPID something is wrong. Note on masternodes mining does not start until chain is synced so please be patient. Ensure HPS > 0 in getmininginfo if you have a CPID.
3) You should see the CPID and the signature on almost every block now. Type 'showblock height'. The column CPID is the signed CPID that mined the block. The Signature: true/false is if it passed the signature and the magnitude test (we require a distinct CPID that has magnitude).
4) Note: The only exception is if the block span is > 15 mins (the new late block threshhold, this means no one has solved a block in 15 mins in testnet), we do accept the block from anyone- that keeps the chain from sticking if Rosetta is down, or if no other miner with a CPID is around.
So, if you find a showblock with a missing CPID, check the HRTime and subtract that HRTime from the previous block HRTime and it should be > 15 mins. If so, things are still OK and working.
I appreciate if people can test this with me relatively thoroughly so we have no surprises in prod, lets bust that botnet successfully in one shot.