All you gotta do is download the new version and transfer your wallet.dat
Importing my wallet.dat (copied into the .bitcoin folder) gave me an error "wallet corrupt" upon starting bitcoin-qt (0.8.2)
Topic: May 15 omg what do I do? (Read 2147 times)
Importing my wallet.dat (copied into the .bitcoin folder) gave me an error "wallet corrupt" upon starting bitcoin-qt (0.8.2)
All you gotta do is download the new version and transfer your wallet.dat
bitcoin-qt doesn't record an error, it just locks up my machine.
After 10 or so tries, the blockchain download was complete. Importing my wallet.dat (copied into the .bitcoin folder) gave me an error "wallet corrupt" upon starting bitcoin-qt (0.8.2)
Then I opened the same wallet file with bitcoin0.6.3 and it loaded fine - I exported my private key and changed over to Electrum.
I have a lot of money tied up in bitcoin and can't have 'bugs'. Really disappointed in developers who messed things up, i.e. a mandatory update that kills functionality (they needed only to correct the block size).
After 10 or so tries, the blockchain download was complete. Importing my wallet.dat (copied into the .bitcoin folder) gave me an error "wallet corrupt" upon starting bitcoin-qt (0.8.2)
Then I opened the same wallet file with bitcoin0.6.3 and it loaded fine - I exported my private key and changed over to Electrum.
I have a lot of money tied up in bitcoin and can't have 'bugs'. Really disappointed in developers who messed things up, i.e. a mandatory update that kills functionality (they needed only to correct the block size).
Normally you provide the output of lines like
$ dmesg > bitcoin_qt_error.txt
$ cat /var/log/syslog >> bitcoin_qt_error.txt
or its contents to the developers. It is best to gather the information
closest to your incident. If you cannot figure out your problem by yourself,
you could try to reach the developers via sourceforge.net.
$ dmesg > bitcoin_qt_error.txt
$ cat /var/log/syslog >> bitcoin_qt_error.txt
or its contents to the developers. It is best to gather the information
closest to your incident. If you cannot figure out your problem by yourself,
you could try to reach the developers via sourceforge.net.
I updated from .07x to 0.8.1 on the 15th.
Bitcoin-qt starts, begins to re-index, and then locks up my Ubuntu 10.04LTS box - this machine has never locked up before, runs 24/7 - months on end.
I saw a post from another 10.04 user in one of my local lists saying he had the same issue- another member said, "update to 0.8.2...?
I updated to 0.8.2 - same thing.
Anyone?
Bitcoin-qt starts, begins to re-index, and then locks up my Ubuntu 10.04LTS box - this machine has never locked up before, runs 24/7 - months on end.
I saw a post from another 10.04 user in one of my local lists saying he had the same issue- another member said, "update to 0.8.2...?
I updated to 0.8.2 - same thing.
Anyone?
Remember Remember the Fifteenth of May-vember?
HELP
15th May has arrived and I haven't yet done anything cos I didn't get chance.
What shall I do so I can receive bitcoins?
I am not tech savvy so I dunno what I am doing.
Thanks
15th May has arrived and I haven't yet done anything cos I didn't get chance.
What shall I do so I can receive bitcoins?
I am not tech savvy so I dunno what I am doing.
Thanks
You could always visit free bitcoin sites, lol!
Sorry, I couldn't resist.
If you open up your Bitcoin client and click on "Help" you will get "About Bitcoin" and "About Qt". If I click on "About Qt I get 4.8.3 version. But if I click on "About Bitcoin" I get v0.8.1-beta.
I Assume I am already updated.
You might lose your coins by leaving them on some site with crooks . Or you may lose your coins by some computer mistake or problem. I'm not sure what is the bigger risk?
I Assume I am already updated.
You might lose your coins by leaving them on some site with crooks . Or you may lose your coins by some computer mistake or problem. I'm not sure what is the bigger risk?
Yes, as soon as there is a block that exceeds the max (expect it sooner rather than later), then your 0.4.8 will no longer take blocks.
As an aside, — the failure is not quite deterministic. It's possible that there will be some large blocks that trigger the failure in some nodes and not others. (This was one of the reasons that sticking with the 0.7 behavior was not acceptable, and also why the 0.8.1 temporary protective rule had to be so low). Not that it matters for this thread, but later you may find yourself confused if you hear mixed reports and don't know this. 
I am running qt version 4.8.3.
Sanity check. Qt is the framework. Bitcoin-Qt is an app.
You can see the version of Bitcoin-Qt by Help -> About.
I don't know about other versions, but in 0.8.0, there is no Help -> About.
There is only:
Help -> About Bitcoin
and
Help -> About Qt
Obviously, choose the first one.
I am running qt version 4.8.3.
Sanity check. Qt is the framework. Bitcoin-Qt is an application.
You can see the version of Bitcoin-Qt by Help -> About Bitcoin. [Edited, thanks Cyberdyne]
will I have difficulty receiving bitcoin and be out of sync, as described in here http://bitcoin.org/may15.html..
Yes, as soon as there is a block that exceeds the max (expect it sooner rather than later), then your 0.4.8 will no longer take blocks.
You can also use v0.4.9 backport:
- https://bitcointalksearch.org/topic/bitcoin-qt-bitcoind-may15-backport-versions-073-etc-release-candidate-3-199699
Additionally, you may also remove your hash power from any pools that do not have a stated policy of limiting blockchain bloat and let them know why.
This won't affect any user until a miner/pool creates a block big enough to break older clients again and repeat the fork. It is very easy for a pool to say "We don't need to manually alter the default 250k blocksize of Bitcoin again to purposefully create big blocks".
This won't affect any user until a miner/pool creates a block big enough to break older clients again and repeat the fork. It is very easy for a pool to say "We don't need to manually alter the default 250k blocksize of Bitcoin again to purposefully create big blocks".
Hi and thanks
I am running qt version 4.8.3.
I just downloaded and installed 0.8.1 and when I went into it, it still showed it to be version 4.8.3.
As I am installing it on 15th May, and therefore late for the deadline before 15th May, will I have difficulty receiving bitcoin and be out of sync, as described in here http://bitcoin.org/may15.html..
Please could someone help thanks again I really appreciate it.
I am running qt version 4.8.3.
I just downloaded and installed 0.8.1 and when I went into it, it still showed it to be version 4.8.3.
As I am installing it on 15th May, and therefore late for the deadline before 15th May, will I have difficulty receiving bitcoin and be out of sync, as described in here http://bitcoin.org/may15.html..
Please could someone help thanks again I really appreciate it.
15th May has arrived and I haven't yet done anything cos I didn't get chance.
Are you referring to the May 15th hard fork?
You don't need to do anything if you are using the Bitcoin-Qt/bitcoind client software v0.8.x or higher.
If you are using an older version of the client, you simply need to be using a version that supports more transactions per block. This means v0.7.3 instead and other v0.7.x you might be using. Or just go to v0.8.1.
Upgrading is simply installing the new client. It will not erase your existing wallet, so there's no wallet migration or anything like that.
You will want to make sure you have a current backup before upgrading (well, you always want to make sure you have a current backup).
So is that what you meant about "May 15th"?
If you're not running Bitcoin-qt or Bitcoind, do nothing.
If you're running Bitcoin-qt or Bitcoind version v0.8 or later (0.8.0 or 0.8.1), do nothing.
If you're running Bitcoin-qt or Bitcoind prior to v0.8 (0.7.2, 0.6.1, 0.3.24, etc), upgrade to 0.8.1 (or if you feel adventurous the 0.8.2 RC)
If you're running Bitcoin-qt or Bitcoind, apply the workaround on the may 15 page or use a backport.
If your hair is on fire: Call 911. This isn't the right place for getting help with actual emergencies.
If you're running Bitcoin-qt or Bitcoind version v0.8 or later (0.8.0 or 0.8.1), do nothing.
If you're running Bitcoin-qt or Bitcoind prior to v0.8 (0.7.2, 0.6.1, 0.3.24, etc), upgrade to 0.8.1 (or if you feel adventurous the 0.8.2 RC)
If you're running Bitcoin-qt or Bitcoind, apply the workaround on the may 15 page or use a backport.
If your hair is on fire: Call 911. This isn't the right place for getting help with actual emergencies.
HELP
15th May has arrived and I haven't yet done anything cos I didn't get chance.
What shall I do so I can receive bitcoins?
I am not tech savvy so I dunno what I am doing.
Thanks
15th May has arrived and I haven't yet done anything cos I didn't get chance.
What shall I do so I can receive bitcoins?
I am not tech savvy so I dunno what I am doing.
Thanks
Jump to: