Feathercoin Fork
-
If most pools and exchanges follow v0.8.7 and v0.11.2, maybe it’s better to follow this fork and investigate incompatibility with v0.9.x. When BTC forked in 2013 due to differences between LevelDB (v0.8) and BerkeleyDB (v0.7 and earlier), they reverted to the v0.7 chain.
-
I’ve got my 0.8.7 node back up
-
@uncle_muddy Thanks. OK. Is it best I just wait, don’t open it and worry about it when its resolved? Or should I try disablesafemode? . . .I would need someone to walk me through exactly how to do that.
-
is there a 0.9.5 for mac? Im having luck with 0.9.5 on windows.
-
When non-v0.9 wallets recognised they are on a shorter chain and couldn’t reorganise to the v0.9 chain, they dropped into safe mode. The Bitcoin Core developers decided some time ago when a wallet drops into safe mode, it disables all RPC commands. This is dangerous. Therefore pools had their Stratum front ends running, but couldn’t submit any work to their daemons. They were stuck.
-
@ghostlander Hey guys, sorry to be the biggest dummy in the room. OK so to be sure I have this right. I’m going into my console on 8.7.1 and entering the -disablesafemode command. . . . Then I’m entering the lines ghostlander posted above? Is that right?
-
Run feathercoin-qt -disablesafemode
or put disablesafemode=1 to your feathercoin.conf -
@ghostlander hmm, thanks. I’m on mac though so I have no “Run” feature, is this something i do using terminal? I also did a full scan of my drive and have no files named feathercoin.conf. Also looked in applications support and the feathercoin-qt package contents myself as well, no luck.
-
I would guess as apple is a unix system that would would have to do it command line
-
@RIPPEDDRAGON No luck. I can open feathercoin-qt, but the -disablesafemode command is not valid.
Here’s what I enter:
open -a feathercoin-qt -disablesafemodeAnd this is what i get back:
open: invalid option – d -
-
@bsotnikow Locate .feathercoin directory in your home directory and create a feathercoin.conf file there.
We have a problem with v0.9 rather than other releases. A pool operator reported more orphans than valid blocks for his pool 2 weeks ago.
https://bitcointalk.org/index.php?topic=178286.msg13944056#msg13944056
When he downgraded v0.9.3 to v0.8.7 per my advise, no more excessive orphans. I didn’t investigate it any further, though noted. It seems v0.9 has compatibility issues. I’m sure it isn’t NeoScrypt related. Maybe something transaction related. If v0.9 accepts certain transactions as valid while v0.8 and v0.11 don’t, we can have such a situation.
-
Thanks! Creating a .conf file worked. I’m synced again.
-
If its transaction related, I wonder if increased traffic from the recent price spike and trade volume contributed.
-
@ghostlander
Where do we stand? At give-me-coins we have been mining a bunch of blocks with 0.9.3. -
@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.
-
Bittrex is having issues related to this as an fyi
@Bushstar miss you!
-
@ghostlander True. But we tested 0.11.2 and had problems also. And staying with 0.8.7 represented a risk also.
-
@GMC What risk? The basic functionality including the ACP is the same.
-
@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.
