_Before filing a new issue, please provide the following information._
I'm running:
Which Parity version?: 1.10.0
Which operating system?:Linux,Ubuntu
How installed?: via installer
Are you fully synchronized?: no, not yet
Which network are you connected to?: ethereum
Did you try to restart the node?: yes,many times
I‘m trying to restore my account from the 12 words mnemonic phrase via the Parity-ui. But after i submitted the 12 words, i get a new account with a new address starting with 0X00......., which is not the one corresponding the mnemonic words i input.
It took me many days to sync, but parity looks dead, blocks count stops at 1,015,XXX. Am i wrong about sth?
i get a new account with a new address starting with 0X00
Then the mnemonic you entered is not the one given originally. You should double check, make sure the spelling is good, white space, the words here is the supported list
It took me many days to sync, but parity looks dead, blocks count stops at 1,015,XXX
You are not synced as the top of the chain is currently around 5.xM blocks. I believe that the warp sync failed. Here is what I advise you to do:
Syncing is with warp is tricky these days because of several issues we're working on, here is my rule of thumb :
parity db kill--warp-barrier following [these instructions}(https://wiki.parity.io/FAQ-Basic-Operations,-Configuration,-and-Synchronization.html#why-is-warp-synchronization-so-fast)--light flag. This doesn't use snapshots and only sync block headers. It's secure and quick.This is not per se a parity problem, just some challenges brought by the growing network, it's a good thing :)
@Tbaut thanks, i will try again
Most helpful comment
Then the mnemonic you entered is not the one given originally. You should double check, make sure the spelling is good, white space, the words here is the supported list
You are not synced as the top of the chain is currently around 5.xM blocks. I believe that the warp sync failed. Here is what I advise you to do:
Syncing is with warp is tricky these days because of several issues we're working on, here is my rule of thumb :
parity db kill--warp-barrierfollowing [these instructions}(https://wiki.parity.io/FAQ-Basic-Operations,-Configuration,-and-Synchronization.html#why-is-warp-synchronization-so-fast)--lightflag. This doesn't use snapshots and only sync block headers. It's secure and quick.This is not per se a parity problem, just some challenges brought by the growing network, it's a good thing :)