on a more serious note.. it seems both H2C and ispace are on a different chain then cryptopia again.... I just sent 14.6BTB to my wallet from H2C and they haven't showed yet. I checked the diff and see my wallet is the same as cryptopia.(42.xx as of right now with H2c and ispace @ 36 and 37) I just did a check and repair wallet and 34 bars just popped into my wallet....wtf?! this is becoming ridiculous. i have 6 more sitting there immature that I think I am going to lose..  but where did the 34 come from and do I get to keep them?


isn't there a way to shrink the size of the wallet file by removing the transactions of orphans?

here is the Bitcoin address for donations to help with Bitbar:
17jeqzYLi7Y4QivVA32MKpqWMcRzwEmFmK

feel free to use it as much as you would like   

Is the new windows wallet coming out today?

I saw the new litebar wallet and running it now.  

I was trying to think of a way to alert the old wallets and thought of this: You know how you can see peers in a list with the console command and in that info shows the wallet version. so use that to msg old wallets. make it say like "If you are reading this you need to upgrade your wallet to xxxxxx.xxx sucka!" for the new wallet version info. But if it is a new wallet you are using the getpeerinfo command on, it shows the actual version less the "you need to" part, probably wouldn't be that hard to code. It's not perfect, but a msg would get to the old wallet if they looked at the peer list. What do you think?

It's a good idea. Most of the time if a wallet gets the wrong information, it bans the connecting wallet. same effect

It might me possible to send a small message back, but if they were to actually do a getpeerinfo - they should get a clue when they see all of theBitBar:0.7.4/ in there list.
Some people just don't get it until it's broke.

Update on the wallet.

So the daemon part is done.
new key added for checkpoint server
new key and replaced missing code for alert messages
added -zapwallettxes - removes all transactions from your wallet.dat and rescans the whole chain (this takes a while)
build  version increased to v0.4.4.xxx
client version increased to 60007

Those of you using bitbard, feel free to pull the source and start using it.

Those of you using the QT wallet, just a little longer.
I'm still working on the style sheets.
(and any problems found by our testers - thanks userpike)

That was a wild ride.
10,000 Mh slammed on a ? 300Mh network.

All the new wallets didn't like it and disconnected.

I tried the "balance" option in cgminer between the new BTB wallet and 42 wallet and its working out nicely. I've never tried the balance option before. There doesn't seem to be any problems mining solo with the new BTB wallet either.

Good work, guys. Keep BTB rolling!

Any word on whats going on with the BTB at Cryptsy?

So the windows-qt wallet release is ready.
I've sent a link to our guinea pig - I mean userpike - to see if it crashes his system  

If all goes well, I post the link here, and update Bitbar.co