Thibaut Sardan

Should we close then? ~~I'll open several issues to break down #100 later on.~~ edit: just saw https://github.com/paritytech/fether/pull/400 addresses most of it, we can open another issue for what's left.

This happened to me this week-end on mainnet, I was trying to narrow it down. It did not happen when letting Fether launch parity itself AFAIR

>Then it changed to 'Syncing...(2%) (kovan)' Because of this I don't think that you had the bug. I had it (also saying it's synced on Kovan whereas it was syncing...

This is a fair point, but since we are on a light client, and we want to stay light (in terms of bandwidth), I don't want us to start spamming...

In the transaction recap would be already good: 

Agreed that it would be a welcome additional security feature.

Yes, this is part of https://github.com/paritytech/fether/issues/486

Do you know it this happens with the packaged version (.dmg, .exe, .deb)? if not then it's not a big deal.

Thanks for you PR, this is being revamped in https://github.com/ChainSafe/dappeteer/pull/202 and it should be more robust

This should be solved by #181