c8f57315a8
* Merge pull request #7368 from paritytech/td-future-blocks Wait for future blocks in AuRa * Advance AuRa step as far as we can and prevent invalid blocks. (#7451) * Advance AuRa step as far as we can. * Wait for future blocks. * Problem: AuRa's unsafeties around step duration (#7282) Firstly, `Step.duration_remaining` casts it to u32, unnecesarily limiting it to 2^32. While theoretically this is "good enough" (at 3 seconds steps it provides room for a little over 400 years), it is still a lossy way to calculate the remaining time until the next step. Secondly, step duration might be zero, triggering division by zero in `Step.calibrate` Solution: rework the code around the fact that duration is typically in single digits and never grows, hence, it can be represented by a much narrower range (u16) and this highlights the fact that multiplying u64 by u16 will only result in an overflow in even further future, at which point we should panic informatively (if anybody's still around) Similarly, panic when it is detected that incrementing the step counter wrapped around on the overflow of usize. As for the division by zero, prevent it by making zero an invalid value for step duration. This will make AuRa log the constraint mismatch and panic (after all, what purpose would zero step duration serve? it makes no sense within the definition of the protocol, as finality can only be achieved as per the specification if messages are received within the step duration, which would violate the speed of light and other physical laws in this case). * Fix tests. * detect different node, same-key signing in aura (#7245) * detect different node, same-key signing in aura * reduce scope of warning |
||
|---|---|---|
| dapps | ||
| devtools | ||
| docker | ||
| ethash | ||
| ethcore | ||
| ethcrypto | ||
| ethkey | ||
| ethstore | ||
| evmbin | ||
| evmjit | ||
| hash-fetch | ||
| hw | ||
| ipc | ||
| ipc-common-types | ||
| ipfs | ||
| js | ||
| json | ||
| local-store | ||
| logger | ||
| mac | ||
| nsis | ||
| parity | ||
| rpc | ||
| rpc_cli | ||
| rpc_client | ||
| scripts | ||
| secret_store | ||
| snap | ||
| stratum | ||
| sync | ||
| updater | ||
| util | ||
| windows/ptray | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| LICENSE | ||
| license_header | ||
| README.md | ||
| 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 beta-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 1.7.x-beta 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 | shParity also requires
gcc,g++,libssl-dev/openssl,libudev-devandpkg-configpackages to be installed. -
OSX:
$ curl https://sh.rustup.rs -sSf | shclangis 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.serviceto your systemd user directory (usually~/.config/systemd/user). -
To pass any argument to Parity, write a
~/.parity/parity.conffile this way:ARGS="ARG1 ARG2 ARG3".Example:
ARGS="ui --identity MyMachine".