Clients on 0.8.7.x Upgrade ASAP to solve current fork situation!!!
-
@Wellenreiter Hi thanks. I’m on mac running 8.7.1, is upgrading going to work for me? I know i can’t upgrade to v9… How do i upgrade exactly please? Is it just a matter of swapping the application files? Thanks!
-
yes, for a Mac replacing the binary should be fine.
Unfortunatelly there is no binary available, so you’d need to compile yourself or wait.If you decide for the later, can you shutdown your client, until a 0.8.7.3 binary is available for you?
-
@Wellenreiter Absolutely thanks, shutting down now. And I don’t mind waiting at all, my FTC are a long term investment.
-
Would someone be able to provide details on how I can do this on a PC. I would need it step by step and in detail if possible as my technical abilities are somewhere close to zero!!!
Thank you.
-
ok, as there has not been a reply here I will have to try and do this myself (hopefully not loosing my coins in the process).
I have downloaded the files from GitHub and I was looking for a .exe file however I cannot see one. I can see the ‘feathercoin-qt.pro’ is this the file i need to move over?
-
@Danlau said:
ok, as there has not been a reply here I will have to try and do this myself (hopefully not loosing my coins in the process).
I have downloaded the files from GitHub and I was looking for a .exe file however I cannot see one. I can see the ‘feathercoin-qt.pro’ is this the file i need to move over?
No, feathercoin-qt.pro is the make file, not the executable for the gui.
We are in the process to compile windows binaries, but that may take some time
If somebody in the community could help out with compiled binaries for the windows gui and mac gui, that would be great.
Regarding your coins, do the following
Locate the feathercoin working directory on your pc. For Windows it is a subdirectory of %appdata%
copy the file ‘wallet.dat’ to a save place
This file contains your private keys
This is your first backup
As a second backup you can start your current gui and then:
- go to help->debug->console
- enter ‘dumpprivkey <address>’ for each of your feathercoin addresses
- write down or copy the returned private key to a safe place
This is your second backup
Be careful with the file and the private keys noted.
Whoever has access to the file or the keys has access to your coins.When you have copied the file and keys it should be safe to update
-
@Wellenreiter Thank you for your help, I shall do that straight away.
I will keep an eye out for the binary file when its available. In the meantime should I not open and use 0.8.1?
-
You should not use any version < 0.8.7.3 and also not 0.9.3.0, as you extend the time we have a fork in the chain by these client versions.
To backup your keys, I suggest to do this offline, without a connection to the Internet, if possible.
If you need to do it online, just open the client, make your backups and close it.
The be patient and wait for the new binaries without opening the client again.
-
@Wellenreiter Thanks again for your help and advice. I have successfully backed up the wallet.dat file however when I try the second backup I keep getting an ‘invalid address’ error. I am not sure what I am doing wrong as I am using the ‘copy address’ option.
-
It is very sensitiy to ‘unreadeble’ characters and I always to it with a basic copy/paste
Waht I did :
- go to ‘receive’
- without filling out anything clicked ‘Request Payment’
- did a copy of the key shown in the following window
- pasted it as parameter to the dumpprivkey command into the console window of the client
-
ok when I go to ‘receive’ I cant see the option ‘Request payment’.
-
should be a button
you also can g to any list sowing your address and use windows copy/paste instead of ‘copy address’ in the client -
Ok I have tried that and I keep getting this message:

Invalid Feathercoin address (code -5) -
If you have a copy of wallet.dat you should be fine.
The dumpprivkey always worked fine for me and was meant as second safety net. -
@Wellenreiter ok thanks for your help. I have the wallet.dat file so I guess ill just wait for the binary file so that I can upgrade.
Thanks again.
