Join Testnet , Solve fork

lizhi

Hi , it offers perfect performan.
When 0.11.2 create a block version 4, 0.9.3.1 accept it . Look at these beautiful blocks.

height = 955, version=4
height = 954, version=2
height = 953, version=4
height = 950, version=2

feathercoin-cli -testnet getblockhash 955
feathercoin-cli -testnet getblock 03d71ecc20a6803c48f623287eba56825e8cf36b4a5d58ebb454849802a4406e
{
“hash” : “03d71ecc20a6803c48f623287eba56825e8cf36b4a5d58ebb454849802a4406e”,
“confirmations” : 2,
“size” : 296,
“height” : 955,
“version” : 4,
“merkleroot” : “c65b508d734a1836fce8e63e2109b94a5c408cde7616afc9bb2584df9ce66d20”,
“tx” : [
“c65b508d734a1836fce8e63e2109b94a5c408cde7616afc9bb2584df9ce66d20”
],
“time” : 1459318296,
“nonce” : 331925,
“bits” : “1e0fffff”,
“difficulty” : 0.00024414,
“chainwork” : “000000000000000000000000000000000000000000000000000000006bb156e8”,
“previousblockhash” : “c3848614ca059f4a215355b463b4e828bf5c9f0babcafea22adcdee3633ec57a”,
“nextblockhash” : “84e7ceacc48ba1eaacac9f90bd62cfae67192a3c32f58d8a8f818da72fbd8f60”
}

feathercoin-cli -testnet getblockhash 954
feathercoin-cli -testnet getblock c3848614ca059f4a215355b463b4e828bf5c9f0babcafea22adcdee3633ec57a
{
“hash” : “c3848614ca059f4a215355b463b4e828bf5c9f0babcafea22adcdee3633ec57a”,
“confirmations” : 4,
“size” : 337,
“height” : 954,
“version” : 2,
“merkleroot” : “cb7059dcc358ca847c9c2690baeb1d09f9513ae8840c8c49f7bf88c53a6a2691”,
“tx” : [
“cb7059dcc358ca847c9c2690baeb1d09f9513ae8840c8c49f7bf88c53a6a2691”
],
“time” : 1459318018,
“nonce” : 119865,
“bits” : “1e0fffff”,
“difficulty” : 0.00024414,
“chainwork” : “000000000000000000000000000000000000000000000000000000006ba156e7”,
“previousblockhash” : “71167387cc61eee4319dac176672939666d45e97897f992924d2b969e408de36”,
“nextblockhash” : “03d71ecc20a6803c48f623287eba56825e8cf36b4a5d58ebb454849802a4406e”
}

feathercoin-cli -testnet getblockhash 953
feathercoin-cli -testnet getblock 71167387cc61eee4319dac176672939666d45e97897f992924d2b969e408de36
{
“hash” : “71167387cc61eee4319dac176672939666d45e97897f992924d2b969e408de36”,
“confirmations” : 6,
“size” : 296,
“height” : 953,
“version” : 4,
“merkleroot” : “6d20e1be50d0c416e96713aca9710a54e79dd8d52b70f6c0f31762d6d7805b77”,
“tx” : [
“6d20e1be50d0c416e96713aca9710a54e79dd8d52b70f6c0f31762d6d7805b77”
],
“time” : 1459317665,
“nonce” : 330294,
“bits” : “1e0fffff”,
“difficulty” : 0.00024414,
“chainwork” : “000000000000000000000000000000000000000000000000000000006b9156e6”,
“previousblockhash” : “699b216d74e609c728a7a97d68f5d0d0c7f91b80836b333bd10161fde54af325”,
“nextblockhash” : “c3848614ca059f4a215355b463b4e828bf5c9f0babcafea22adcdee3633ec57a”
}

lizhi

the pool that run 0.11.2 and the pool that run 0.9.3.1 , both are right .

0.9.3.1 daemon
alt text

0.11.2.0 daemon
alt text

lizhi

Fix testnet , upgrade to 0.11.2.1
https://github.com/FeatherCoin/Feathercoin/commit/4d32222f7fba8d6990dcac4e9f20152232a1d0c0

Download 0.11.2.1
http://www.ftc-c.com/pack4/feathercoin-setup.exe

lizhi

if tesnet is all right, next, I will broadcast version 4 on mainnet

AcidD

@lizhi have you compiled a linux version for the testnet ?

I have 0.11.2.1 compiled on Centos7, but it wont connect to the testnet.

I keep getting this in my /testnet3/debug.log

