Topic: Protocol changes scheduled for Feb 20 (Read 5818 times)
My slightly older client was getting stuck too- it is because of the new P2SH transactions being included in blocks. I'm not sure if this is the case for you, but it would be very wise to upgrade regardless- the old clients are not receiving small and medium bug fixes. Surly soon they won't receive large bug fixes either.
My 0.4.1.1 got stuck, and I cannot get past this block: http://vvcap.net/db/2IR75OWyJj5AsUW7eo_i.htp . Is that end of life for non-qt client?
Quote
If there are things that the new GUI does poorly
It wastes space, are difficult to use (farther mouse travel etc.) looks unintuitive and childish. There is no fix that will make Qt version as good as VX.
Fwiw, I wouldn't use a GUI that used wxWidgets. Love the Qt version though. Guess everyone has their preferences.
Thanks 
Quote
If there are things that the new GUI does poorly
It wastes space, are difficult to use (farther mouse travel etc.) looks unintuitive and childish. There is no fix that will make Qt version as good as VX.Fwiw, I wouldn't use a GUI that used wxWidgets. Love the Qt version though. Guess everyone has their preferences.
Thanks 
(marking) 
Fwiw, I wouldn't use a GUI that used wxWidgets. Love the Qt version though. Guess everyone has their preferences.
Change complete! We'll see over the next few days how common any problems are.
We'll see over the next few days how common any problems are.FYI... Armory switched over 15 minutes early for some reason. But it works now. If there's any problems, just restart... stuff
Change complete! We'll see over the next few days how common any problems are.
We'll see over the next few days how common any problems are. 
Quote
If there are things that the new GUI does poorly
It wastes space, are difficult to use (farther mouse travel etc.) looks unintuitive and childish. There is no fix that will make Qt version as good as VX. 
agreed. still using 4.1.1
If there are things that the new GUI does poorly, please open issues on them: https://github.com/bitcoin/bitcoin/issues
There are many people willing to work on and maintain the QT interface. If there are objective weaknesses that are bugging you they will probably be fixed. (On matters of taste— well, no promises... Its no good making one user happy only to make another unhappy).
No one is maintaining the WX gui anymore. No one is willing to do so. It's even a pain to build.
Speaking about version, I will use 0.4.1 as long as it works. Hundreds of transactions with it and still working fine. The Qt version is turned out to be crap.
agreed. still using 4.1.1
Speaking about version, I will use 0.4.1 as long as it works. Hundreds of transactions with it and still working fine. The Qt version is turned out to be crap.
The version charts are very interesting. Most popular version is "stable" version 502 but the majority is still on 323 and 324. Probably they are people who joined the Bitcoin in first half of 2011 and still are running the software. There are few running 401.
Safe mode means no blocks can be received and no transactions made? Lazy to look again at wiki.
Safe mode means no blocks can be received and no transactions made? Lazy to look again at wiki.
I'd bet most of these are not active users.
3.23 beta here and very active... over 2000 transactions on just this laptop....
Cool, that proves it's not 100%. Still, I'd bet most of these are not active, defining most as 50%+.
The version charts are very interesting. Most popular version is "stable" version 502 but the majority is still on 323 and 324. Probably they are people who joined the Bitcoin in first half of 2011 and still are running the software. There are few running 401.
Safe mode means no blocks can be received and no transactions made? Lazy to look again at wiki.
Safe mode means no blocks can be received and no transactions made? Lazy to look again at wiki.
I'd bet most of these are not active users.
Good to know.
Where is this being displayed? I have had the client open in Ubuntu 10.04 for days (Satoshi version 0.5.0), and I see no alert anywhere. I always wondered how the alerts work...
The GUIs of some early versions of bitcoin-qt don't display alerts. You'll still see it in JSON-RPC getinfo, though.
I upgraded to 0.5.2 and I see the alert now. It's tough to miss.
Where is this being displayed? I have had the client open in Ubuntu 10.04 for days (Satoshi version 0.5.0), and I see no alert anywhere. I always wondered how the alerts work...
The GUIs of some early versions of bitcoin-qt don't display alerts. You'll still see it in JSON-RPC getinfo, though.
An alert has been sent. Nearly every Bitcoin client is now printing "See bitcoin.org/feb20 if you have trouble connecting after 20 February" somewhere.
Where is this being displayed? I have had the client open in Ubuntu 10.04 for days (Satoshi version 0.5.0), and I see no alert anywhere. I always wondered how the alerts work...
When I last ran my statistics collecting program on 14 February, it caught these older nodes:
0.3.11 - One client
0.3.02 - Two clients
0.3.00 - One client
http://bitcoinstats.org/versions.html
0.3.11 - One client
0.3.02 - Two clients
0.3.00 - One client
http://bitcoinstats.org/versions.html
I assume downloading the latest version as of today will solve it?
No action is required right now. The alert is in case something bad happens on Feb 20.
Jump to: