Quote from: kraizi on January 26, 2015, 04:00:17 PM

Quote from: mmpool on January 26, 2015, 08:06:08 AM

Quote from: kraizi on January 26, 2015, 06:27:48 AM

I remember reading about BIP30 a while ago so I did a search. Lots of talk about forking. Not sure if it's true but we should probably pick a direction (BIP30 or no BIP30) and stick with it to prevent problems. I'd probably go with whatever Bitcoin does to be consistent and make updates easier. Frictionless should know if it was enabled in v0.8.6. He did the update.

https://bitcointalk.org/index.php?topic=230141.msg5582659#msg5582659

Looking at the 0.8.6 source, BIP 16 and 30 was enabled for 02 Jan 2014 01:07:11 GMT. So we'll have to keep them enabled:

Code:

+ // BIP30 for Ixcoin will go into effect on 2014-01-01 0:00 UTC
+ // date -j -f "%b %d %Y" "Jan 01 2014" "+%s"
+ int64 nBIP30SwitchTime = 1388624831;

+ // BIP16 will be enabled for Ixcoin will go into effect on 2014-01-01 0:00 UTC
+ // date -j -f "%b %d %Y" "Jan 01 2014" "+%s"
+ int64 nBIP16SwitchTime = 1388624831;

I plugged the epoch into http://www.epochconverter.com/ and got the different time to the comments.

Doing some more testing I'm getting blocks rejected due to block times being in the past and future. Not sure what's happening there. This is the patch I used for diff 1 mining on a new chain: http://pastebin.com/QGM4CZWr

Run this with two ixcoin nodes connected to each other, and only each other. An ixcoin.conf like the following:

Code:

rpcuser=abcd
rpcpassword=defg
daemon=0
upnp=0
port=10333
rpcport=10332
irc=0
noirc=1
dnsseed=0
nodnsseed=1
printtoconsole=1

Make sure you use different ports/rpcports for the two. And in the 2nd node add a "addnode=127.0.0.1:10333" or whatever you set the port too, so node 2 connects to node1.

@mmpool:

I'm curious did you see this same issue when you upgraded your pool from v0.3.24 to v0.8.6? It should have occurred then too, right?

BIP30 is for preventing duplicate transactions so I assume it wouldn't be an issue with every single block generated. Are you seeing 'tried to overwrite transaction' errors on every block?

Also, I believe the majority of pool hasing power for iXcoin is still using v0.3.24. How do we get the rest of the pools migrated to v0.8.6 or v0.9.x without causing a fork? The start date in v0.8.6 is already in the past. Or is this even a fork issue?

Because the 0.8.6 client was NEVER deployed, the effective dates don't apply.

For a 0.9.x client that will be deployed, use a data that is in the future.