Repository files navigation

Fether was originally developed on top of Parity Ethereum which transitions to Open Ethereum,more info here. As a result, Parity Technologies will not maintain actively Fether anymore.

» Download the latest release «

Parity Fether aims to be the lightest and simplest decentralized wallet. It supports Ether and ERC-20 tokens, and runs on top ofParity Ethereum light client. This allows smooth synchronization and interaction with the Ethereum blockchain, in a decentralized manner.

By default, Fether will launch its embedded Parity Ethereum light client. You can also separately launch your Ethereum client and Fether will automatically connect to it, as described in theFether FAQ.

Parity Fether interacts with the light node using@parity/light.js, a Javascript library specifically crafted for wallets to connect with light clients.

Parity Fether is licensed under the BSD 3-Clause, and can be used for all your Ethereum needs.

If you run into problems while using Parity Fether, first check out theFAQ on our wiki and feel free to file an issue in this repository or hop on ourGitter orRiot chat rooms if you have any question. We are glad to help!

For security-critical issues, please refer to the security policy outlined inSECURITY.md.

Get in touch with us on Gitter:

Official website:https://parity.io | Be sure to check outour Wiki for more information.

• Download the.dmg file.
• Double click on it to install Fether.

• Download the.exe file.
• Double click on it to install Fether.
• Fether will be added to the program menu.

• Download the.AppImage file.
• Make it executablechmod +x /path/to/fether-x.x.x-x86_64.AppImage.
• Launch it/path/to/fether-x.x.x-x86_64.AppImage.

• Download the.tar.xz file.
• Unarchive ittar xf fether-x.x.x.tar.xz.
• Launch it./fether-x.x.x/fether.

• Download the.deb file.
• Double click on the file to install Fether.
• Fether will be added to the program menu.

• Don't run Fether as root

• Beware of suspicious symlinks called fether-x.y.z-x86_64.AppImage.home

This attack vector applies to any AppImage application. It consists of crafting a .home file/folder to be used as the home folder by an AppImage application. The danger resides in the fact that this .home file could be a symlink somewhere on the user's computer. The AppImage would be using this new location as a home folder, in a non-transparent way. Running the application as root might damage a system, for example, by overflowing the /boot partition.

Install Xcode Command Line Tools, NVM, Node.js latest LTS, Yarn, and Git

xcode-select --install;curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.11/install.sh| bash;export NVM_DIR="$HOME/.nvm"[-s"$NVM_DIR/nvm.sh" ]&&\."$NVM_DIR/nvm.sh"# This loads nvm[-s"$NVM_DIR/bash_completion" ]&&\."$NVM_DIR/bash_completion"# This loads nvm bash_completionecho -e"Installing Node.js latest LTS version";nvm install --ltsecho -e"Switching to use Node.js latest LTS version";nvm use --lts;brew install yarn --without-node;brew install git --verbose;brew upgrade git --verbose;

Install Node.js 10.x, Yarn, Git, and increase amount of inotify watchers

sudo apt update;sudo apt install -y git nodejs npm curl;curl -sL https://deb.nodesource.com/setup_10.x| sudo -E bash -;apt-get install -y nodejs;sudo ln -s /usr/bin/nodejs /usr/bin/node;curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg| sudo apt-key add -;echo"deb https://dl.yarnpkg.com/debian/ stable main"| sudo tee /etc/apt/sources.list.d/yarn.list;sudo apt-get update&& sudo apt-get install yarn;sudo ln -s /usr/bin/yarn /usr/local/bin/yarn;yarn global add windows-build-tools;

git clone https://github.com/paritytech/fethercd ./fetheryarn install

yarn electron

yarn package

yarn start

1. Alternative toyarn; yarn build; DEBUG=electron-builder yarn release --mac; is to just runyarn package and then run theopen "./packages/fether-electron/dist/mac/Parity Fether.app" (i.e. no need to install)

2. Publishing a new release to GitHub is performed by a maintainer of the repository. In this case you need to obtain theGH_TOKEN from GitHub settings and add it usingexport GH_TOKEN="..." to ~/.bashrc and then runsource ~/.bashrc. If you get an error that theGH_TOKEN is missing and you are only building the binary but not publishing, then just ignore the error.

Build and run binaries (i.e. .dmg) for production on Mac of a specific remote branch

git fetch origin INSERT_BRANCH_NAME:INSERT_BRANCH_NAME;git checkout INSERT_BRANCH_NAME;rm -rf ./packages/fether-electron/dist/rm -rf /Applications/Parity\Fether.app/yarn; yarn build; DEBUG=electron-builder yarn release --mac;open ./packages/fether-electron/dist/Parity\Fether-0.3.0.dmg

Build and run binaries (i.e. .deb) for production on Linux

Note: If you want to save time building, then first edit electron-builder.json so that it only builds a single binary like .deb instead of all of them

sudo rm -rf /opt/Parity\Fether;rm -rf~/.config/Electron;rm -rf~/.config/fether;rm -rf ./packages/fether-electron/dist/;sudo rm /usr/local/bin/fether;sudo apt remove -y fether;yarn; yarn build; DEBUG=electron-builder yarn release --linuxsudo apt install -y ./packages/fether-electron/dist/fether_0.3.0_amd64.debfether

Build and run binaries (i.e. .exe) binary for production on Windows

rm -rf /packages/fether-electron/dist;yarn; yarn build; DEBUG=electron-builder yarn release --win;./packages/fether-electron/dist/Parity\Fether-0.3.0.exe