|
Title: Protocol changes scheduled for Feb 20 Post by: theymos on December 27, 2011, 10:50:35 PM At midnight on February 20 (UTC), versions of Bitcoin later than 0.2.9 will automatically change the protocol:
Code: // Version 0.2 obsoletes 20 Feb 2012 It looks like the effect of this change is that all messages will now have checksums, including verack and version. Alternate clients that use the Bitcoin protocol will need to apply this change on Feb 20. Bitcoin versions 0.1.x and 0.2.[0-9] (now 2+ years old) will stop functioning as a result of this change. Title: Re: Protocol changes scheduled for Feb 20 Post by: theymos on February 14, 2012, 10:06:40 PM 5 days until the protocol change.
Looks like an alert will be issued before the change in case anything goes wrong. Title: Re: Protocol changes scheduled for Feb 20 Post by: jim618 on February 14, 2012, 10:36:31 PM For MultiBit, the update for the Feb20 change went into the version:
Version: 0.3.0Beta2 Date: 23 Jan 2012 (You can see the version number in the "Help | About MultiBit" screen). If you are running an earlier version, please update it from the http://multibit.org (http://multibit.org) website. Title: Re: Protocol changes scheduled for Feb 20 Post by: btc_artist on February 14, 2012, 11:12:41 PM Now would be a good time for the devs of alternative clients to make sure their clients are compatible, if they haven't already.
Title: Re: Protocol changes scheduled for Feb 20 Post by: etotheipi on February 15, 2012, 04:51:36 AM At least it's an easy upgrade. It amounts to changing half a line of code in Armory. I'll be pushing the update tomorrow or the next day and post on the Armory thread.
I would guess that timezones don't matter. Worst case, some users fail to connect to peers for a couple hours, but even that's a stretch (any peers in the same time will be sync'd with you) Title: Re: Protocol changes scheduled for Feb 20 Post by: theymos on February 15, 2012, 04:55:58 AM Worst case, some users fail to connect to peers for a couple hours, but even that's a stretch (any peers in the same time will be sync'd with you) It's UTC, so nodes with the correct time will all make the change at the same instant. Title: Re: Protocol changes scheduled for Feb 20 Post by: nibor on February 17, 2012, 09:40:08 PM Version 315 is the oldest listening node on the network:
http://bitcoinstatus.rowit.co.uk/ (See 1/3rd of way down a table). So should not be any big issue/chain split! Might be interesting if a few people with old clients fire them up and see what happens? Title: Re: Protocol changes scheduled for Feb 20 Post by: theymos on February 17, 2012, 09:46:14 PM Version 315 is the oldest listening node on the network: http://bitcoinstatus.rowit.co.uk/ (See 1/3rd of way down a table). Ha! That one might be me; I still run a 0.3.15 node. This node is old enough that it might go into safe mode when it receives the alert. (Versions older than 0.3.19 can have safe mode activated by alerts.) Title: Re: Protocol changes scheduled for Feb 20 Post by: MysteryMiner on February 19, 2012, 03:02:46 AM 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. Title: Re: Protocol changes scheduled for Feb 20 Post by: theymos on February 19, 2012, 03:32:09 AM 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.
Safe mode means no blocks can be received and no transactions made? Lazy to look again at wiki. Just JSON-RPC is disabled. Title: Re: Protocol changes scheduled for Feb 20 Post by: Valalvax on February 19, 2012, 03:33:50 AM 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. Safe mode means no blocks can be received and no transactions made? Lazy to look again at wiki. Just JSON-RPC is disabled. ! It's the truth! Mine has printed a message.... from the FUTURE I assume downloading the latest version as of today will solve it? Oh nevermind, reading, I can do it! Title: Re: Protocol changes scheduled for Feb 20 Post by: theymos on February 19, 2012, 03:41:39 AM 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. Title: Re: Protocol changes scheduled for Feb 20 Post by: Atheros on February 19, 2012, 04:15:44 AM 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 Title: Re: Protocol changes scheduled for Feb 20 Post by: etotheipi on February 19, 2012, 04:18:49 AM 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... Title: Re: Protocol changes scheduled for Feb 20 Post by: theymos on February 19, 2012, 04:31:27 AM 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. Title: Re: Protocol changes scheduled for Feb 20 Post by: etotheipi on February 19, 2012, 05:05:47 AM 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. Title: Re: Protocol changes scheduled for Feb 20 Post by: finway on February 19, 2012, 09:48:21 AM Good to know.
Title: Re: Protocol changes scheduled for Feb 20 Post by: muyuu on February 19, 2012, 02:47:48 PM 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. I'd bet most of these are not active users. Title: Re: Protocol changes scheduled for Feb 20 Post by: muyuu on February 19, 2012, 03:10:14 PM 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. 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%+. Title: Re: Protocol changes scheduled for Feb 20 Post by: MysteryMiner on February 19, 2012, 05:47:39 PM 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.
Title: Re: Protocol changes scheduled for Feb 20 Post by: grue on February 19, 2012, 08:15:01 PM 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 :DTitle: Re: Protocol changes scheduled for Feb 20 Post by: gmaxwell on February 19, 2012, 08:33:38 PM agreed. still using 4.1.1 :D 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. Title: Re: Protocol changes scheduled for Feb 20 Post by: MysteryMiner on February 19, 2012, 09:16:18 PM 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.Title: Re: Protocol changes scheduled for Feb 20 Post by: theymos on February 20, 2012, 12:12:47 AM Change complete! :) We'll see over the next few days how common any problems are.
Title: Re: Protocol changes scheduled for Feb 20 Post by: etotheipi on February 20, 2012, 12:13:53 AM Change complete! :) 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 :) Title: Re: Protocol changes scheduled for Feb 20 Post by: Wordlet on February 20, 2012, 02:13:46 PM Fwiw, I wouldn't use a GUI that used wxWidgets. Love the Qt version though. Guess everyone has their preferences.
Title: Re: Protocol changes scheduled for Feb 20 Post by: BookLover on February 20, 2012, 02:29:38 PM (marking) :D
Title: Re: Protocol changes scheduled for Feb 20 Post by: wumpus on February 22, 2012, 04:40:35 PM 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 :)Title: Re: Protocol changes scheduled for Feb 20 Post by: btc_artist on February 25, 2012, 05:06:26 AM 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 :)Title: Re: Protocol changes scheduled for Feb 20 Post by: coga on April 24, 2012, 02:20:28 PM 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?
Title: Re: Protocol changes scheduled for Feb 20 Post by: Atheros on April 25, 2012, 12:49:25 AM 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.
|