fa6a0a6b60
* Improve handling of RocksDB corruption (#7630) * kvdb-rocksdb: update rust-rocksdb version * kvdb-rocksdb: mark corruptions and attempt repair on db open * kvdb-rocksdb: better corruption detection on open * kvdb-rocksdb: add corruption_file_name const * kvdb-rocksdb: rename mark_corruption to check_for_corruption * Hardening of CSP (#7621) * Fixed delegatecall's from/to (#7568) * Fixed delegatecall's from/to, closes #7166 * added tests for delegatecall traces, #7167 * Light client RPCs (#7603) * Implement registrar. * Implement eth_getCode * Don't wait for providers. * Don't wait for providers. * Fix linting and wasm tests. * Problem: AttachedProtocols don't get registered (#7610) I was investigating issues I am having with Whisper support. I've enabled Whisper on a custom test network and inserted traces into Whisper handler implementation (Network<T> and NetworkProtocolHandler for Network<T>) and I noticed that the handler was never invoked. After further research on this matter, I found out that AttachedProtocol's register function does nothing: https://github.com/paritytech/parity/blob/master/sync/src/api.rs#L172 but there was an implementation originally: 99075ad#diff-5212acb6bcea60e9804ba7b50f6fe6ec and it did the actual expected logic of registering the protocol in the NetworkService. However, as of 16d84f8#diff-5212acb6bcea60e9804ba7b50f6fe6ec ("finished removing ipc") this implementation is gone and only the no-op function is left. Which leads me to a conclusion that in fact Whisper's handler never gets registered in the service and therefore two nodes won't communicate using it. Solution: Resurrect original non-empty `AttachedProtocols.register` implementation Resolves #7566 * Fix Temporarily Invalid blocks handling (#7613) * Handle temporarily invalid blocks in sync. * Fix tests. |
||
---|---|---|
.github | ||
chainspec | ||
dapps | ||
devtools | ||
docker | ||
docs | ||
ethash | ||
ethcore | ||
ethcrypto | ||
ethkey | ||
ethstore | ||
evmbin | ||
evmjit | ||
hash-fetch | ||
hw | ||
ipfs | ||
js | ||
js-old | ||
json | ||
local-store | ||
logger | ||
mac | ||
machine | ||
nsis | ||
panic_hook | ||
parity | ||
price-info | ||
rpc | ||
rpc_cli | ||
rpc_client | ||
scripts | ||
secret_store | ||
snap | ||
stratum | ||
sync | ||
transaction-pool | ||
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:
Or join our community on Matrix:
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
and a websockets server on 127.0.0.1:8546
. This is fully configurable and supports a number of APIs.
If you run into an issue while using Parity, feel free to file one in this repository or hop on our Gitter or Riot 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.8. 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.21.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
Note: When compiling a crate and you receive the following error:
error: the crate is compiled with the panic strategy `abort` which is incompatible with this crate's strategy of `unwind`
Cleaning the repository will most likely solve the issue, try:
$ cargo clean
This will always compile the latest nightly builds. If you want to build stable or beta, do a git checkout stable
or git checkout beta
first.
Simple one-line installer for Mac and Ubuntu
bash <(curl https://get.parity.io -Lk)
The one-line installer always defaults to the latest beta release.
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
./scripts/parity.service
to your systemd user directory (usually~/.config/systemd/user
). - To configure Parity, write a
/etc/parity/config.toml
config file, see Configuring Parity for details.