Pages:
Author

Topic: Bitcoin-Qt, bitcoind version 0.5.1 released (Read 6164 times)

legendary
Activity: 3066
Merit: 1145
The revolution will be monetized!
December 20, 2011, 12:14:55 AM
#25
I'm on Ubuntu subscribed to the Matt Corallo PPA but so far have seen no 0.5.1 update come down. Is that delayed or something wrong why it's not being propagated?
Thx.

Edit: I spoke too soon. A few minutes after posting the update manager showed it was coming. I guess the squeaky wheel gets the grease here. Is it normal to take 3-4 days to get recognized?
For what it's worth; Subscribing to the same PPA an Ubuntu 11.10 machine I have updated bitcoind along with all my other updates. Totally sweet. Cheesy The version 10.10 computer im on right now is not cooperating. Smiley (I'm still happy though)
hero member
Activity: 784
Merit: 1009
firstbits:1MinerQ
December 19, 2011, 11:05:09 PM
#24
I'm on Ubuntu subscribed to the Matt Corallo PPA but so far have seen no 0.5.1 update come down. Is that delayed or something wrong why it's not being propagated?
Thx.

Edit: I spoke too soon. A few minutes after posting the update manager showed it was coming. I guess the squeaky wheel gets the grease here. Is it normal to take 3-4 days to get recognized?
newbie
Activity: 54
Merit: 0
December 18, 2011, 11:56:16 PM
#23
There is something wrong.
I have copy the old 0.5 wallet to 0.5.1 and transfer bitcoins to my mt.gox account,but today there is a strange address show in my bitcoin0.5.1:1FvEPVsHmX3TjwUn4PPpwTdHcTA8BQSATE.
It show I transfer 2.12027407 BTC to that address.But I swear I haven't do it.
What's wrong with it?
legendary
Activity: 1652
Merit: 2216
Chief Scientist
December 18, 2011, 02:18:31 PM
#22
i hadn't backed up my wallet for a while and just noticed that there is now a wallet.dat and a wallet.dat.rewrite in my Bitcoin folder.  which is the real private key wallet that needs to be backed up?

wallet.dat

wallet.dat.rewrite SHOULD be automatically removed as part of the upgrade-to-0.5 process; I don't know why it isn't in some cases-- and, frankly, I would much rather spend time getting really, truly secure wallet solutions working.

RE: bitcoin version 0.4 starting up on your machine:

You should run the old bitcoin, un-check the "start on windows system startup", then exit.
Then remove it using the Add/Remove Programs control panel doo-hickey (did that move again in Vista?).  You should see both "bitcoin" (the old 0.4) and "bitcoin-qt" (the new 0.5).

... all of which is, I know, annoying and painful.  Again, frankly, I'm more interested in spending time on the very-highest-priority issues rather than making every beta release upgrade completely smooth in all cases.
legendary
Activity: 1764
Merit: 1002
December 17, 2011, 11:46:59 PM
#21
i hadn't backed up my wallet for a while and just noticed that there is now a wallet.dat and a wallet.dat.rewrite in my Bitcoin folder.  which is the real private key wallet that needs to be backed up?

I believe .rewrite is the old wallet, which ideally should be "rewritten" over since it may hold unencrypted private keys as a result of a bug in the 0.4 wallet encryption code. Ideally though if you used the built in encryption prior to 0.5 you should transfer your coins to a new wallet in case the old one has leaked.

thats a good pt.  i'm moving them now....
donator
Activity: 308
Merit: 250
December 17, 2011, 09:53:56 PM
#20
I thought I'd changed the gavinandresen.asc file on bitcoin.org to contain both keys, but it looks like I didn't (or pgp/gpg doesn't allow more than one key in the .asc file; I was disappointed to learn that gpg doesn't support putting multiple signatures in an .asc file...)
The Apache Foundation uses something they call the KEYS file: http://www.apache.org/dev/release-signing#keys-policy
donator
Activity: 853
Merit: 1000
December 17, 2011, 09:46:14 PM
#19
i hadn't backed up my wallet for a while and just noticed that there is now a wallet.dat and a wallet.dat.rewrite in my Bitcoin folder.  which is the real private key wallet that needs to be backed up?

