Feathercoin Fork

bsotnikow

Thanks! Creating a .conf file worked. I’m synced again.

bsotnikow

If its transaction related, I wonder if increased traffic from the recent price spike and trade volume contributed.

GMC

@ghostlander
Where do we stand? At give-me-coins we have been mining a bunch of blocks with 0.9.3.

ghostlander

@GMC You have also mined a bunch of orphans. 14 of the last 30 FTC blocks found by your pool prior to the fork were orphans. 47% miss rate is something to think about.

RIPPEDDRAGON

Bittrex is having issues related to this as an fyi

@Bushstar miss you!

GMC

@ghostlander True. But we tested 0.11.2 and had problems also. And staying with 0.8.7 represented a risk also.

ghostlander

@GMC What risk? The basic functionality including the ACP is the same.

GMC

@ghostlander If I recall correctly, 0.8.7 doesn’t allow v3 blocks. With 0.11.2 out, a v3 block could be mined at any moment stopping all v0.8.7 wallets. That sounds like a risk to me.

ghostlander

@GMC Speaking technically, v3 (DERSIG/BIP66) and v4 (CHECKLOCKTIMEVERIFY/BIP65) are forced by v0.11 only when 95% of the network produce these blocks. However v0.8 rejects anything other than v2 for a reason. Therefore v3 or v4 blocks are a hard forking change which isn’t going to happen any time soon. Although I can add support for BIP66 and BIP65 to v0.8 while keeping these blocks labelled v2.

ghostlander

I have just finished v0.8.7.3 with the BIP66 (Strict DER) support and checks to make sure such a fork won’t happen again.

https://github.com/ghostlander/Feathercoin/commits/master-0.8

FlatBlack

@ghostlander so, this node is ‘back-on-track’ again for FTC-android-wallet…?
*me at ‘+8:00’ time-zone if referring time-display as picture below attached
alt text

lizhi

up to now, 0.9.5 sync normal, but 0.11.2 are stuck. 0.9.5 is version 3.

lizhi

I create a mechanism that when the 75% hashrate agree, blockchain upgrade automatically.
0.8.7.X and 0.9.3 use version 2, 0.9.5 use version 3, 0.11.2 use version 4.

Wellenreiter

After analysing the behavior of the different clients and the timing of the events leading to a fork the most probable reason for the fork is the follwing:

Client version 0.8.X and 0.9.3 use a block format version 2
Client version 0.9.5 uses a block format version 3

What happened:

A pool using 0.9.5 as client generated a block and annouced it to be inserted into block chain
As this block was using block format 3, all 0.8.7.x/0.9.3 clients rejected that block, while all 0.9.5 clients accepted it and inserted it into their local copy of the block chain
Then a pool using 0.8.7.x found a block and annouced it to be inserted into the block chain.
all 0.8.7.x and 0.9.3 clients accepted that block, while 0.9.5 clients flagged it as orphan, as they already had a block with that block number/height.

The result was the split into two chains, where 0.9.5 clients where on a different trunk of the chain than all other clients.

For for all pool operators and miners who to solo mining on a client with version 0.9.5 please change your client to 0.8.7.3 or 0.9.3

GMC

Thanks for the update @Wellenreiter
Will it be a 0.9.3 patch? Blockchain still looks a bit strange. 0.9.3 and 0.8.7.3 are forked?

Wellenreiter

At the current state, it seems, that the current problems are solved as soon as all 0.8.7.x versions are upgraded to 0.8.7.3

Hopefully pool operators will react fast.

AmDD

@Wellenreiter said:

At the current state, it seems, that the current problems are solved as soon as all 0.8.7.x versions are upgraded to 0.8.7.3

Hopefully pool operators will react fast.

Those on 0.9.3 are ok to stay or should we downgrade to 0.8.7.3 too?

Wellenreiter

@AmDD said:

@Wellenreiter said:

At the current state, it seems, that the current problems are solved as soon as all 0.8.7.x versions are upgraded to 0.8.7.3

Hopefully pool operators will react fast.

Those on 0.9.3 are ok to stay or should we downgrade to 0.8.7.3 too?

downgrade to 0.8.7.3 would work, but require careful planning and a full re-sync, so it’ll take several hours.

Especially the wallet private keys should be dumped and noted down in addition to a safety copy of wallet.dat as the database format has changed.

If you are not keeping the mined coins on the pool system, and the wall’et address doesn’t mind, that is no problem of course.

I started a downgrade from 0.9.3 to 0.8.X/0.8.7.3 yesterday early afternoon and I’m synced to block 992462 now, so for me the downgrade takes more than 24h.

I’m not sure how long an upgrade from 0.9.3 to 0.9.5 would take, as I never did that.

I’m currently trying to determine, if 0.9.3 can handle block format version 3. If that is the case, no change would be required.

AmDD

@Wellenreiter said:

@AmDD said:

@Wellenreiter said:

At the current state, it seems, that the current problems are solved as soon as all 0.8.7.x versions are upgraded to 0.8.7.3

Hopefully pool operators will react fast.

Those on 0.9.3 are ok to stay or should we downgrade to 0.8.7.3 too?

downgrade to 0.8.7.3 would work, but require careful planning and a full re-sync, so it’ll take several hours.

Especially the wallet private keys should be dumped and noted down in addition to a safety copy of wallet.dat as the database format has changed.

If you are not keeping the mined coins on the pool system, and the wall’et address doesn’t mind, that is no problem of course.

I started a downgrade from 0.9.3 to 0.8.X/0.8.7.3 yesterday early afternoon and I’m synced to block 992462 now, so for me the downgrade takes more than 24h.

I’m not sure how long an upgrade from 0.9.3 to 0.9.5 would take, as I never did that.

I’m currently trying to determine, if 0.9.3 can handle block format version 3. If that is the case, no change would be required.

Alright, I’ll sit tight then and wait on your word.

Wellenreiter

@Wellenreiter said:

For for all pool operators and miners who do solo mining on a client with version 0.9.5 please change your client to 0.8.7.3 or 0.9.3.1

Attention: we found that the 0.9.3 has the same problem as 0.8.7.x

A patched version 0.9.3.1 will be available soon.

Status of patch will be updated here