How to install Exodus wallet on any Linux distribution

Exodus wallet is a cross-platform, dual-use crypto-wallet that’s truly fun to use. Its interface is about the cleanest I’ve come across, and it’s dual-use, because it also functions as an exchange platform – it can be used to trade several popular cryptocurrencie.

This article shows how to install it on any Linux distribution.

To accomplish that, you first have to download it, which you can do by visiting the project’s download page. Then click on the appropriate button to download the zip file for Linux. At the time of this publication, the latest release is v1.32.0. After the download has completed, installing Exodus simply involves unzipping the file and running the executable buried two directories deep. The following show the steps from after downloading it to running it:

# After downloading Exodus wallet for Linux, navigate to the directory it was downloaded into
# this assumes that that directory is "Downloads"

cd Downloads

# unzip it. The version you downloaded might be different, so don't just copy and paste this
# command

unzip Exodus-linux-x64-1.32.0.zip

# In my case, it was extracted into "exodus-1.32.0/Exodus-linux-x64" directory. 
# Inside that directory is an executable named Exodus. 
# Run that executable to start the wallet
# > indicates output

./Exodus

# You'll always get the following output as the program starts

> ENV: production
> Secp256k1 bindings are not compiled. Pure JS implementation will be used.
> bitcoin fee: 380 sat/byte
> Secp256k1 bindings are not compiled. Pure JS implementation will be used.
> Exodus (production): DATA DIR: /home/kamit/.config/Exodus
> main: 3015.936ms

> SET WALLET LOADED
> true

> { Error: ENOENT: no such file or directory, open '/home/kamit/.config/Exodus/exodus.conf.json'
>    at Error (native)
>  errno: -2,
>  code: 'ENOENT',
>  syscall: 'open',
>  path: '/home/kamit/.config/Exodus/exodus.conf.json' }

#

Despite those errors, the application will work. And using npm to install secp256k1 will not make any difference to that part of the output about Secp256k1.

So at the end of the error-filled output, the programs starts. Figure 1 shows the main interface.