I believe .rewrite is the old wallet, which ideally should be "rewritten" over since it may hold unencrypted private keys as a result of a bug in the 0.4 wallet encryption code. Ideally though if you used the built in encryption prior to 0.5 you should transfer your coins to a new wallet in case the old one has leaked.
donator
Activity: 2772
Merit: 1019
December 17, 2011, 09:04:03 PM
#18
Runs fine on XP, which is good for occasional use.
Sadly still fails on W2k, which is bad for constant use.

Maybe it would make sense to add an option to pause the blockchain download. That might come in handy during the initial download, when you sometimes need all resources for something else.

You can just quit the client and start it again, no problem. You'll have some overhead due to the network reconnect, but it's negligible, I'd say.
newbie
Activity: 19
Merit: 0
December 17, 2011, 04:37:55 PM
#17
updated to 0.5.1-beta
Thanks for fixing tooltips on the transaction list view!
sr. member
Activity: 252
Merit: 250
December 17, 2011, 04:35:55 PM
#16
0.5.1 works ok for me. Compiled from source, Ubuntu Linux 11.04, 64 bit.
hero member
Activity: 576
Merit: 514
December 17, 2011, 04:12:44 PM
#15
Runs fine on XP, which is good for occasional use.
Sadly still fails on W2k, which is bad for constant use.

Maybe it would make sense to add an option to pause the blockchain download. That might come in handy during the initial download, when you sometimes need all resources for something else.
legendary
Activity: 1764
Merit: 1002
December 17, 2011, 02:20:37 PM
#14
i hadn't backed up my wallet for a while and just noticed that there is now a wallet.dat and a wallet.dat.rewrite in my Bitcoin folder.  which is the real private key wallet that needs to be backed up?
legendary
Activity: 1764
Merit: 1002
December 16, 2011, 08:17:36 PM
#13
0.4 still won't go away!  automatically loads in my tray despite 0.51 download.
donator
Activity: 2772
Merit: 1019
December 16, 2011, 05:39:26 PM
#12
Awesome GUI!

I must admit I've not been looking at bitcoins gui for many months (since 0.3.x).

Congrats to all devs/testers and whoever else made this nice release possible.

Also: cool, I'm now a millionaire (in µBTC)
legendary
Activity: 2198
Merit: 1311
December 16, 2011, 02:09:37 PM
#11
I haven't run a bitcoin client in a few months now.  I just ran this one and I'm impressed with the progress.  It still takes a while to get the whole blockchain but not nearly as long as it did in the clients I ran in the past.  Also, usability has improved a lot.  Nice work.
legendary
Activity: 1652
Merit: 2216
Chief Scientist
December 16, 2011, 02:06:33 PM
#10
GPG signature bitcoin-0.5.1-macosx.dmg.asc tells me that bitcoin-0.5.1-macosx.dmg is correctly signed by key BE38D3A8, but on bitcoin.org the "PGP" link next to Gavin's name gives me a public key 1FC730C1. I just wanted to confirm that both of those keys in fact belong to Gavin.
Yes, those are both my PGP keys. I generated a new, stronger key yesterday (1FC7...) that I intend to use for code signing for the next release. I thought I'd changed the gavinandresen.asc file on bitcoin.org to contain both keys, but it looks like I didn't (or pgp/gpg doesn't allow more than one key in the .asc file; I was disappointed to learn that gpg doesn't support putting multiple signatures in an .asc file...)
legendary
Activity: 1764
Merit: 1002
December 16, 2011, 09:45:45 AM
#9
did u get that reversion to a previous password fixed?

Explain?


in v0.4 i changed my pw once.  then i installed 0.5 and encrypted the wallet.  the new pw wouldn't work; i had to use the original pw.
legendary
Activity: 1072
Merit: 1174
December 16, 2011, 05:13:56 AM
#8
did u get that reversion to a previous password fixed?

Explain?
legendary
Activity: 1148
Merit: 1001
Radix-The Decentralized Finance Protocol
December 16, 2011, 03:57:29 AM
#7
I recently tried version 5 coming from version 3 and I want to congratulate whoever made the client eat a lot less RAM. Big improvement.
hero member
Activity: 602
Merit: 501
December 15, 2011, 09:38:14 PM
#6
Thanks to everyone who was involved in this.
Pages:
Jump to: