Topic: [BTB] The BitBar Information Thread - page 25. (Read 180352 times)

I got the same message about being fixed - but it's not. They are about 1100 blocks behind - must be on a fork.

I made a new ticket and asked them to remove everything but their wallet.dat and bitbar.conf files and re-sync.

missing? how it could be?

Here is the new windows-qt wallet bitbar-qt_v04_4_005.zip

This is a mandatory update:
Why ?
The checkpoint functions have been enabled, and we will have a checkpoint server up and running in a few days.
I've sent the private key to CCE so that our official node can also be the master node/checkpoint server.
Because lukemarshall paid for the CCE sponsorship - he has to give CCE permission for the changes, and it might take a few days for luke to get in touch.


Some of the other updates are:
Coin control - so you can join smaller blocks of bitbar's into larger blocks - like 20 BTB blocks for staking.
Staking icon - let's you know if your are staking, and gives a (very) rough guess as to how long your wait is before you stake - not when you get rewards, but when you can actually stake.
Zap wallet  -  This will remove all of the transactions out of your wallet, then re-scan through the entire chain for confirmed transactions. It WILL take a while, and your wallet will need to be restarted.

I added color to the wallet and added a link to the Bitbar logo so when you click on it, your web browser will open up to our Bitbar.co website.

I think that should do for a while, although I've been thinking about making the wallets skin-able, so you can choose different designs or colors..
Maybe adding a small chat window - opposite side from the logo ??

Thoughts?

Well Cryptopia's Bitbar exchange wallet is about 900 blocks behind what it should be.
I'll submit a ticket to let them know - you should submit one also with the tx and amount, just to be safe.

I know that there Bitbar pool wallet is down, last I checked the exchange wallet was ok.
I'll look into it.

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

Haven't heard a thing about cryptsy since the site went down.
I pretty much wrote off my losses there. damn it.

Good work, guys. Keep BTB rolling!

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

nice.

The new wallet is about ready -
I added the zapwallet to the wallet menu, and it works nice, I can't figure out how to clear and reload the transactions table.

I might just leave it that way. All you have to do is shut down the wallet and start it back up again.

At least you don't have to use a command prompt (cmd) to zap the wallet - you just do it in the GUI, then restart the wallet.

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.

alert = ""
to temporarily mask the 'checkpoint to old' message

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

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

Net Hashrate
10,317.25 MH/s

So far our block explorer seems to be keeping up with the blocks coming in about 10 seconds apart.

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)

Well, the Cryptopia pools hash rate is 2.48 GH/s
Current Block: 163508
Difficulty: 30.05880266

the rest of us have a hash rate of 552.57 MH/s
Current Block: 163697
Difficulty: 31.90737198

Cryptopia works with two wallets, one for the pool and one for the exchange. Their exchange wallet still matches us - so that's good.
I asked Hex to update the pool's wallet and resync.

When total network hash is 552 Mh you can't throw 2,000 Mh (2 Gh) on it

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 the /BitBar:0.7.4/ in there list.
Some people just don't get it until it's broke.

holy crap.. theres over 1000MH on the wrong btb chain over @ H2C right now...

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?

The one for Litebar has.

The one for Bitbar is about done. I had to back up a few steps and delete the rounded corners on the tooltips (popup discriptions) and get rid of the font changes because, while it worked awesome on the linux qt wallets, it looked like crap on the windows wallets.
The pop up tips didn't fit the fonts.

I've been running the new wallet to test it and so far so good.

I'm thinking about restricting the older wallets from connecting so they are forced to update. If I do that, I should probably put out a warning, but since they haven't updated anyway - they probably don't know about the update ...

Is the new windows wallet coming out today?