2016-04-01 17:09:37 ERROR: invalid header received
2016-04-01 17:09:37 ProcessMessages(headers, 95097 bytes) FAILED peer=1
2016-04-01 17:10:07 PROCESSMESSAGE: pfrom->nVersion=0,msg.hdr.pchMessageStart=7c
2016-04-01 17:10:07 PROCESSMESSAGE: ERRORS IN HEADER inv peer=2,fMagic=0
2016-04-01 17:10:09 PROCESSMESSAGE: pfrom->nVersion=70003,msg.hdr.pchMessageStart=daafa5badaafa5ba706f6e67
2016-04-01 17:10:15 PROCESSMESSAGE: pfrom->nVersion=0,msg.hdr.pchMessageStart=7c
2016-04-01 17:10:15 PROCESSMESSAGE: ERRORS IN HEADER inv peer=2,fMagic=0
2016-04-01 17:10:55 PROCESSMESSAGE: pfrom->nVersion=0,msg.hdr.pchMessageStart=7c
2016-04-01 17:10:55 PROCESSMESSAGE: ERRORS IN HEADER inv peer=2,fMagic=0
2016-04-01 17:12:09 PROCESSMESSAGE: pfrom->nVersion=70003,msg.hdr.pchMessageStart=daafa5badaafa5ba706f6e67

AcidD

I downloaded the windows version @lizhi with your link.

my debug.log says this

2016-04-02 11:41:09 CalculateNextWorkRequired.5 RETARGET
2016-04-02 11:41:09 nTargetTimespan = 60    nActualTimespan = 240
2016-04-02 11:41:09 Before: 1e0259cc  00000259cc000000000000000000000000000000000000000000000000000000
2016-04-02 11:41:09 After:  1e096730  0000096730000000000000000000000000000000000000000000000000000000
2016-04-02 11:41:09 GetNextWorkRequired.2 Difficulty rules regular blocks,nHeight=629,nInterval=1,nHeight nInterval=0
2016-04-02 11:41:09 GetNextWorkRequired.3 Difficulty pindexFirst->nHeight=627,nInterval=1,nHeight=629
2016-04-02 11:41:09 CalculateNextWorkRequired.1 nActualTimespan = 4007  before bounds
2016-04-02 11:41:09 CalculateNextWorkRequired.3 RETARGET: >nForkThree nActualTimespanShort = 6114, nActualTimespanMedium = 1881, nActualTimespanLong = 589, nActualTimeSpanAvg = 2861, nActualTimespan (damped) = 760
2016-04-02 11:41:09 CalculateNextWorkRequired.5 RETARGET
2016-04-02 11:41:09 nTargetTimespan = 60    nActualTimespan = 240
2016-04-02 11:41:09 Before: 1e0259cc  00000259cc000000000000000000000000000000000000000000000000000000
2016-04-02 11:41:09 After:  1e096730  0000096730000000000000000000000000000000000000000000000000000000
2016-04-02 11:41:09 ContextualCheckBlockHeader,block.nBits=503483378,GetNextWorkRequired=503932720
2016-04-02 11:41:09 ERROR: ContextualCheckBlockHeader: incorrect proof of work
2016-04-02 11:41:09 AcceptBlockHeader ContextualCheckBlockHeader Fail.
2016-04-02 11:41:09 Misbehaving: 115.29.37.248 (0 -> 100) BAN THRESHOLD EXCEEDED
2016-04-02 11:41:09 ERROR: invalid header received
2016-04-02 11:41:09 ProcessMessages(headers, 111216 bytes) FAILED peer=9
2016-04-02 11:41:11 PROCESSMESSAGE: pfrom->nVersion=0,msg.hdr.pchMessageStart=daafa5badaafa5ba76657273696f6e
2016-04-02 11:41:11 receive version message: /Satoshi:0.9.3.1/: version 70003, blocks=2000, us=88.97.72.134:53292, peer=10
2016-04-02 11:41:11 PROCESSMESSAGE: pfrom->nVersion=70003,msg.hdr.pchMessageStart=daafa5badaafa5ba76657261636b
2016-04-02 11:41:12 PROCESSMESSAGE: pfrom->nVersion=70003,msg.hdr.pchMessageStart=daafa5badaafa5ba61646472
2016-04-02 11:41:12 PROCESSMESSAGE: pfrom->nVersion=70003,msg.hdr.pchMessageStart=daafa5badaafa5ba706f6e67
2016-04-02 11:41:14 PROCESSMESSAGE: pfrom->nVersion=70003,msg.hdr.pchMessageStart=daafa5badaafa5ba68656164657273
2016-04-02 11:41:14 GetNextWorkRequired.2 Difficulty rules regular blocks,nHeight=630,nInterval=1,nHeight nInterval=0
2016-04-02 11:41:14 GetNextWorkRequired.3 Difficulty pindexFirst->nHeight=628,nInterval=1,nHeight=630
2016-04-02 11:41:14 CalculateNextWorkRequired.1 nActualTimespan = 4606  before bounds
2016-04-02 11:41:14 CalculateNextWorkRequired.3 RETARGET: >nForkThree nActualTimespanShort = 5291, nActualTimespanMedium = 1919, nActualTimespanLong = 598, nActualTimeSpanAvg = 2602, nActualTimespan (damped) = 695
2016-04-02 11:41:14 CalculateNextWorkRequired.5 RETARGET
2016-04-02 11:41:14 nTargetTimespan = 60    nActualTimespan = 240
2016-04-02 11:41:14 Before: 1e028bf2  0000028bf2000000000000000000000000000000000000000000000000000000
2016-04-02 11:41:14 After:  1e0a2fc8  00000a2fc8000000000000000000000000000000000000000000000000000000
2016-04-02 11:41:14 GetNextWorkRequired.2 Difficulty rules regular blocks,nHeight=630,nInterval=1,nHeight nInterval=0
2016-04-02 11:41:14 GetNextWorkRequired.3 Difficulty pindexFirst->nHeight=628,nInterval=1,nHeight=630
2016-04-02 11:41:14 CalculateNextWorkRequired.1 nActualTimespan = 4606  before bounds
2016-04-02 11:41:14 CalculateNextWorkRequired.3 RETARGET: >nForkThree nActualTimespanShort = 5291, nActualTimespanMedium = 1919, nActualTimespanLong = 598, nActualTimeSpanAvg = 2602, nActualTimespan (damped) = 695
2016-04-02 11:41:14 CalculateNextWorkRequired.5 RETARGET
2016-04-02 11:41:14 nTargetTimespan = 60    nActualTimespan = 240
2016-04-02 11:41:14 Before: 1e028bf2  0000028bf2000000000000000000000000000000000000000000000000000000
2016-04-02 11:41:14 After:  1e0a2fc8  00000a2fc8000000000000000000000000000000000000000000000000000000
2016-04-02 11:41:14 ContextualCheckBlockHeader,block.nBits=503497286,GetNextWorkRequired=503984072
2016-04-02 11:41:14 ERROR: ContextualCheckBlockHeader: incorrect proof of work
2016-04-02 11:41:14 AcceptBlockHeader ContextualCheckBlockHeader Fail.
2016-04-02 11:41:14 Misbehaving: 115.29.37.248 (0 -> 100) BAN THRESHOLD EXCEEDED
2016-04-02 11:41:14 ERROR: invalid header received
2016-04-02 11:41:14 ProcessMessages(headers, 111135 bytes) FAILED peer=10

