FTC Wallet
-
I’ve asked those more knowledgeable than me to help, but can you see what block number it is stuck at?
You can get this by going to the console and typing
getinfo
-
Where exactly is the console and what is it?
And also it says 444762, but it never actually freezes.
When you hover your mouse over the green sync bar it says…
"Catching up…
Processed 444765 blocks of transaction history.
Last received block was generated 23 hours ago.
Transactions after this will not yet be visible"
Even though it is stuck at 23 hours, the processed block count keeps rising. Now it is at 444767.
-
Current block is 444,865 and as its about 2 hours since your post that would be about right.
Something odd is going on here because if you are up to block 444765 you are up to date.
Sounds to me like you have some odd time stamp issue going on.
To get to the console, click on the help menu optin in the wallet, then select ‘Debug window’ then click on the console tab and you are there
If you type help into the box at the bottom it will give you a list of commands you can use
If you type getinfo in there it will list the latest block you have synced to.
Then go to a FTC mining website and see what they list as the latest block.
If they are the same or only 1 or 2 different you are up to date, as it can sometimes take a minute or 2 for the latest block to propagate to all wallets.
If you look here http://www.wemineftc.com/stats
It will give the stats the blockchain is up to.
If your wallet and the website above agree its the same block it would make me think its still some odd issue with the time on your PC.
Have you set the clock on windows to automatically sync itself to the correct time?
-
Well, when I check the debug window the blocks are matching up, but for some reason won’t go past 23 hours.
Figured out the issue. I had to go in to my computers time settings and sync time with an online source. Wow, what a pain the arse.
Thanks so much for your help tmuir12. As soon as this next transaction goes through, I’ll hook you up!
-
I had a feeling it was something to do with the time on your pc.
An extra check the wallet does is check the timestamps on the blocks against the time on your PC and if the timestamp on the block is out of whack with your PC it won’t fully sync up.
Its a pain but its essentially part of the security protocol of the block chain to stop people faking blocks.
Glad you got it sorted in the end.
-
my 0.9.3 core wallet ,the synchronization of all the blockchain of spending 12 hours.
-
Ok guys, I’m having another issue. I recently made a withdraw from an exchange server I use when I got this new wallet and I never received it. I though it was due to the syncing, but after going back n forth with the company, they sent me where the coins went too and it is not my address.
BUT, the flip to this is, when you type in my FTC wallet address which is 6jkohpNx6JTkib8eWEMVqqEDa7xWJALAbx (current wallet) is brings up 796QgvgEoUvdY2GjXegpKxW1CdDSvp8SKu. How in the crap can this happen?
Thanks for all the support by the way.
Check it out…
https://bitinfocharts.com/feathercoin/address/6jkohpNx6JTkib8eWEMVqqEDa7xWJALAbx << see my current address in the URL and it pulls up that other address.
-
Anyone?
-
I noticed this too and I’m not sure why its doing that. But it looks like bitinfocharts is on a fork of the block chain anyway try http://explorer.Feathercoin.com for the real chain. :)
-
There is at least one other post here on the forum describing the same problem.
My personal guess is, that the explorere at bitcoininfocharts has not been upgraded to use neoscrypt, so that the wallet address is not decoded correctly.
-
I also recommend to update to 0.8.7.1 as soon as possible.
The Linux versions on the FTC main page are already updated, the new version for windows will be available soon
-
So does this mean the coins that I transferred are goin?
-
So does this mean the coins that I transferred are goin?
not necessarily.
if you can find the transaction in the blockchain with the official feathercoin explorer and the to address is correct the coins should arrive sometimes.
If the exchange server you sent the coins from has been on the old hashing algorithm at the time of sending, there is a big chance the the coins are gone or at least it will last a very long time until the coins come back on that exchange.
The reason for this is, that some clients are still not updated and your coins may be in the wrong branch of the blockchain. If that branch becomes invalidated, the transaction will be reversed and the coins will be on the exchange again.
-
So what should I do to get the coins back?
-
Which exchange was it? You could raise a ticket and say the tx never appeared! (Maybe also mention about the updated wallet and fork to NeoScrypt)
-
I did. They are basically saying they are looking in to it.
CoinMKT.com is the exchange. I will email them again and see what they say.
-
I did some tests and checks and we have the following situation:
Most of all clients are updated to software version 0.8.7.x, which is the Neoscrypt version.
Neverthless there is a small number of clients still running on 0.8.6.X, which is the Scrypt version. Unfortunately also some of the miners forgot to update to 8.7.X, too. Therefore a small parallel Blockchain still procucing Scrypt based FTC exist.
As most or all of the exchanges have updated to 0.8.7.x the Scrypt based blockchain is useless for the miners as they never can convert any coins mined after block 432000 to any other coin or FIAT.
This leads to the following situation when sending coins:
- Sender on 0.8.7.x -> receiver on 0.8.7.x -> transactions work
- Sender on 0.8.7.x -> receiver on 0.8.6.x -> coins will not arrive
- Sender on 0.8.6.x -> receiver on 0.8.7.x -> coins will not arrive
- Sender on 0.8.6.x -> receiver on 0.8.6.x -> coins will arrive, but useless
So I assume your coins where sent in either situation 2. or 3.
The good news is, that after both participants in a transfer are on 0.8.7.x the coins will show up somewhere, either at the sender side because the transaction has never happened on the Neoscrypt chain, of on the receiver side, because after the update the receiver will pick up the Neoscrypt blockchain and see the coins commming in.
The only coins that will not show up are any coins that where mined with the old Scrypt alrgorithm after block 432000, as these coins officially never existed
-
So, basically, old coins cannot be transferred to a new wallet. I have to wait until CoinMKT.com updates to neoscrypt then? Is my wallet fine to use?
I’m pretty sure I had old coins going to a new wallet. I got them on an exchange for BTC.
I bought FTC with BTC, so if I bought old coins from the exchange and sent them to a new wallet, I won’t get them until CoinMKT.com updates to neo or will I never receive them.
Thanks for the help.
-
So, basically, old coins cannot be transferred to a new wallet. I have to wait until CoinMKT.com updates to neoscrypt then? Is my wallet fine to use?
I’m pretty sure I had old coins going to a new wallet. I got them on an exchange for BTC.
I bought FTC with BTC, so if I bought old coins from the exchange and sent them to a new wallet, I won’t get them until CoinMKT.com updates to neo or will I never receive them.
Thanks for the help.
It’s not related to the age of the coins, unless you talk about coins mined with scrypt after October 27th, which are lost.
The point is, that the sending and receiving wallet must be on 0.8.7.x. If your wallet is on that version it’s fine to use.
