mist icon indicating copy to clipboard operation
mist copied to clipboard

token autoscan does not work

Open RaZeRiel opened this issue 7 years ago • 8 comments
trafficstars

like the title says, token autoscan does not work and i don't know why. i have already deleted all folders & reinstalled the wallet, tried 0.10.0 version and still not working. also deleted all tokens.

the log says: [2018-09-04T19:56:55.728] [INFO] (ui: browser) - Error parsing token list: SyntaxError: Unexpected token : in JSON at position 3 [2018-09-04T19:56:55.729] [WARN] (ui: browser) - %cUnhandled rejection Error parsing token list: SyntaxError: Unexpected token : in JSON at position 3 color: red

Version: `0.11.1`
OS & Version: windows
Node version: `geth 1.8.13`
Number of blocks synchronized: 6 271 616

git

git2

all.log.zip

RaZeRiel avatar Sep 04 '18 18:09 RaZeRiel

Thanks for reporting @RaZeRiel, it will be sorted out soon!

evertonfraga avatar Sep 10 '18 13:09 evertonfraga

this bug also exists in Linux image

sycomix avatar Sep 29 '18 07:09 sycomix

Confirming bug also exists in MacOS

mpge avatar Oct 10 '18 04:10 mpge

confirmed, it seems this url that it is trying to download is invalid:

https://raw.githubusercontent.com/MyEtherWallet/ethereum-lists/master/tokens/tokens-eth.json

psy0rz avatar Oct 10 '18 10:10 psy0rz

Yeah, the source changed URLs. That was fixed in our local repository and will be available as soon as we release 0.12.0.

Thanks for reporting.

evertonfraga avatar Oct 11 '18 16:10 evertonfraga

Shouldn't we be our "own" source? e.g. fork that repository and create a cronjob somewhere that updates it automatically.

This way we can fix it retroactively when they change something, instead of having to wait on the next release.

Also: Should our json parser handle data from an "untrusted" source? What if someone crafts a special file that exploits a weakness in our json handling code?

psy0rz avatar Oct 11 '18 17:10 psy0rz

I can confirm this issue under Windows 10 for ethereum wallet and Mist.

UGatgithub avatar Mar 17 '19 16:03 UGatgithub

Also: Should our json parser handle data from an "untrusted" source? What if someone crafts a special file that exploits a weakness in our json handling code?

Still no reply to this yet? I'm very worried that a cryptowallet makes REST calls to a 3rd party service. It basically means you have to trust all the libraries that are involved in getting and parsing json via a https get request. (e.g. a lot of code, inclusing ssl libraries.)

psy0rz avatar Mar 18 '19 11:03 psy0rz