Quote from: presstab on July 03, 2015, 07:34:44 PM

Quote from: mchrist152 on July 03, 2015, 07:20:23 PM

Quote from: Crestington on July 03, 2015, 06:00:03 PM

Quote from: presstab on July 03, 2015, 04:53:18 PM

Quote from: Derek492 on July 03, 2015, 04:46:36 PM

So the fork will be at about 85,000 blocks from now?

I am coding in the fork as we speak. I have set it for:

Code:

static const unsigned int FORK_TIME = 1438444800; // Sat, 01 Aug 2015 16:00:00 GMT

This is a time and date when I will be available to provide some QR code if needed (quick response Tongue

)

Watch https://github.com/presstab/Mintcoin-Desktop-Wallet/commits/master today if you want to watch the fork commits. It will be merged with the main mintcoin repo after proper scrutiny.

I would suggest that if coding in a fork to also bump the protocol number and reject old clients once the fork is in effect. Even if the fork is set a month in advance, there are many that would not upgrade and will just use their old client and this can lead to chain conflicts, stuck blocks. If you reject old protocols then they will not be able to sync with the rest of the network, this is fine because if someone cannot sync, they will come here anyways and ask why, realize they need to be on the latest version and upgrade and back up to speed. If you do not reject old clients then they may be able to sync, it won't be apparent they need to upgrade and won't so it's best not to allow that to happen.

You can add it to the main.cpp file and Block old clients based on time and protocol number, this is an example from PayCon.

if (nTime > 1430124800 && pfrom->nVersion < 70122)
{
// Since February 20, 2012, the protocol is initiated at version 209,
// and earlier versions are no longer supported
printf("partner %s using obsolete version %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->nVersion);
pfrom->fDisconnect = true;
return false;
}

I agree with this completely. People don't always pay attention to wallet releases and if the wallet appears to be working normally they just let it go. This will let them know that they need to upgrade.

Don't worry this is all already covered in the fork commit.

All good, was just making sure. I had people still on old versions months later and since there was an original OP I couldn't control, there were also people trying to download there too but they could never connect and ask about it, I'd ask them what version it was and if they didn't know I'd get them to post a picture (It's also helpful if there are some cosmetic changes too) and then can just get them sorted and on the right version.