I have tried whitelisting that IP with -whitelist=115.29.37.248 but nothing happens

lizhi

Yes. I’ve noticed this information, and I think some code needs to be checked in the testnet.

lizhi

I solve your issues , fix CalculateNextWorkRequired on testnet
https://github.com/FeatherCoin/Feathercoin/commit/4604c4d856e83d7e80d9fd18eca9f6d8a4417a08

download 0.11.2.1 on windows
http://www.ftc-c.com/pack4/feathercoin-setup.exe

AcidD

Thanks Lizhi, I’ll try to test this as soon as possible.

Wellenreiter

@lizhi said:

if tesnet is all right, next, I will broadcast version 4 on mainnet

Lizhi, please wait with the announcement for the main net, until

you are sure, that the 11.2.1 pool found a block with BIP66 and 0.9.3.1 accepted it
I didn’t check your blocks in detail.
we have no more clients with version 0.8.7, 0.8.7.1 or 0.8.7.2 in the main network.
There are still many of them in my peers list.
Also the Android version of the wallet is at equivalent of 0.8.7 and needs an update first

The last point probably is the hardest one to archive, as currently I’m the only one trying to maintain the Android wallet and Java/Android programming is not really one of my skills.

Any Java/Android programmers willing to help out there?

Please contact me

lizhi

Our 0.11.2 work , it can sync all blocks.

lizhi

When miners find out a block version 4, 0.9.3.1 client make a alert info “Warning: This version is obsolete, upgrade required!”

Wellenreiter

@lizhi
That is good :)

It is the expected behaviour.The next step is to keep mining with both versions, but slowly move more and more miners to 0.11.x. As far as I understood, the 'old clients should be obsoleted, as soon as more than 95% of the hash rate is on the new version.
The question is, if this woks smooth, or if we get a fork in the testnet during this step.