d35f4c1f0d
* produce portable binaries (#9725) * HF in POA Core (2018-10-22) (#9724) https://github.com/poanetwork/poa-chain-spec/pull/87 * Use static call and apparent value transfer for block reward contract code (#9603) * Verify block syncing responses against requests (#9670) * sync: Validate received BlockHeaders packets against stored request. * sync: Validate received BlockBodies and BlockReceipts. * sync: Fix broken tests. * sync: Unit tests for BlockDownloader::import_headers. * sync: Unit tests for import_{bodies,receipts}. * tests: Add missing method doc. * Fix ancient blocks sync (#9531) * Log block set in block_sync for easier debugging * logging macros * Match no args in sync logging macros * Add QueueFull error * Only allow importing headers if the first matches requested * WIP * Test for chain head gaps and log * Calc distance even with 2 heads * Revert previous commits, preparing simple fix This reverts commit 5f38aa885b22ebb0e3a1d60120cea69f9f322628. * Reject headers with no gaps when ChainHead * Reset block sync download when queue full * Simplify check for subchain heads * Add comment to explain subchain heads filter * Fix is_subchain_heads check and comment * Prevent premature round completion after restart This is a problem on mainnet where multiple stale peer requests will force many rounds to complete quickly, forcing the retraction. * Reset stale old blocks request after queue full * Revert "Reject headers with no gaps when ChainHead" This reverts commit 0eb865539e5dee37ab34f168f5fb643300de5ace. * Add BlockSet to BlockDownloader logging Currently it is difficult to debug this because there are two instances, one for OldBlocks and one for NewBlocks. This adds the BlockSet to all log messages for easy log filtering. * Reset OldBlocks download from last enqueued Previously when the ancient block queue was full it would restart the download from the last imported block, so the ones still in the queue would be redownloaded. Keeping the existing downloader instance and just resetting it will start again from the last enqueued block.:wq * Ignore expired Body and Receipt requests * Log when ancient block download being restarted * Only request old blocks from peers with >= difficulty https://github.com/paritytech/parity-ethereum/pull/9226 might be too permissive and causing the behaviour of the retraction soon after the fork block. With this change the peer difficulty has to be greater than or euqal to our syncing difficulty, so should still fix https://github.com/paritytech/parity-ethereum/issues/9225 * Some logging and clear stalled blocks head * Revert "Some logging and clear stalled blocks head" This reverts commit 757641d9b817ae8b63fec684759b0815af9c4d0e. * Reset stalled header if useless more than once * Store useless headers in HashSet * Add sync target to logging macro * Don't disable useless peer and fix log macro * Clear useless headers on reset and comments * Use custom error for collecting blocks Previously we resued BlockImportError, however only the Invalid case and this made little sense with the QueueFull error. * Remove blank line * Test for reset sync after consecutive useless headers * Don't reset after consecutive headers when chain head * Delete commented out imports * Return DownloadAction from collect_blocks instead of error * Don't reset after round complete, was causing test hangs * Add comment explaining reset after useless * Replace HashSet with counter for useless headers * Refactor sync reset on bad block/queue full * Add missing target for log message * Fix compiler errors and test after merge * ethcore: revert ethereum tests submodule update * Add hardcoded headers (#9730) * add foundation hardcoded header #6486017 * add ropsten hardcoded headers #4202497 * add kovan hardcoded headers #9023489 * gitlab ci: releasable_branches: change variables condition to schedule (#9729) |
||
---|---|---|
.cargo | ||
.github | ||
chainspec | ||
devtools | ||
docs | ||
ethash | ||
ethcore | ||
ethkey | ||
ethstore | ||
evmbin | ||
hash-fetch | ||
hw | ||
ipfs | ||
json | ||
local-store | ||
logger | ||
machine | ||
miner | ||
parity | ||
parity-clib | ||
parity-clib-examples/cpp | ||
price-info | ||
registrar | ||
rpc | ||
rpc_cli | ||
rpc_client | ||
scripts | ||
secret_store | ||
updater | ||
util | ||
whisper | ||
.dockerignore | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
.gitmodules | ||
Cargo.lock | ||
Cargo.toml | ||
CHANGELOG.md | ||
LICENSE | ||
license_header | ||
README.md | ||
rust-toolchain | ||
rustfmt.toml | ||
SECURITY.md | ||
test.sh |
The fastest and most advanced Ethereum client.
» Download the latest release «
Built for mission-critical use: Miners, service providers, and exchanges need fast synchronisation and maximum uptime. Parity Ethereum provides the core infrastructure essential for speedy and reliable services.
- Clean, modular codebase for easy customisation
- Advanced CLI-based client
- Minimal memory and storage footprint
- Synchronise in hours, not days with Warp Sync
- Modular for light integration into your service or product
Technical Overview
Parity Ethereum's goal is to be the fastest, lightest, and most secure Ethereum client. We are developing Parity Ethereum using the sophisticated and cutting-edge Rust programming language. Parity Ethereum is licensed under the GPLv3 and can be used for all your Ethereum needs.
By default, Parity Ethereum runs a JSON-RPC HTTP server on port :8545
and a Web-Sockets server on port :8546
. This is fully configurable and supports a number of APIs.
If you run into problems while using Parity Ethereum, check out the wiki for documentation, feel free to file an issue 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 Ethereum's current beta-release is 2.1. You can download it at the releases page or follow the instructions below to build from source. Please, mind the CHANGELOG.md for a list of all changes between different versions.
Build Dependencies
Parity Ethereum requires Rust version 1.29.x 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 Ethereum also requires
gcc
,g++
,libudev-dev
,pkg-config
,file
,make
, andcmake
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 themsvc
toolchain:$ rustup default stable-x86_64-pc-windows-msvc
Once you have rustup
installed, then you need to install:
Make sure that these binaries are in your PATH
. After that, you should be able to build Parity Ethereum from source.
Build from Source Code
# download Parity Ethereum code
$ git clone https://github.com/paritytech/parity-ethereum
$ cd parity-ethereum
# build in release mode
$ cargo build --release --features final
This produces 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 errors, it's in most cases your outdated version of Rust, or some of your crates have to be recompiled. Cleaning the repository will most likely solve the issue if you are on the latest stable version of Rust, try:
$ cargo clean
This always compiles the latest nightly builds. If you want to build stable or beta, do a
$ git checkout stable
or
$ git checkout beta
Simple One-Line Installer for Mac and Linux
bash <(curl https://get.parity.io -L)
The one-line installer always defaults to the latest beta release. To install a stable release, run:
bash <(curl https://get.parity.io -L) -r stable
Start Parity Ethereum
Manually
To start Parity Ethereum manually, just run
$ ./target/release/parity
so Parity Ethereum begins syncing the Ethereum blockchain.
Using systemd
service file
To start Parity Ethereum as a regular user using systemd
init:
- Copy
./scripts/parity.service
to yoursystemd
user directory (usually~/.config/systemd/user
). - To configure Parity Ethereum, write a
/etc/parity/config.toml
config file, see Configuring Parity Ethereum for details.
Parity Ethereum toolchain
In addition to the Parity Ethereum client, there are additional tools in this repository available:
- evmbin - EVM implementation for Parity Ethereum.
- ethabi - Parity Ethereum function calls encoding.
- ethstore - Parity Ethereum key management.
- ethkey - Parity Ethereum keys generator.
- whisper - Implementation of Whisper-v2 PoC.
Join the chat!
Questions? Get in touch with us on Gitter:
Alternatively, join our community on Matrix:
Documentation
Official website: https://parity.io
Be sure to check out our wiki for more information.