I have parity 1.6.8 installed on OSX 10.13.6

Parity used to work by running to .app file and then accessing on a web browser.

Now it tells me, "Unable to make a connection to the Parity Secure API. To update your secure token or to generate a new one, run (parity signer new-token) and paste the generated token into the space below."

I open Terminal and type in parity signer new-token but returns

-bash: parity: command not found

I go to https://www.parity.io/ethereum/#download to download the stable version of Parity but when I double click on it opens up my text editor with a bunch of code in it without installing the app.

How can I get Parity going again? I'd also like to be able to prevent Parity from downloading the blockchain when I start it.

My objective is to check to see if a wallet I created on parity a while ago has any funds in it.


Unfortunately Parity has dropped support for the UI in favor of focusing on the core node - if you want the kind of experience that you were used to with the old "Parity App", you should consider moving to one of the alternatives.

Here's some information that might help you migrate:

The default data directory on OSX is: $HOME/Library/Application Support/io.parity.ethereum/

If you dig around in the "keys" folder (there might be additional keys folders in the different "chains" folders) you will be able to find your json key files which you can import into the wallet of your choice (I hope you remember your password)

If you have forgotten your passwords or can't find your key files, but you remember your seed-phrase, you can use a legacy version of MEW.

(grab the parity-enabled zip, extract it somewhere, open index.html, go to the "view wallet info" page, and after you use your parity phrase to unlock, you'll be able to grab your private key to import into other wallet software)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.