New 3.2.0.0 wallets now available at britcoin.xyz. (You might consider v3.1 to be the failed attempt to mine the new coins earlier.)
Note that the location of our github repo has changed from greenmo000's account to https://github.com/britcoin3/britcoin3.2/
These new wallets will stake up the new 10 million coins for the investor, no matter who gets that block. It will happen at block 1,020,000 which could be found in about a week from now, so be sure to upgrade your wallets before then.
Linux/VPS users will also note that the annoying "Tor: Exit policy" message has disappeared :8]
And we've finally made the in-wallet logo not have a jaggy edge ;8]
Other, more major changes have been postponed until the next release in order to get this one out without any more delay.
Thanks to xCore and mammix2 for the help with these wallets. And thanks to all of you for your patience, Britcoin holders!
Note that the location of our github repo has changed from greenmo000's account to https://github.com/britcoin3/britcoin3.2/
These new wallets will stake up the new 10 million coins for the investor, no matter who gets that block. It will happen at block 1,020,000 which could be found in about a week from now, so be sure to upgrade your wallets before then.
Linux/VPS users will also note that the annoying "Tor: Exit policy" message has disappeared :8]
And we've finally made the in-wallet logo not have a jaggy edge ;8]
Other, more major changes have been postponed until the next release in order to get this one out without any more delay.
Thanks to xCore and mammix2 for the help with these wallets. And thanks to all of you for your patience, Britcoin holders!
I'm afraid the OSX one isn't working. This is what I get: http://imgur.com/a/6gqze
The GUI pops up earlier than expected but with the splash screen still in front with no tx in it and that error appears behind it.
If I run the previous version, there's no issue at all.
Hi mate,
Looks like it is caused by the latest wallet using DB4, some of the much older wallets were built using DB5. Best way to get around this is to run an old wallet and export the private keys then import into the newest wallet.
Hope this helps.
