The Feathercoin forum’s software has bee updated to the latest Version
@jameswilliam Welcome to the forum,
your question ist hard to answer. As there are many different crypto coins, there are as many wallets plus some.
The same it true for exchanges, as not all exchanges have all coins listed.
So the best exchange for one coin may be not the best for the other one.
If you are using Linix packages to install and update the feathercoin wallet on your system, you need to update the repository key configured on your system.
The old repository key expired on March 22nd and the Linux packages are signed with a new key.
Please find the new key and instructions to install it
First of all many thanks for your feedback.
You are right, I need to clean up a couple of things in the repository. The submodule init is a left over from the first tests and in the neantime there is a python neoscrypt module available, that can be installed with pip.
I also missed the fact, that I need to adapt the cache and config locattion, when forking directly from spesmilo repository. It’s on my todo list now.
I also have access to some of the server not working for you. I will check and probably update the ssl certificates there.
Please keep your wallet open for at least 12 hours and check if your transaktion will get verified. This can take some time.
Please keep me updated here.
Last but not least, my focus is on the 4.x version, as the 3.3.8 version is about 2 years old, maybe older and a bit outdated already.
I’d like you to try out 4.1.5 or 3.3.8 from my repository.
As mentioned I had the same problem and somehow fixed it.
The last thing I remember was, that I replaced the checkpoints.json and created one containing one block only,
but that was more due to the fact, that the checkpoints.json from the upstream repository containted BTC checkpoints.
my current checkpoints.json looks like this:
[ ["4c492ece482967a3a76d825e1f440f51d255f0dd84af15544fef09b72691d57d",2016], ]
If you can connect to one of the 4 server I mentioned, the communication between server and wallet is ok.
I have exactly the opposite problem and can connect to all servers, but electrumx-1.neoscrypt.de. This seems to be another problem and nor related to your actual problem.
As long as you can connect to one server it should be ok.
electrumx-1.neoscrypt.de is running server version 1.9.5, cloned from https://github.com/spesmilo/electrumx.git
with wallet version 184.108.40.206
The latest server version 1.16.0 should be ok, too
The block your wallet is complaining about is block #2165184 which was generated Apr 15, 2018 12:49:48 PM according to block explorer
Is that around the time you used your electrum wallet the last time with success?
I had a message similar to the one you mentioned in your first post, but for block #1, when I started to adapt the 0.4.x version for Feathercoin.
If I remember right, I modified the checkpoints.json, but I’m not sure.
So to locate the cause of the problem, I suggest to export your seed and just to be sure your private keys, clean the local block storage by moving or deleting the file ‘blockchain_headers’ in your config directory (~/.electrum on linux systems) and start the electrum wallet.
The wallet will then re-sync with the server from scratch.
I see three possibilities:
By the way, what is the source you got your 3.3.8 wallet from?