It looks like the node removed was:
addnode=69.85.86.195


I removed this from the .conf file, restarted the client, but the error message was still there. I'll wait for the next version. Everything else seems to work well.

I deleted all except for the wallet and my .conf file (c/w with the revised addnodes) and re-downloaded the blockchain to correct the problem. I was able to re-create the problem on several different computers and cure it.

Jays Jerky and Treats will now accept Bottlecaps

http://jaysjerkyandgoodies.com/

Support this great site as it accepts
BTC, LTC, FRK and now CAP's

Im sure you can handle it look forward to seeing your project! And thank you to all the bottlecaps supporters.

Yes the checkpoint warning did come back into effect today. Its a protection only necessary in the early life of the blockchain.

I will go ahead and add the new checkpoints to the source and they will be included n the client released 7-30-13.

 There is nothing to worry about if you are receiving the warning it is just a notification to the developers that checkpoints are needed soon. All updated clients should have not seen the warning until just today. When PoS is fully active on the network the need for the checkpoints will decrease and we can implement another system

My apologies for your frustration. I will make announcements in the future if the warning will be present

As far as the new client not fixing the issue.

The warning was removed by the original developer. When i took over i felt this was not the correct way of going about it. I added the warning back in so we would stay notified of when checkpoints are needed. We are looking into a checkpointing system but want to keep it as decentralized as possible

That behavior is typical of a wallet not in sync.  So if your wallet is in sync it leads me to believe your Tx is omitted from new blocks, and thus isn't being confirmed via PoW.  I would suggest to make sure your wallet is definitely in sync.  Next, perhaps a delete of blkindex.dat and peers.dat to force the Tx to be submitted into the CAP network.  If you have any CAP in that wallet, send 1 CAP to anyone.  Sometimes receiving/sending a PoS coin will trigger a quick scan of all past Tx with network and will force a re-submit of your Tx above.

-Merc

Does anyone want me to start a pool I can do p2pool or stratum

Yes. If you can get p2pool working for botttlecaps I would immediately point hashpower your way

Edit:


Yeah, it appears that got off about 12 hours ago. Real excited about wasting all that hash power 

How is that even possible ?  Glad I wasn't mining , going to pause on bottlecaps , too many issues .

Hey  I have to say the transaction may have gone though ....

I'm blowing my own whistle here guys but Nibble is about the release one of the most stable clients currently out there

https://bt.irlbtc.com/view/216637.0

Team digitalindustry nearly took Nibble PoS , I'm glad we did not bloat the client and , we are using an ultra low fee structure .

Feel free to come download have a look , we intend to show you how effective management can provide security and all that the end user wants .

A rising price and security , PoS provides no security against someone with no "stake motive" , the biggest threat to an active Cryptocurrency team is not stakeholders , but  Government agencies of course , that work directly for commercial fiat banking interests ,  none of this is addressed by PoS , and look at the fee structure , and client bloat ?

The user wants a Secure cryptocurrency with an efficient client , low fees , that is now/soon Nibble .

The time to be fixing this stuff is now, when if attacked we can roll back the BC , we know any attacker now  has not " stake motive " .