48c7e4ab8c
* Tweaked snapshot sync threshold * Change keypath derivation logic (#6815) While the standard defined by Trezor as the default derivation path here https://blog.trezor.io/trezor-integration-with-myetherwallet-3e217a652e08 says that it should be `m/44'/60'/0`, in practice they don't have an implementation of a wallet for Ethereum themselves and refer customers to MEW. MEW has a custom implementation of the path derivation logic that allows them to generate multiple addresses by essentially adding `/0`, `/1` etc to the path. In my initial implementation of Trezor I didn't take this into consideration unfortunately and just used the keypath that Trezor themselves recommended. However, given that it's seemingly standard practice to append `/0` for a "sub-address" (and this is what we've done for Ledger as well) it seems like a mistake on my part to not take that into consideration. Unfortunately, anyone who has used their Trezor device with Parity previously would now see a different address when they connect the Trezor device the next time. The only way they would have to access the old address is to use an old version, or by going through MEW and selecting the Ledger keypath. Also see #6811 |
||
---|---|---|
.github | ||
chainspec | ||
dapps | ||
devtools | ||
docker | ||
docs | ||
ethash | ||
ethcore | ||
ethcrypto | ||
ethkey | ||
ethstore | ||
evmbin | ||
evmjit | ||
hash-fetch | ||
hw | ||
ipc | ||
ipc-common-types | ||
ipfs | ||
js | ||
json | ||
local-store | ||
logger | ||
mac | ||
machine | ||
nsis | ||
panic_hook | ||
parity | ||
price-info | ||
rpc | ||
rpc_cli | ||
rpc_client | ||
scripts | ||
secret_store | ||
snap | ||
stratum | ||
sync | ||
updater | ||
util | ||
whisper | ||
windows/ptray | ||
.dockerignore | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
.gitmodules | ||
build.rs | ||
Cargo.lock | ||
Cargo.toml | ||
CHANGELOG.md | ||
LICENSE | ||
license_header | ||
README.md | ||
rust-toolchain | ||
rustfmt.toml | ||
SECURITY.md | ||
test.sh |
Parity - fast, light, and robust Ethereum client
Join the chat!
Get in touch with us on Gitter:
Be sure to check out our wiki and the internal documentation for more information.
About Parity
Parity's goal is to be the fastest, lightest, and most secure Ethereum client. We are developing Parity using the sophisticated and cutting-edge Rust programming language. Parity is licensed under the GPLv3, and can be used for all your Ethereum needs.
Parity comes with a built-in wallet. To access Parity Wallet simply go to http://web3.site/ (if you don't have access to the internet, but still want to use the service, you can also use http://127.0.0.1:8180/). It includes various functionality allowing you to:
- create and manage your Ethereum accounts;
- manage your Ether and any Ethereum tokens;
- create and register your own tokens;
- and much more.
By default, Parity will also run a JSONRPC server on 127.0.0.1:8545
. This is fully configurable and supports a number of RPC APIs.
If you run into an issue while using parity, feel free to file one in this repository or hop on our gitter chat room to ask a question. We are glad to help!
For security-critical issues, please refer to the security policy outlined in SECURITY.MD
.
Parity's current release is 1.7. You can download it at https://github.com/paritytech/parity/releases or follow the instructions below to build from source.
Build dependencies
Parity requires Rust version 1.19.0 to build
We recommend installing Rust through rustup. If you don't already have rustup, you can install it like this:
-
Linux:
$ curl https://sh.rustup.rs -sSf | sh
Parity also requires
gcc
,g++
,libssl-dev
/openssl
,libudev-dev
andpkg-config
packages to be installed. -
OSX:
$ curl https://sh.rustup.rs -sSf | sh
clang
is required. It comes with Xcode command line tools or can be installed with homebrew. -
Windows
Make sure you have Visual Studio 2015 with C++ support installed. Next, download and run the rustup installer from https://static.rust-lang.org/rustup/dist/x86_64-pc-windows-msvc/rustup-init.exe, start "VS2015 x64 Native Tools Command Prompt", and use the following command to install and set up the msvc toolchain:
$ rustup default stable-x86_64-pc-windows-msvc
Once you have rustup, install parity or download and build from source
Install from the snap store
In any of the supported Linux distros:
sudo snap install parity --edge
(Note that this is an experimental and unstable release, at the moment)
Build from source
# download Parity code
$ git clone https://github.com/paritytech/parity
$ cd parity
# build in release mode
$ cargo build --release
This will produce an executable in the ./target/release
subdirectory.
Note: if cargo fails to parse manifest try:
$ ~/.cargo/bin/cargo build --release
Simple one-line installer for Mac and Ubuntu
bash <(curl https://get.parity.io -Lk)
Start Parity
Manually
To start Parity manually, just run
$ ./target/release/parity
and Parity will begin syncing the Ethereum blockchain.
Using systemd service file
To start Parity as a regular user using systemd init:
-
Copy
parity/scripts/parity.service
to your systemd user directory (usually~/.config/systemd/user
). -
To pass any argument to Parity, write a
~/.parity/parity.conf
file this way:ARGS="ARG1 ARG2 ARG3"
.Example:
ARGS="ui --identity MyMachine"
.