Protocol changes scheduled for Feb 20 - page 2.

Valalvax

sr. member

Activity: 437

Merit: 250

Quote from: theymos on February 18, 2012, 10:32:09 PM

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.

Quote from: MysteryMiner on February 18, 2012, 10:02:46 PM

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!

theymos

administrator

Activity: 5222

Merit: 13032

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.

Quote from: MysteryMiner on February 18, 2012, 10:02:46 PM

Safe mode means no blocks can be received and no transactions made? Lazy to look again at wiki.

Just JSON-RPC is disabled.

MysteryMiner

legendary

Activity: 1540

Merit: 1049

Death to enemies!

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.

theymos

administrator

Activity: 5222

Merit: 13032

Quote from: nibor on February 17, 2012, 04: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).

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.)

nibor

sr. member

Activity: 438

Merit: 291

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?

theymos

administrator

Activity: 5222

Merit: 13032

Quote from: etotheipi on February 14, 2012, 11:51:36 PM

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.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

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)

btc_artist

full member

Activity: 154

Merit: 102

Bitcoin!

Now would be a good time for the devs of alternative clients to make sure their clients are compatible, if they haven't already.

jim618

legendary

Activity: 1708

Merit: 1069

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 website.

theymos

administrator

Activity: 5222

Merit: 13032

5 days until the protocol change.

Looks like an alert will be issued before the change in case anything goes wrong.

theymos

administrator

Activity: 5222

Merit: 13032

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
if (GetTime() > 1329696000)
{
vSend.SetVersion(209);
vRecv.SetVersion(209);
}

(net.h)

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.

Topic: Protocol changes scheduled for Feb 20 - page 2. (Read 5840 times)