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:
+ // 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.
Reviewing the posts here, and realized this was the correct answer, we need the same as v8, so was changing the code to the correct value, based on the date, and got this:
Epoch timestamp: 1388534400
Timestamp in milliseconds: 1388534400000
Human time (GMT): Wed, 01 Jan 2014 00:00:00 GMT
Upon running the value apparently programmed, we get a date/time of the following for int64 nBIP30SwitchTime = 1388624831;
GMT: Thu, 02 Jan 2014 01:07:11 GMT
...is that what everybody wants then for BIP30 testing? Or the date as listed, with the correct value, or some future date? Hate to have to keep changing this.
On the BIP16 test, bitcoin uses this value :
// BIP16 didn't become active until Apr 1 2012
int64_t nBIP16SwitchTime = 1333238400;
Guess what, the comment and value match. From our v8 listed above, I would say the comment states one date, while the value specifies another, same as BIP30, whatever you guys want, is fine by me...
I just want the comment to match the value, and have both BIP16 and BIP30 work for us too.
@mmpool - Thanks for the epochconverter link, great tool.