GMC 2.0 is not compatible with 2.5 about go-musicoin HOT 10 CLOSED

Is the above error from GMC 2.0? I suggest upgrading to 2.5.

from go-musicoin.

I think it's from v2.5.1 https://github.com/Musicoin/go-musicoin/releases/tag/v2.5.1

from go-musicoin.

testing with latest parity 1.8.9 stable and gmc 2.5.3 stable

from go-musicoin.

I upgraded web app's client to 2.5.1 smoothly two days ago, not sure what's wrong with their side.

from go-musicoin.

it's probably parity issue, I don't see difference in gmc 2.0 and 2.5

from go-musicoin.

can I see the full log from above? In general this just means a client submits a bad block, this is not an issue unless the client totally stops syncing.

from go-musicoin.

Confirmed consensus issues between GMC 2.0.0 and 2.5.3. Please use 2.5.x

from go-musicoin.

I have at least two 2.0 peers that actually are compatible with 2.5:

Version                                                              Header
----------------------------------------------------------------------------------
GMC/v2.6.0-beta-3fd25c0f/linux-amd64/go1.8.3                         d7ac0f…4fa3ee
GMC/music.miningpond.com/v2.5.1-stable-039a2d99/linux-amd64/go1.7.5  d7ac0f…4fa3ee
GMC/v2.5.3-stable-69422700/linux-amd64/go1.7.3                       d7ac0f…4fa3ee
GMC/v2.5.0-unstable-105239b9/linux-amd64/go1.8.3                     d7ac0f…4fa3ee
GMC/v2.5.3-stable-69422700/linux-amd64/go1.7.3                       d7ac0f…4fa3ee
GMC/v2.0.0-stable-d849d276/windows/go1.7.3                           d7ac0f…4fa3ee
GMC/v2.0.0-stable-8b31cac1/linux/go1.7.5                             d7ac0f…4fa3ee

See header hash. This is seen from Parity 1.8.9 which is also compatible.

from go-musicoin.

I'm confused, tracing back some history to see what's the clue. On musicoin.org web, the 2.5.1 upgraded smoothly upon the first moment of reported bad block issue. It's not even resync but continued from existing databsae. Not the same to Bittrex though.

from go-musicoin.

I'm also confused. I suspect that we have an unclear versioning at this time. See the two 2.0 nodes in my screenshot have different commits. There might be even more.

from go-musicoin.