Feathercoin Fork
-
@bsotnikow You should upgrade as fast as possible.
Unfortunatelly I’m no familiar with Mac so I can’t help very much
What you should do in principle:
-
backup you private keys
- first option:
- min your 0.8.7 wallet go to help-> debug->console window
- enter dumpprivkey “feathercoinaddress” for all of your addresses
- write down or copy/paste the provate key returned to a safe place
- second option:
- copy your wallet.dat file in the %appdata% directory (windows terminology, sorry) to a safe place
- first option:
-
download and install 0.9.3. For mac it is just the binary.
- restore your private keys
- open console window and enter importprivkey “feathercoinprivkey” for all of your noted private keys
- For the last one add ‘rescan’ at the end of the line
- or copy the saved wallet .dat back to %appdata%
- open console window and enter importprivkey “feathercoinprivkey” for all of your noted private keys
- restore your private keys
-
restart your wallet and let it sync
I hope that someone more familiar with Mac can give a more detailed description what to do
-
-
@bsotnikow said:
@AmDD Thanks, sounds easy enough. Im just a little freaked out to do it. Anybody know for sure?..I also did a backup from the wallet and I’m backing up my entire hard drive.
If you make a good wallet backup then you should be fine. Just install the 0.9.3 over the old version and if it doesnt display your FTC, shut down the wallet and replace your wallet.dat with the one you backed up and then open the wallet again.
-
@AmDD Thanks to you both. I’ll give it a go once the hard drive has backed up too, I want to be extra sure.
-
There is currently no Mac 0.9.3 wallet available, we are currently working on it but it may take some time
-
@all What makes you think v0.9.3 is correct while v0.8.7 and v0.11.2 are not?
-
@ghostlander said:
@all What makes you think v0.9.3 is correct while v0.8.7 and v0.11.2 are not?
good question!
-
@ghostlander
more or less because 0.9.3 is up to date with blocks, while 0.11.X is stuck at a block with time stamp 2016-03-04 01:18:53 -
What’s the current version of the ACP master?
-
good question
it’s on 0.8.7
I just got the login
will upgrade now -
Restart your v0.8.7 or v0.11.2 or whatever clients with -disablesafemode to get past block 1114310:
getmininginfo
{
“blocks” : 1114311,
“currentblocksize” : 0,
“currentblocktx” : 0,
“difficulty” : 3.18099943,
“errors” : “Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.”,
“generate” : false,
“genproclimit” : 2,
“hashespersec” : 0,
“networkhashps” : 7255790,
“pooledtx” : 0,
“testnet” : false
}getblockhash 1114311
93515f222f16a9ff3db6594e5ee7c12924cff9ba05b01dbe551d0a9e65dd141f
getblock 93515f222f16a9ff3db6594e5ee7c12924cff9ba05b01dbe551d0a9e65dd141f
{
“hash” : “93515f222f16a9ff3db6594e5ee7c12924cff9ba05b01dbe551d0a9e65dd141f”,
“confirmations” : 1,
“size” : 699,
“height” : 1114311,
“version” : 2,
“merkleroot” : “66820d69d4182bbed60e5e16c44abf41bfc0ba0b502ed0045977c09b48a0751e”,
“tx” : [
“66d9ad39a53a125af297f29c854b8a601c94a90a1db50ba66dcff4455ab4b4f5”,
“0279c10941069002cd8dff09131796d11d214820287f98bd3eb7e1b176b3fa5a”,
“400f7f8ec558f427cb4207deea196cb20cccc403da0c971225dec1f9394ec100”
],
“time” : 1457105972,
“nonce” : 30598,
“bits” : “1c507a04”,
“difficulty” : 3.18099943,
“previousblockhash” : “944a95ddacb5b567448ee450b0f0f4c328e4cfff92c7ad2f255d199ef53e0641”
}BTW, I think it’s a nonsense to disable RPC in safe mode.
-
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
