I have a serious problem here with btb client. I have requested payout from
http://btb.ltcoin.net/ pool two days ago. More than 18 btb. My wallet downloads blocks, synchronizes with network, appears as synchronized and than it downloads block again. It's somehow looped. Payout does not appear in my wallet. Nothing helps. I have deleted all files (I've made back up of *.dat file), downloaded 4.03 version of client unzipped to the folder and nothing. The strange thing is that when I download 4.03 the version shown in client is v0.4.2.0g32a928e-beta. Any ideas what is wrong?
BTB already forked once and part of my miners happily mined it for days on the wrong fork (fortunately I never put 100% of my miners on altcoins). You may still be on this fork or a new one.
Updating to latest git didn't make any change so I considered this altcoin dead (if the newest client can't tell it's on a fork there's really no point to the coin).
Make sure your client matches the block height on btb.cryptocoinexplorer.com
If not, back up your wallet through the client,save file someplace else and move the copy in your data directory also. Clear everything out of your data directory except your .conf file.
In your conf file add:
This is the Cryptocoinexplorer IP address. Connect means your client will only talk to that node.
Start your client up and wait for it to sync.
Once synced, shut the client down and change the inserted line above to:
addnode means it will try to use that node, but look for other nodes as well.
move your wallet back and see if this works. You may have to use the rescan or repairwallet option to fix the wallet.
Two reasons for sync problems:
1. Too long as period of time has passed since the last block was solved. The client assumes it is out of sync.
2.One of the reasons for constant cycling occurs if the client/daemon still has the network prefix code from the coin it was forked from . This is represented by 4 2 Digit hex numbers, and allow clients to discern P2P messages from their chain regardless of port. Unfortunately this needs to be fixed at a developers level and requires a hard fork.
everything is fine now 
