The fast, light, and robust client for Ethereum-like networks.

Last update: Dec 24, 2022

Overview

The Fastest and most Advanced Ethereum Client.

Description
Technical Overview
Building
3.1 Building Dependencies
3.2 Building from Source Code
3.3 Simple One-Line Installer for Mac and Linux
3.4 Starting Parity Ethereum
Testing
Documentation
Toolchain
Community
Contributing
License

1. Description

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

2. 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.6. 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.

3. Building

3.1 Build Dependencies

Parity Ethereum requires latest stable Rust version 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++, pkg-config, file, make, and cmake 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 installed, then you need to install:

Perl
Yasm

Make sure that these binaries are in your PATH. After that, you should be able to build Parity Ethereum from source.

3.2 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

$ git checkout beta

3.3 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

3.4 Starting 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 your systemd user directory (usually ~/.config/systemd/user).
Copy release to bin folder, write sudo install ./target/release/parity /usr/bin/parity
To configure Parity Ethereum, write a /etc/parity/config.toml config file, see Configuring Parity Ethereum for details.

4. Testing

Download the required test files: git submodule update --init --recursive. You can run tests with the following commands:

All packages
```
cargo test --all
```
Specific package
```
cargo test --package <spec>
```

Replace <spec> with one of the packages from the package list (e.g. cargo test --package evmbin).

You can show your logs in the test output by passing --nocapture (i.e. cargo test --package evmbin -- --nocapture)

5. Documentation

Official website: https://parity.io

Be sure to check out our wiki for more information.

Viewing documentation for Parity Ethereum packages

You can generate documentation for Parity Ethereum Rust packages that automatically opens in your web browser using rustdoc with Cargo (of the The Rustdoc Book), by running the the following commands:

All packages

cargo doc --document-private-items --open

Specific package

cargo doc --package <spec> -- --document-private-items --open

Use--document-private-items to also view private documentation and --no-deps to exclude building documentation for dependencies.

Replacing <spec> with one of the following from the details section below (i.e. cargo doc --package parity-ethereum --open):

Package List

Parity Ethereum (EthCore) Client Application
```
parity-ethereum
```
Parity Ethereum Account Management, Key Management Tool, and Keys Generator
```
ethcore-accounts, ethkey-cli, ethstore, ethstore-cli
```
Parity Chain Specification
```
chainspec
```
Parity CLI Signer Tool & RPC Client
```
cli-signer parity-rpc-client
```
Parity Ethereum Ethash & ProgPoW Implementations
```
ethash
```
Parity (EthCore) Library
```
ethcore
```
- Parity Ethereum Blockchain Database, Test Generator, Configuration, Caching, Importing Blocks, and Block Information
```
ethcore-blockchain
```
- Parity Ethereum (EthCore) Contract Calls and Blockchain Service & Registry Information
```
ethcore-call-contract
```
- Parity Ethereum (EthCore) Database Access & Utilities, Database Cache Manager
```
ethcore-db
```
- Parity Ethereum Virtual Machine (EVM) Rust Implementation
```
evm
```
- Parity Ethereum (EthCore) Light Client Implementation
```
ethcore-light
```
- Parity Smart Contract based Node Filter, Manage Permissions of Network Connections
```
node-filter
```
- Parity Private Transactions
```
ethcore-private-tx
```
- Parity Ethereum (EthCore) Client & Network Service Creation & Registration with the I/O Subsystem
```
ethcore-service
```
- Parity Ethereum (EthCore) Blockchain Synchronization
```
ethcore-sync
```
- Parity Ethereum Common Types
```
common-types
```
- Parity Ethereum Virtual Machines (VM) Support Library
```
vm
```
- Parity Ethereum WASM Interpreter
```
wasm
```
- Parity Ethereum WASM Test Runner
```
pwasm-run-test
```
- Parity EVM Implementation
```
evmbin
```
- Parity Ethereum IPFS-compatible API
```
parity-ipfs-api
```
- Parity Ethereum JSON Deserialization
```
ethjson
```
- Parity Ethereum State Machine Generalization for Consensus Engines
```
parity-machine
```

Parity Ethereum (EthCore) Miner Interface

ethcore-miner parity-local-store price-info ethcore-stratum using_queue

Parity Ethereum (EthCore) Logger Implementation
```
ethcore-logger
```
C bindings library for the Parity Ethereum client
```
parity-clib
```
Parity Ethereum JSON-RPC Servers
```
parity-rpc
```
Parity Ethereum (EthCore) Secret Store
```
ethcore-secretstore
```
Parity Updater Service
```
parity-updater parity-hash-fetch
```

Parity Core Libraries (Parity Util)

ethcore-bloom-journal blooms-db dir eip-712 fake-fetch fastmap fetch ethcore-io
journaldb keccak-hasher len-caching-lock macros memory-cache memzero
migration-rocksdb ethcore-network ethcore-network-devp2p panic_hook
patricia-trie-ethereum registrar rlp_compress rlp_derive parity-runtime stats
time-utils triehash-ethereum unexpected parity-version

Contributing to documentation for Parity Ethereum packages

Document source code for Parity Ethereum packages by annotating the source code with documentation comments.

Example (generic documentation comment):

/// Summary
///
/// Description
///
/// # Panics
///
/// # Errors
///
/// # Safety
///
/// # Examples
///
/// Summary of Example 1
///
/// ```rust
/// // insert example 1 code here for use with documentation as tests
/// ```
///

6. Toolchain

In addition to the Parity Ethereum client, there are additional tools in this repository available:

evmbin - Parity Ethereum EVM Implementation.
ethstore - Parity Ethereum Key Management.
ethkey - Parity Ethereum Keys Generator.

The following tool is available in a separate repository:

ethabi - Parity Ethereum Encoding of Function Calls. Docs here
whisper - Parity Ethereum Whisper-v2 PoC Implementation.

7. Community

Join the chat!

Questions? Get in touch with us on Gitter:

Alternatively, join our community on Matrix:

8. Contributing

An introduction has been provided in the "So You Want to be a Core Developer" presentation slides by Hernando Castano. Additional guidelines are provided in CONTRIBUTING.

Contributor Code of Conduct

CODE_OF_CONDUCT

9. License

LICENSE

Comments

Memory usage spike induced crash

Parity Ethereum version: 2.2.10
Operating system: Linux
Installation: one-line installer
Fully synchronized: yes
Network: ethereum
Restarted: yes

The logs before parity shuts down

2019-02-16 20:43:45 UTC Imported #7229128 0xd4a8…60a3 (67 txs, 8.00 Mgas, 808 ms, 27.78 KiB)
2019-02-16 20:43:53 UTC   29/50 peers   6 MiB chain 105 MiB db 0 bytes queue 144 KiB sync  RPC:  0 conn,    8 req/s,  647 µs
2019-02-16 20:44:03 UTC Imported #7229129 0x5158…5fb6 (141 txs, 7.99 Mgas, 1267 ms, 29.82 KiB)
2019-02-16 20:44:11 UTC Imported #7229130 0xe8a2…6339 (153 txs, 7.96 Mgas, 1808 ms, 22.25 KiB)
2019-02-16 20:44:23 UTC   29/50 peers   5 MiB chain 105 MiB db 0 bytes queue 144 KiB sync  RPC:  0 conn,    5 req/s,  668 µs
2019-02-16 20:44:28 UTC Imported #7229132 0x34f5…ab4b (5 txs, 0.40 Mgas, 96 ms, 2.03 KiB)
2019-02-16 20:44:28 UTC Finishing work, please wait...
2019-02-16 20:45:35 UTC Shutdown is taking longer than expected.
2019-02-16 20:49:35 UTC Shutdown timeout reached, exiting uncleanly.

This happens randomly.

F2-bug 🐞 P0-dropeverything 🌋 M4-core ⛓

opened by SimonHausdorf 130

Node is failing to sync with error "Error: Error(Engine(RequiresClient)"

Parity Ethereum version: tried 2.2.5 and 2.2.1
Operating system: Ubuntu 16/18
Installation: downloaded binary
Fully synchronized: no and yes
Network: POA xDAI
Restarted: both Error log:

2018-12-19 13:31:46  Stage 3 block verification failed for #1210413 (0xc2a1…9c29)
Error: Error(Engine(RequiresClient), State { next_error: None, backtrace: InternalBacktrace { backtrace: None } })
2018-12-19 13:31:46  
Bad block detected: Error(Engine(RequiresClient), State { next_error: None, backtrace: InternalBacktrace { backtrace: None } })
RLP: f90249f90244a015bf167c5b4c07587408ce07860c6a8a6f4ea098c2457f86042575e4073db456a01dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347946dc0c0be4c8b2dfe750156dc7d59faabfb5b923da0518feb50424fef5033af4fd2d11281e7919218c2538d45db7433191e3c0347d0a056e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421a056e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421b901000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000090fffffffffffffffffffffffffffffffd8312782d8398968080845c1a1e0c9fde830202018f5061726974792d457468657265756d86312e33302e31826c6984126b9f9cb8416432efb986cffdd90973796712f64819aa5daa07ecd21a40284c6a82f1dd7fe64e031a733e95c40e6dae2f9d52c0b56c4f380b189ce17409fe79066d0cf4109b00c0c0
Header: Header { parent_hash: 0x15bf167c5b4c07587408ce07860c6a8a6f4ea098c2457f86042575e4073db456, timestamp: 1545215500, number: 1210413, author: 0x6dc0c0be4c8b2dfe750156dc7d59faabfb5b923d, transactions_root: 0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421, uncles_hash: 0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347, extra_data: [222, 131, 2, 2, 1, 143, 80, 97, 114, 105, 116, 121, 45, 69, 116, 104, 101, 114, 101, 117, 109, 134, 49, 46, 51, 48, 46, 49, 130, 108, 105], state_root: 0x518feb50424fef5033af4fd2d11281e7919218c2538d45db7433191e3c0347d0, receipts_root: 0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421, log_bloom: 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, gas_used: 0, gas_limit: 10000000, difficulty: 340282366920938463463374607431768211453, seal: [[132, 18, 107, 159, 156], [184, 65, 100, 50, 239, 185, 134, 207, 253, 217, 9, 115, 121, 103, 18, 246, 72, 25, 170, 93, 170, 7, 236, 210, 26, 64, 40, 76, 106, 130, 241, 221, 127, 230, 78, 3, 26, 115, 62, 149, 196, 14, 109, 174, 47, 157, 82, 192, 181, 108, 79, 56, 11, 24, 156, 225, 116, 9, 254, 121, 6, 109, 12, 244, 16, 155, 0]], hash: Some(0xc2a1a685d2cedd5f3c69826bfb7a8210213dd58e177dd438512baaa717cb9c29) }
Uncles: 
Transactions:

We have launched a number of validator nodes at xDAI network (statistics at https://dai-netstat.poa.network) at AWS that works pretty fine. After that we have tried to launch one of the nodes via the same way, but at the local infrastructure (Protofire Validator). Node is hided behind the NAT, and 30303 port were made public. It worked fine for some time and then errors started to occur (see logs above). We've launched a full resync, and it helped, but for a short period of time only. We've decided, that the roots of that issue might lie in a fact that Ubuntu 18 were used. So we launched an Ubuntu 16, but it didn't help. Can you help us solving the issue?

F2-bug 🐞 P2-asap 🌊 M4-core ⛓ A3-stale 🍃

opened by ArseniiPetrovich 102

Archive node loses peers (stop syncing blocks)

Parity Ethereum version: 2.4.6
Operating system: Linux
Installation: docker
Fully synchronized: yes
Network: ethereum mainnet
Restarted: yes

Machine spec: 8 CPU 64GB ram, parity cache-size= 32GB

We have launched archive node and complete its sync. Today we update the node from 2.4.5. to 2.4.6 and run some software that fetch blocks information.

It's working, but peers connection is unstable and after some time node stop syncing blocks (it just displays Syncing 0.00 0.00 blk/s )

Below is examples of peers pump and down logs and last blocks (reversed order)

peers info



2019-06-05 20:32:52 UTC   12/25 peers     60 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 34380 µs
--
2019-06-05 20:32:12 UTC   10/25 peers     54 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 32475 µs
2019-06-05 20:31:40 UTC   10/25 peers     53 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 32475 µs
2019-06-05 20:31:05 UTC    9/25 peers     53 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 24494 µs
2019-06-05 20:30:34 UTC    9/25 peers     53 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 17362 µs
2019-06-05 20:29:55 UTC    9/25 peers     53 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 18661 µs
2019-06-05 20:29:20 UTC    9/25 peers     53 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    7 req/s, 17362 µs
2019-06-05 20:28:49 UTC    9/25 peers     52 MiB chain   16 MiB db  0 bytes queue   82 KiB sync  RPC:  1 conn,    1 req/s, 32642 µs
2019-06-05 20:28:15 UTC   10/25 peers     49 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 31118 µs
2019-06-05 20:27:41 UTC    6/25 peers     48 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    2 req/s, 25000 µs
2019-06-05 20:27:05 UTC    5/25 peers     48 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 25000 µs
2019-06-05 20:26:33 UTC    5/25 peers     48 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 20223 µs
2019-06-05 20:26:00 UTC    5/25 peers     48 MiB chain   16 MiB db  0 bytes queue   80 KiB sync  RPC:  1 conn,    1 req/s, 33003 µs
2019-06-05 20:26:00 UTC    4/25 peers     48 MiB chain   16 MiB db  0 bytes queue   80 KiB sync  RPC:  1 conn,    1 req/s, 33003 µs
2019-06-05 20:25:11 UTC    5/25 peers     48 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 33558 µs
2019-06-05 20:24:33 UTC    6/25 peers     47 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 33558 µs
2019-06-05 20:23:53 UTC    8/25 peers     47 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 30569 µs
2019-06-05 20:23:53 UTC    8/25 peers     47 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 30569 µs
2019-06-05 20:23:11 UTC    8/25 peers     47 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 26161 µs
2019-06-05 20:22:43 UTC Updated conversion rate to Ξ1 = US$248.89 (19132568 wei/gas)
2019-06-05 20:22:40 UTC    7/25 peers     47 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 17618 µs
2019-06-05 20:22:16 UTC    8/25 peers     47 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 15189 µs
2019-06-05 20:21:37 UTC    8/25 peers     46 MiB chain   16 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    4 req/s, 21464 µs
2019-06-05 20:21:02 UTC    7/25 peers     44 MiB chain   15 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 25221 µs
2019-06-05 20:21:02 UTC    7/25 peers     44 MiB chain   15 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 25221 µs
2019-06-05 20:20:31 UTC    7/25 peers     43 MiB chain   15 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 25221 µs
2019-06-05 20:19:50 UTC    5/25 peers     43 MiB chain   15 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    3 req/s, 25221 µs

stuck on block


2019-06-05 20:36:00 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7895893   21/25 peers     62 MiB chain   17 MiB db  0 bytes queue  443 MiB sync  RPC:  1 conn,    0 req/s, 46705 µs
2019-06-05 20:35:55 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7893988   21/25 peers     62 MiB chain   17 MiB db  0 bytes queue  355 MiB sync  RPC:  1 conn,    1 req/s, 46705 µs
2019-06-05 20:35:50 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7893988   21/25 peers     62 MiB chain   17 MiB db  0 bytes queue  176 MiB sync  RPC:  1 conn,    1 req/s, 46705 µs
2019-06-05 20:35:45 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7892083   20/25 peers     62 MiB chain   17 MiB db  0 bytes queue  147 MiB sync  RPC:  1 conn,    1 req/s, 38701 µs
2019-06-05 20:35:40 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7885225   21/25 peers     62 MiB chain   17 MiB db  0 bytes queue  551 MiB sync  RPC:  1 conn,    0 req/s, 38701 µs
2019-06-05 20:35:35 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7885225   19/25 peers     62 MiB chain   17 MiB db  0 bytes queue  401 MiB sync  RPC:  1 conn,    1 req/s, 38701 µs
2019-06-05 20:35:30 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7885225   19/25 peers     62 MiB chain   17 MiB db  0 bytes queue  318 MiB sync  RPC:  1 conn,    1 req/s, 38701 µs
2019-06-05 20:35:25 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7885225   19/25 peers     62 MiB chain   17 MiB db  0 bytes queue  212 MiB sync  RPC:  1 conn,    0 req/s, 33990 µs
2019-06-05 20:35:20 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7884971   17/25 peers     62 MiB chain   17 MiB db  0 bytes queue  140 MiB sync  RPC:  1 conn,    1 req/s, 33990 µs
2019-06-05 20:35:15 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7884971   16/25 peers     61 MiB chain   17 MiB db  0 bytes queue   60 MiB sync  RPC:  1 conn,    2 req/s, 33990 µs
2019-06-05 20:35:10 UTC Syncing #7901361 0xd3df…ad5c     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7884971   18/25 peers     61 MiB chain   17 MiB db  0 bytes queue   87 KiB sync  RPC:  1 conn,    1 req/s, 33990 µs
2019-06-05 20:35:08 UTC Syncing #7901361 0xd3df…ad5c     0.60 blk/s   59.2 tx/s    4.8 Mgas/s      0+    0 Qed  #7884971   17/25 peers     61 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    2 req/s, 32341 µs
2019-06-05 20:35:01 UTC Reorg to #7901360 0xba42…c2a0 (0x8d58…2732 #7901358 0x9dc9…e404 0x3b25…123b)
2019-06-05 20:35:00 UTC Syncing #7901359 0x8d58…2732     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    1 Qed  #7901360   13/25 peers     61 MiB chain   17 MiB db   98 KiB queue   80 KiB sync  RPC:  1 conn,    0 req/s, 33990 µs
2019-06-05 20:34:55 UTC Syncing #7901359 0x8d58…2732     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7901358   11/25 peers     61 MiB chain   17 MiB db  0 bytes queue   81 KiB sync  RPC:  1 conn,    1 req/s, 29244 µs
2019-06-05 20:34:51 UTC Syncing #7901359 0x8d58…2732     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7901358   11/25 peers     61 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 29244 µs
2019-06-05 20:34:46 UTC Syncing #7901359 0x8d58…2732     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7901358   11/25 peers     61 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 29244 µs
2019-06-05 20:34:45 UTC Syncing #7901359 0x8d58…2732     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7901358   11/25 peers     61 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 29244 µs
2019-06-05 20:34:45 UTC Syncing #7901359 0x8d58…2732     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed  #7901358   10/25 peers     61 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 29244 µs
2019-06-05 20:34:44 UTC Syncing #7901359 0x8d58…2732     0.06 blk/s    6.6 tx/s    0.4 Mgas/s      0+    0 Qed  #7901358   11/25 peers     61 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    1 req/s, 29244 µs
2019-06-05 20:34:30 UTC Imported #7901359 0x8d58…2732 (102 txs, 7.99 Mgas, 709 ms, 29.14 KiB)
2019-06-05 20:34:09 UTC Imported #7901358 0x9dc9…e404 (136 txs, 7.99 Mgas, 632 ms, 34.54 KiB)
2019-06-05 20:34:09 UTC   10/25 peers     61 MiB chain   17 MiB db  0 bytes queue   79 KiB sync  RPC:  1 conn,    0 req/s, 23838 µs
2019-06-05 20:33:43 UTC Imported #7901357 0xec21…a3fd (118 txs, 8.00 Mgas, 563 ms, 28.45 KiB)

Also we have usual full node and it's not faced this issue (it's just continue syncing normaly) After archive node restart it continuous syncing

Is it a bug? Or maybe we can do something to prevent restarting every two hours?

Thanks in advance

F2-bug 🐞 M4-core ⛓ A3-stale 🍃

opened by APshenkin 100

Can't keep peer count above min

Before filing a new issue, please provide the following information.

I'm running:

Which Parity version?: 1.8.6

Which operating system?: Ubuntu

How installed?: curl

Are you fully synchronized?: yes

Which network are you connected to?: ethereum

Did you try to restart the node?: yes

been running 1.8.5 with no problems since it was released. peer count was always at max peers or very close to it. since installing 1.8.6 (node has been synced for months, only stopped a few seconds) parity constantly drops below min peers.

i saw the "Please note, that the initial database compaction after upgrading might temporarily reduce the node's performance." but node performance includes peers connected?

[parity]
base_path = "/mnt/ethereum/io.parity.ethereum"
db_path = "/mnt/ethereum/io.parity.ethereum/chains"
keys_path = "$HOME/.local/share/io.parity.ethereum/keys"

[network]
min_peers = 20
max_peers = 40

[footprint]
pruning = "fast"
pruning_history = 64
db_compaction = "ssd"

Jan 10 23:07:52 example.com parity[7594]: 2018-01-10 23:07:52  Imported #4889458 6fa8…c365 (56 txs, 1.19 Mgas, 266.45 ms, 6.73 KiB)
Jan 10 23:08:19 example.com parity[7594]: 2018-01-10 23:08:19  Imported #4889459 c0b1…aa1f (113 txs, 7.99 Mgas, 523.31 ms, 31.44 KiB)
Jan 10 23:08:41 example.com parity[7594]: 2018-01-10 23:08:41    25/40 peers    224 KiB chain  111 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  2 req/s, 7395 µs
Jan 10 23:08:43 example.com parity[7594]: 2018-01-10 23:08:43  Imported #4889460 2d62…e353 (163 txs, 8.00 Mgas, 479.30 ms, 23.10 KiB)
Jan 10 23:08:57 example.com parity[7594]: 2018-01-10 23:08:57  Imported #4889461 3f88…9993 (307 txs, 7.99 Mgas, 626.78 ms, 37.46 KiB)
Jan 10 23:09:04 example.com parity[7594]: 2018-01-10 23:09:04  Imported #4889463 b72f…5509 (159 txs, 8.00 Mgas, 729.15 ms, 28.04 KiB) + another 1 block(s) containing 90 tx(s)
Jan 10 23:09:16 example.com parity[7594]: 2018-01-10 23:09:16    36/40 peers     19 MiB chain  112 MiB db 776 bytes queue   71 KiB sync  RPC:  2 conn,  4 req/s, 139 µs
Jan 10 23:09:36 example.com parity[7594]: 2018-01-10 23:09:36  Imported #4889464 161a…ae54 (144 txs, 8.00 Mgas, 437.09 ms, 25.87 KiB)
Jan 10 23:09:46 example.com parity[7594]: 2018-01-10 23:09:46  Imported #4889467 9b8d…a06e (157 txs, 8.00 Mgas, 507.49 ms, 29.25 KiB)
Jan 10 23:09:55 example.com parity[7594]: 2018-01-10 23:09:55    18/20 peers      4 MiB chain  112 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  1 req/s, 127 µs
Jan 10 23:10:31 example.com parity[7594]: 2018-01-10 23:10:31    18/20 peers      5 MiB chain  112 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  1 req/s, 140 µs
Jan 10 23:11:06 example.com parity[7594]: 2018-01-10 23:11:06     6/20 peers      6 MiB chain  112 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  2 req/s, 138 µs
Jan 10 23:11:19 example.com parity[7594]: 2018-01-10 23:11:19  Reorg to #4889468 b802…a9fa (9b8d…a06e #4889466 b708…aabf f42e…3606)
Jan 10 23:11:24 example.com parity[7594]: 2018-01-10 23:11:24  Imported #4889470 636c…15b1 (293 txs, 7.96 Mgas, 1130.40 ms, 37.64 KiB) + another 2 block(s) containing 535 tx(s)
Jan 10 23:11:37 example.com parity[7594]: 2018-01-10 23:11:37  Imported #4889473 8bcc…e2b8 (248 txs, 5.73 Mgas, 503.62 ms, 28.95 KiB) + another 1 block(s) containing 280 tx(s)
Jan 10 23:11:48 example.com parity[7594]: 2018-01-10 23:11:48    15/20 peers      8 KiB chain  113 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  0 req/s, 171 µs
Jan 10 23:12:38 example.com parity[7594]: 2018-01-10 23:12:38    12/20 peers      2 MiB chain  112 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  1 req/s, 101 µs
Jan 10 23:12:39 example.com parity[7594]: 2018-01-10 23:12:39    12/20 peers      5 MiB chain  112 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  2 req/s, 101 µs
Jan 10 23:12:53 example.com parity[7594]: 2018-01-10 23:12:53    11/20 peers      5 MiB chain  112 MiB db 776 bytes queue   71 KiB sync  RPC:  2 conn,  0 req/s, 101 µs
Jan 10 23:13:00 example.com parity[7594]: 2018-01-10 23:13:00  Imported #4889475 329a…6c85 (61 txs, 1.45 Mgas, 143.55 ms, 7.52 KiB) + another 1 block(s) containing 192 tx(s)
Jan 10 23:13:02 example.com parity[7594]: 2018-01-10 23:13:02  Imported #4889469 e58f…5f97 (247 txs, 7.98 Mgas, 446.68 ms, 33.19 KiB)
Jan 10 23:13:52 example.com parity[7594]: 2018-01-10 23:13:52     5/20 peers      8 MiB chain  113 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  0 req/s, 123 µs
Jan 10 23:13:52 example.com parity[7594]: 2018-01-10 23:13:52     5/20 peers      6 MiB chain  113 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  0 req/s, 123 µs
Jan 10 23:13:52 example.com parity[7594]: 2018-01-10 23:13:52     5/20 peers      6 MiB chain  113 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  0 req/s, 123 µs
Jan 10 23:13:52 example.com parity[7594]: 2018-01-10 23:13:52     5/20 peers      6 MiB chain  113 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  0 req/s, 123 µs
Jan 10 23:14:07 example.com parity[7594]: 2018-01-10 23:14:07  Syncing #4889475 329a…6c85     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #4889475   10/20 peers      4 MiB chain  113 MiB db  0 bytes queue   78 KiB sync  RPC:  2 conn,  1 req/s, 140 µs
Jan 10 23:14:31 example.com parity[7594]: 2018-01-10 23:14:31  Imported #4889485 e95a…d4c7 (188 txs, 7.97 Mgas, 980.32 ms, 28.97 KiB)
Jan 10 23:15:06 example.com parity[7594]: 2018-01-10 23:15:06     8/20 peers      9 MiB chain  115 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  1 req/s, 141 µs
Jan 10 23:15:07 example.com parity[7594]: 2018-01-10 23:15:07     8/20 peers      5 MiB chain  115 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  1 req/s, 139 µs
Jan 10 23:15:09 example.com parity[7594]: 2018-01-10 23:15:09     7/20 peers      5 MiB chain  115 MiB db  0 bytes queue   71 KiB sync  RPC:  2 conn,  0 req/s, 139 µs

F2-bug 🐞 P0-dropeverything 🌋 M4-core ⛓

opened by gaia 89

Parity warp sync is no longer very warpy.
I'm running:

Parity version: 1.7.0

Operating system: Windows

And installed: via installer

I just installed Parity onto a brand new computer with a fresh install of Windows 10 Pro. The computer has Hyper-V enabled and Docker, but otherwise is a stock Windows 10 Pro computer of reasonable power (Dell XPS 9560). It is connected via wireless ab/n 5GHz to a nearby router and is able to easily max out my internet connection (100Mb/s down, 12 Mb/s up).

It launched after install about 12 hours ago and at first warp sync was moving quickly. However, at about 91.46% warp restore (pretty shortly into the initial sync) the restore progress froze at 91.46% and best block started counting up from 0. About 12 hours later it is only up to best block 3,594,000.

On previous versions of parity launching Parity with no chain data and no extra parameters (other than the default ui) would result in a full restore in about an hour on a less powerful computer.

Over the course of this time, it has written 2 TB to disk (presumably mostly overwrites since I only have a 1TB disk) and it has read almost nothing off of disk (42MB). It has received ~7GB over the network and only sent about 300MB.

It seems there are several issues floating around about Parity's footprint (one of them even by me) and I apologize if this should have been a comment on one of those, but none of them expressed the same symptoms so I wasn't sure.

Some cumulative numbers across the lifetime of the process:
P0-dropeverything 🌋 F3-annoyance 💩 F7-footprint 🐾 Q7-involved 💪 M4-core ⛓
opened by MicahZoltu 80
Client occasionally stops importing new blocks
OpenEthereum version: v3.0.0-stable-b079d1746

Operating system: Linux

Installation: built from source

Fully synchronized: yes

Network: ethereum

Restarted: yes

Openethereum occasianally (1-3x per month) stops importing new blocks, simply goes silent without producing any error. Then we issue SIGTERM and we get "Finishing work, please wait..." message. But it does not finish in many minutes... so we kill the process with SIGKILL. Upon restarting everything works normally, until next such 'freeze'.

We first noticed this behaviour in Parity 2.7.2 several months ago and it is now present with Openethereum 3.0.0. We noticed this independently on two different hardware configurations, one fast synced, the other fatdb synced from scratch. There is a similar issue reported in #11737 and also #11539, but the latter is linked to slow block import. That is not the case here. Except for the 'freezes', everything is working responsively, fast and overall very well, block imports are very fast.

Any suggestions on how to debug this issue much appreciated. Thanks.
F2-bug 🐞 P2-asap 🌊 M4-core ⛓
opened by mdben1247 78
60 TPS ? (parity aura v1.11.11)
I am benchmarking Ethereum based PoA chains, with my toolbox chainhammer.

My initial results for a dockerized network of parity aura v1.11.8 nodes ...

... leaves space for improvements :-)

Initial -unoptimized- run:

More details here: https://gitlab.com/electronDLT/chainhammer/blob/master/parity.md#benchmarking

Please help ...

... by suggesting what we could try, to get this faster than 60 TPS.

(Ideally approx 8 times faster, to beat quorum IBFT.)

Thanks a lot!
Andreas

I'm running:

Which Parity version?: v1.11.8

Which operating system?: Linux

How installed?: via docker

Are you fully synchronized?: not relevant

Which network are you connected to?: private chain

Did you try to restart the node?: yes

actual behavior slow

expected behavior faster

steps to reproduce: See parity.md.

Z1-question 🙋‍♀️ M2-config 📂
opened by drandreaskrueger 60

RPC stops working after a while on parity v2.5.10

Parity Ethereum version: Parity-Ethereum/v2.5.10-stable-9f94473-20191112/x86_64-linux-gnu/rustc1.39.0
Operating system: Linux
Installation: built from source
Fully synchronized: yes
Network: ethereum
Restarted: yes

We have been running a parity node for ethereum mainnet for a few years now. Today we tried updating our software to v2.5.10 (from v2.5.6). We attempted this upgrade twice today but both times, the RPC API stopped working after a while. This is a behavior we had previously never seen (the RPC is just unresponsive).

Here you can see that the RPC was working for block 8929535 but at some point between that block and block 8929769 the RPC stopped responding. A restart fixed it. This has been reproduced twice in production:

ubuntu@parity:~/parity_builds/parity-ethereum$ curl --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545 --silent 
{"jsonrpc":"2.0","result":"0x8840ff","id":1}


ubuntu@parity:~/parity_builds/parity-ethereum$ time curl --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545 --silent 
^C

real	0m17.480s
user	0m0.000s
sys	0m0.004s
ubuntu@parity:~/parity_builds/parity-ethereum$ time curl --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545 --silent 
^C

real	0m57.002s
user	0m0.004s
sys	0m0.000s
ubuntu@parity:~/parity_builds/parity-ethereum$ sudo systemctl restart parity
ubuntu@parity:~/parity_builds/parity-ethereum$ time curl --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545 --silent 
{"jsonrpc":"2.0","result":"0x8841e9","id":1}

real	0m0.020s
user	0m0.000s
sys	0m0.004s

I couldn't find anything relevant on parity.log but in the following graph you can see that on November 13, 2019 at around 19:06:00 Mexico City time, the RPC became unresponsive (Nov 14, 2019 @ 01:06:00 UTC):

Here's the parity.log file from that time:

2019-11-14 01:02:01 UTC Verifier #4 INFO import  Imported #8929579 0x6762…b4e6 (48 txs, 2.20 Mgas, 297 ms, 9.26 KiB)
2019-11-14 01:02:21 UTC IO Worker #1 INFO import    37/50 peers      4 MiB chain    7 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,   40 req/s,  167 µs
2019-11-14 01:02:32 UTC Verifier #5 INFO import  Imported #8929580 0xeae1…5abb (15 txs, 0.57 Mgas, 79 ms, 2.86 KiB)
2019-11-14 01:02:40 UTC Verifier #0 INFO import  Imported #8929581 0x6924…f17f (221 txs, 9.90 Mgas, 1793 ms, 41.93 KiB)
2019-11-14 01:02:53 UTC Verifier #2 INFO import  Imported #8929582 0xd434…b28a (78 txs, 9.52 Mgas, 1448 ms, 17.77 KiB)
2019-11-14 01:03:03 UTC IO Worker #3 INFO import    39/50 peers      5 MiB chain    7 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,    0 req/s,  183 µs
2019-11-14 01:03:03 UTC Verifier #4 INFO import  Imported #8929583 0xe60c…5b58 (37 txs, 1.97 Mgas, 296 ms, 6.98 KiB)
2019-11-14 01:03:09 UTC Verifier #0 INFO import  Imported #8929584 0xa760…9224 (155 txs, 9.61 Mgas, 1373 ms, 25.70 KiB)
2019-11-14 01:03:17 UTC Verifier #5 INFO import  Imported #8929585 0xd138…a59e (52 txs, 6.89 Mgas, 316 ms, 9.09 KiB)
2019-11-14 01:03:30 UTC Verifier #0 INFO import  Imported #8929587 0x97bf…0e57 (5 txs, 6.62 Mgas, 18 ms, 1.91 KiB)
2019-11-14 01:03:38 UTC IO Worker #3 INFO import    38/50 peers      5 MiB chain    7 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,    0 req/s,  183 µs
2019-11-14 01:03:53 UTC Verifier #2 INFO import  Imported #8929588 0x6306…6bfa (87 txs, 4.49 Mgas, 696 ms, 18.67 KiB)
2019-11-14 01:04:04 UTC Verifier #3 INFO import  Imported #8929589 0x117f…5f1b (51 txs, 4.28 Mgas, 1298 ms, 9.14 KiB)
2019-11-14 01:04:14 UTC IO Worker #3 INFO import    41/50 peers      5 MiB chain    8 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,    0 req/s,  183 µs
2019-11-14 01:04:42 UTC Verifier #4 INFO import  Imported #8929590 0xba69…3933 (125 txs, 9.93 Mgas, 1750 ms, 25.23 KiB)
2019-11-14 01:04:54 UTC IO Worker #0 INFO import    41/50 peers      5 MiB chain    8 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,    0 req/s,  183 µs
2019-11-14 01:04:55 UTC Verifier #6 INFO import  Imported #8929592 0xfd99…7bef (241 txs, 9.81 Mgas, 1279 ms, 45.39 KiB)
2019-11-14 01:05:20 UTC Verifier #1 INFO import  Imported #8929593 0x4f91…00fe (32 txs, 8.93 Mgas, 234 ms, 6.42 KiB)
2019-11-14 01:05:32 UTC IO Worker #0 INFO import    41/50 peers      5 MiB chain    8 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,    0 req/s,  183 µs
2019-11-14 01:05:34 UTC Verifier #3 INFO import  Imported #8929594 0xc958…79e7 (160 txs, 9.89 Mgas, 1323 ms, 28.15 KiB)
2019-11-14 01:06:06 UTC IO Worker #2 INFO import    41/50 peers      5 MiB chain    8 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,    0 req/s,  183 µs
2019-11-14 01:06:16 UTC Verifier #1 INFO import  Imported #8929596 0xcc46…ebd6 (32 txs, 1.31 Mgas, 970 ms, 5.50 KiB)
2019-11-14 01:06:36 UTC IO Worker #2 INFO import    41/50 peers      6 MiB chain    8 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,    0 req/s,  183 µs
2019-11-14 01:07:06 UTC IO Worker #0 INFO import    41/50 peers      6 MiB chain    8 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,    0 req/s,  183 µs
2019-11-14 01:07:19 UTC Verifier #2 INFO import  Imported #8929597 0xe220…30ed (216 txs, 9.77 Mgas, 1239 ms, 42.55 KiB)
2019-11-14 01:07:40 UTC Verifier #3 INFO import  Imported #8929598 0xff62…482c (124 txs, 9.91 Mgas, 2876 ms, 34.78 KiB)
2019-11-14 01:07:50 UTC IO Worker #3 INFO import    41/50 peers      6 MiB chain    8 MiB db  0 bytes queue   34 KiB sync  RPC:  0 conn,    0 req/s,  183 µs
2019-11-14 01:07:59 UTC Verifier #7 INFO import  Imported #8929599 0xced4…f2b9 (60 txs, 9.89 Mgas, 1406 ms, 8.70 KiB)
2019-11-14 01:08:11 UTC Verifier #1 INFO import  Imported #8929600 0xf8f5…e13c (201 txs, 9.89 Mgas, 1593 ms, 35.78 KiB)
2019-11-14 01:08:22 UTC Verifier #2 INFO import  Imported #8929601 0xf95b…2457 (185 txs, 9.90 Mgas, 1763 ms, 30.34 KiB)

This is currently preventing us from supporting the Istanbul hard fork.

opened by vogelito 52

Parity Light Client Sync Stuck
Before filing a new issue, please provide the following information.

I'm running:

Parity version: Parity/v1.8.0-unstable-b9c1d0bd1-20170814/x86_64-macos/rustc1.18.0

Operating system: MacOS

And installed: from source (rustc 1.20.0-nightly (6d9d82d3d 2017-07-14))

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.

I tried running parity --light --scale-verifiers --num-verifiers 4 --fast-and-loose (and parity --light) but both times I get stuck at:

2017-08-16 21:42:48 Syncing #1925655 ac02…fc53 0 hdr/s 0+ 0 Qed #1925655 9/50 peers 2 MiB cache 0 bytes queue RPC: 1 conn, 4 req/s, 139 µs

I would expect it to sync all the way to the current tip, which is currently 4168389.
F2-bug 🐞 P2-asap 🌊 M4-core ⛓
opened by JeremyRubin 49
unreasonably high memory usage (without crash) and won't shut down
Greetings, sadly my Parity-Ethereum/v2.4.6-stable-94164e1-20190514/x86_64-linux-gnu/rustc1.34.1 node eats unreasonably high memory. Node log and process statistics in CSV : https://www.fusionsolutions.io/doc/memlog.tar.gz

Start parameters are:

--ipc-apis all --reserved-peers /own/config/archiveEthNode.txt --no-serve-light --no-periodic-snapshot --jsonrpc-allow-missing-blocks --no-persistent-txqueue --jsonrpc-server-threads 8 --ipc-path=/own/sockets/ethNode.ipc --min-gas-price=10000000 --tx-queue-mem-limit=4096 --tx-queue-size=256000 --reseal-on-txs=all --force-sealing --base-path "/mnt/node-1/eth" --rpcport 8548 --port 30306 --no-ws --no-secretstore --cache-size 4096 --log-file /own/log/nodes/eth/parity_eth_$DATE.log"

The memory usage will not be higher as 12gb.

On 16:20:20 have killed the process with KILLSIG, this is the only way that I can shut down the process.

I glad help with any trace parameters or statistics.
F7-footprint 🐾 M4-core ⛓
opened by iFA88 48
regression with 2.3.3 and 2.2.10: huge disk reads
Parity Ethereum version: 2.3.3-beta and 2.2.10-stable

Operating system: Linux

Installation: provided binaries

Fully synchronized: yes

Network: ethereum

Restarted: yes

Yesterday I upgraded my stable boxes from 2.2.9 zu 2.2.10 and my test box from 2.3.2-beta to 2.3.3-beta.

IO seems to be much higher than with 2.2.9 and 2.3.2 because a couple hours later all the EBS gp2 volumes the EC2 instances use had exhausted their BurstBalance credits.

From the monitoring I can see that versions 2.2.10 and 2.3.3 do much more disk reads than the versions before. Switching back to 2.2.9 and 2.3.2 resolved the issue: let the systems run for several hours, no heavy IO.

Switching back to 2.3.3 and 2.2.10: heavy disk reads was happening again.
P2-asap 🌊 F7-footprint 🐾 M4-core ⛓ M4-io 💾
opened by c0deright 47
Thread 'fetch' panicked at 'cannot access native cert store: Custom { kind: InvalidData, error: BadDER }', src/libcore/result.rs:1188
Before filing a new issue, please provide the following information.

If you think that your issue is an exploitable security vulnerability, please mail your bugreport to [email protected] instead; your submission might be eligible for our Bug Bounty. You can find mode info on the reporting process in SECURITY.md

OpenEthereum version: 0.0.0

Operating system: Windows / MacOS / Linux

Installation: homebrew / one-line installer / built from source

Fully synchronized: no / yes

Network: ethereum / ropsten / goerli / ...

Restarted: no / yes

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.
opened by Hen3 0
Very Slow Sync of Tracing Node
OpenEthereum version: 2.5.2 stable

Operating system: Linux

Installation: homebrew / one-line installer

Fully synchronized: no

Network: ethereum

Restarted: no

I was syncing the tracing node a MacBook and the sync occurred faster than on the server, however, the server is significantly more powerful than the MacBook. The current sync speed is approximately 1-3 blocks per second and the sync became exponentially slow after block 5,000,000.

The parameters of the config are presented below: --max-peers=40 --min-peers=20 --pruning=fast --tracing=on --cache-size=30000 --no-serve-light --no-periodic-snapshot --no-secretstore --no-ipc --jsonrpc-hosts all --jsonrpc-interface all --no-ws --scale-verifiers --mode=active
opened by Raid5594 0

sync is stuck at 10790000 for v3.1.0-rc.1

OpenEthereum version: v3.1.0-rc.1
Operating system: Linux
Installation: docker image from openethereum/openethereum docker hub
Fully synchronized: no
Network: ethereum
Restarted: yes

everything was working fine untill I reached block 10790000. sync is stuck now for 12 hours +

here is the output of logs:

020-11-02 20:29:47 UTC IO Worker #2 INFO import  Syncing snapshot 0/6052  #10790000   26/50 peers      1 MiB chain  0 bytes queue  RPC:  0 conn,    0 req/s,   26 µs  
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  46 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  14 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #2 DEBUG sync  47 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  38 -> Dispatching packet: 2                                                                                           
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2                                                                                           
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  38 -> Dispatching packet: 2  
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #2 DEBUG sync  8 -> Dispatching packet: 2 
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2                                                                                           
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  0 -> Dispatching packet: 2 
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  38 -> Dispatching packet: 2                                                                                           
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  0 -> Dispatching packet: 2   
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #1 DEBUG sync  14 -> Dispatching packet: 2                                                                                           
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  38 -> Dispatching packet: 2                                                                                                                                                                                                                                                                   
2020-11-02 20:29:47 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:29:47 UTC IO Worker #2 DEBUG sync  8 -> Dispatching packet: 2 
2020-11-02 20:29:47 UTC IO Worker #3 DEBUG sync  70 -> Dispatching packet: 2
...
2020-11-02 20:30:16 UTC IO Worker #3 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #0 DEBUG sync  14 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #3 DEBUG sync  37 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #3 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #0 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #3 DEBUG sync  0 -> Dispatching packet: 2 
2020-11-02 20:30:16 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #3 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:16 UTC IO Worker #2 DEBUG sync  4 -> Dispatching packet: 2 
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  14 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #3 INFO import  Syncing snapshot 0/6052  #10790000   26/50 peers      1 MiB chain  0 bytes queue  RPC:  0 conn,    0 req/s,   26 µs  
2020-11-02 20:30:17 UTC IO Worker #3 DEBUG sync  4 -> Dispatching packet: 2 
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #3 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #2 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #3 DEBUG sync  8 -> Dispatching packet: 2                                                                                            
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #1 DEBUG sync  8 -> Dispatching packet: 2 
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  14 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #1 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #3 DEBUG sync  8 -> Dispatching packet: 2 
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #3 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #0 DEBUG sync  14 -> Dispatching packet: 2
2020-11-02 20:30:17 UTC IO Worker #3 DEBUG sync  38 -> Dispatching packet
...
020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  14 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  0 -> Dispatching packet: 2 
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  0 -> Dispatching packet: 2 
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  14 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  0 -> Dispatching packet: 2 
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  4 -> Dispatching packet: 2 
2020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  0 -> Dispatching packet: 2 
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #1 DEBUG sync  8 -> Dispatching packet: 2 
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  14 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  0 -> Dispatching packet: 2 
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  38 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #2 DEBUG sync  77 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #0 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:21 UTC IO Worker #3 DEBUG sync  82 -> Dispatching packet: 2
2020-11-02 20:30:22 UTC IO Worker #2 DEBUG sync  14 -> Dispatching packet: 2
2020-11-02 20:30:22 UTC IO Worker #3 DEBUG sync  0 -> Dispatching packet: 2 
2020-11-02 20:30:22 UTC IO Worker #2 INFO import  Syncing snapshot 0/6052  #10790000   26/50 peers      1 MiB chain  0 bytes queue  RPC:  0 conn,    0 req/s,   26 µs

output of top not a problem of cpu/ram

mem: 12835504K used, 3174596K free, 4084K shrd, 204968K buff, 10684688K cached
CPU:   2% usr   1% sys   0% nic  95% idle   0% io   0% irq   0% sirq
Load average: 1.66 1.48 0.86 2/1400 78
  PID  PPID       USER     STAT   VSZ %VSZ CPU %CPU COMMAND
    1     0             openethe S     563m   4%   6       1% /home/openethereum/openethereum --config /etc/parity/config.toml
   68     0           openethe S     1644   0%   3        0% /bin/sh
   78    68          openethe R     1580   0%   2       0% top

here is my config toml

  [parity]
  mode = "last"
  mode_timeout = 300
  mode_alarm = 3600
  no_persistent_txqueue = false
  base_path = "/home/openethereum/.local/share/openethereum"
  db_path = "/home/openethereum/.local/share/openethereum/chains"
  keys_path = "/home/openethereum/.local/share/openethereum/keys"
  identity = "yolo"

  [network]
  port = 30303
  min_peers = 25
  max_peers = 50
  nat = "any"
  id = 1
  bootnodes = ["enode://d860a01f9722d78051619d1e2351aba3f43f943f6f00718d1b9baa4101932a1f5011f16bb2b1bb35db20d6fe28fa0bf09636d26a87d31de9ec6203eeedb1f666@18.138.108.67:30303","enode://22a8232c3abc76a16ae9d6c3b164f98775fe226f0917b0ca871128a74a8e9630b458460865bab457221f1d448dd9791d24c4e5d88786180ac185df813a68d4de@3.209.45.79:30303","enode://ca6de62fce278f96aea6ec5a2daadb877e51651247cb96ee310a318def462913b653963c155a0ef6c7d50048bba6e6cea881130857413d9f50a621546b590758@34.255.23.113:30303","enode://279944d8dcd428dffaa7436f25ca0ca43ae19e7bcf94a8fb7d1641651f92d121e972ac2e8f381414b80cc8e5555811c2ec6e1a99bb009b3f53c4c69923e11bd8@35.158.244.151:30303","enode://8499da03c47d637b20eee24eec3c356c9a2e6148d6fe25ca195c7949ab8ec2c03e3556126b0d7ed644675e78c4318b08691b7b57de10e5f0d40d05b09238fa0a@52.187.207.27:30303","enode://103858bdb88756c71f15e9b5e09b56dc1be52f0a5021d46301dbbfb7e130029cc9d0d6f73f693bc29b665770fff7da4d34f3c6379fe12721b5d7a0bcb5ca1fc1@191.234.162.198:30303","enode://715171f50508aba88aecd1250af392a45a330af91d7b90701c436b618c86aaa1589c9184561907bebbb56439b8f8787bc01f49a7c77276c58c1b09822d75e8e8@52.231.165.108:30303","enode://5d6d7cd20d6da4bb83a1d28cadb5d409b64edf314c0335df658c1a54e32c7c4a7ab7823d57c39b6a757556e68ff1df17c748b698544a55cb488b52479a92b60f@104.42.217.25:30303","enode://68f46370191198b71a1595dd453c489bbfe28036a9951fc0397fabd1b77462930b3c5a5359b20e99677855939be47b39fc8edcf1e9ff2522a922b86d233bf2df@144.217.153.76:30303","enode://ffed6382e05ee42854d862f08e4e39b8452c50a5a5d399072c40f9a0b2d4ad34b0eb5312455ad8bcf0dcb4ce969dc89a9a9fd00183eaf8abf46bbcc59dc6e9d5@51.195.3.238:30303","enode://b47b197244c054d385f25d7740b33cc7e2a74d6f715befad2b789fd3e3594bb1c8dd2ca2faf1a3bf6b4c9ec03e53b52301f722a2316b78976be03ccbe703c581@54.37.94.238:30303","enode://5f7d0794c464b2fcd514d41e16e4b535a98ac792a71ca9667c7cef35595dc34c9a1b793c0622554cf87f34006942abb526af7d2e37d715ac32ed02170556cce2@51.161.101.207:30303"]
  discovery = true
  warp = true
  allow_ips = "public"
  snapshot_peers = 0
  max_pending_peers = 64
  reserved_only = false

  [rpc]
  disable = false
  port = 8545
  interface = "local"
  cors = ["http://localhost:8000","http://localhost:8080","http://localhost:8545","http://localhost:8546"]
  apis = ["all"]
  hosts = ["none"]

  [websockets]
  disable = false
  port = 8546
  interface = "local"
  origins = ["none"]
  apis = ["all"]
  hosts = ["none"]

  [ipc]
  disable = false
  path = "/home/openethereum/.local/share/openethereum/jsonrpc.ipc"
  apis = ["all"]

  [secretstore]
  disable = false
  nodes = []
  http_interface = "local"
  http_port = 8082
  interface = "local"
  port = 8083
  path = "/home/openethereum/.local/share/openethereum/secretstore"

  [stratum]
  interface = "local"
  port = 8008
  secret = "************"

  [footprint]
  tracing = "auto"
  pruning = "auto"
  pruning_history = 64
  pruning_memory = 32
  cache_size_db = 128
  cache_size_blocks = 8
  cache_size_queue = 40
  cache_size_state = 25
  cache_size = 128 # Overrides above caches with total size
  fast_and_loose = false
  db_compaction = "ssd"
  fat_db = "auto"
  scale_verifiers = true
  num_verifiers = 6


  [misc]
  logging = "own_tx=trace,rpc=trace,sync=trace"
  log_file = "/home/openethereum/.local/share/openethereum/openethereum.log"
  color = true

curl --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545
{"jsonrpc":"2.0","result":"0xa4a470","id":1}

opened by zgorizzo69 0

update Whisper Options

Update Whisper Options from "paritytech" to "openetherem", since the github repo has been changed. This shows up when user use "-h".

opened by tczpl 0

trace_replayBlockTransactions used too much memory

hello. I met a problem. when I use 200 tiems trace_replayBlockTransactions rpc method , openethereum-linux-v3.0.1 will use too much memory：

config.toml:

[parity]

mode="active"
chain = "mainnet"
base_path = "/data/chaindata"

light = false
no_persistent_txqueue = true



[rpc]

disable = false

port = 39842

interface = "0.0.0.0"

cors = ["*"]

apis = ["all"]

hosts = ["all"]

server_threads = 1000

[websockets]

disable = false
port = 39843
interface = "local"
origins = ["all"]

# 浏览器的origin header

apis = ["all"]
hosts = ["all"]

[network]

port = 30303
min_peers = 3
max_peers = 6
snapshot_peers = 0
warp = true
max_pending_peers = 64

[mining]
# Parity will keep/relay at most 32768 transactions in queue.
tx_queue_size = 32768
# Maximum number of transactions per sender in the queue. By default it's 1% of the entire queue, but not less than 16.
tx_queue_per_sender = 8192
# Prepare a block to seal even when there are no miners connected.
force_sealing = true


[footprint]
cache_size = 10240
db_compaction = "ssd"
fast_and_loose = false


[misc]
logging = "own_tx=trace"
log_file = "/var/log/parity.log"
color = true

for block_number in range(4000000, 5000000):
    logger.info(block_number)
    payload = {"jsonrpc": "2.0", "method": "trace_replayBlockTransactions",
               "params": [hex(block_number),  ["trace"]], "id": 1}
    headers = {
        'Content-Type': 'application/json'
    }
    response = requests.request("POST", url, headers=headers, json=payload)
    data = response.json()
    result = data.get('result') or None

The important thing is that when I close the python program, the memory does not drop

Can I limit the memory usage of ethvm？

opened by forencen 0

RUSTSEC-2020-0058: crate has been renamed to `cipher`

crate has been renamed to cipher

| Details | | | ------------------- | ---------------------------------------------- | | Status | unmaintained | | Package | stream-cipher | | Version | 0.3.2 | | URL | https://github.com/RustCrypto/traits/pull/337 | | Date | 2020-10-15 |

This crate has been renamed from stream-cipher to cipher.

The new repository location is at:

<https://github.com/RustCrypto/traits/tree/master/cipher>

See advisory page for additional details.

opened by github-actions[bot] 0

Releases(v3.0.1)

v3.0.1(Jun 1, 2020)

This release contains a hotfix for #11744 that caused a massive network partition due to faulty FORK_ID generation.

ETH / MAINNET nodes are not affected by this issue but rather ETC

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | openethereum-macos-v3.0.1.zip | f41cb1f49727ccf09e4f34b964fdfa9ad3802a046f6acd6c349a41020cdcf1c7 | | | x64 | openethereum-linux-v3.0.1.zip | 8dd753058e5db77ffaede5a53418005f9c8133212448e11df9169a651cdac997 | | | x64 | openethereum-windows-v3.0.1.zip | 42c05ed84a0588110afd8fe379685335cf792660d6684fc90cdac54695dda636 | | | | | | | System | Option | - | Resource | | | Docker | - | hub.docker.com/r/openethereum/openethereum |
Source code(tar.gz)
Source code(zip)
openethereum-linux-v3.0.1.zip(19.69 MB)
openethereum-macos-v3.0.1.zip(18.92 MB)
openethereum-windows-v3.0.1.zip(19.57 MB)
v3.0.0(May 11, 2020)
OpenEthereum v3.0.0 is the first release of OpenEthereum client as part of OpenEthereum project, divested from Parity Technologies.

This release marks the transition from Parity Technologies infrastructure and bootnodes to the one managed by OpenEthereum project.

Parity-Ethereum v2.7 users can continue using their existing data folders. Command-line interface has also stayed identical. Unless specified otherwise, OpenEthereum v3.0.0 will detect if the user's database in the old Parity-Ethereum default path, and only if it's not found will write to the new default location.

This release includes several major improvements to network and database stack:

Support for eth/64 protocol and Node Discovery v4 Ethereum Node Records extension.

Accounts bloom is removed which should decrease the database size.

Due to database changes this is a one-way upgrade. Please back up your database if you plan to continue using Parity-Ethereum v2.7.2.

Note that this release drops support for IPFS and eth/62 protocol. Additionally, it marks light client, private transactions and updater as deprecated features which may be removed in a future release.

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | openethereum-macos-v3.0.0.zip | 6990be730d82b7135e2e7d6563c88806fb01f1e1ecb161b637936d46b6170003 | | | x64 | openethereum-linux-v3.0.0.zip | 202b14eb8c3ec0bb281293b37668427a1e627ee55d221a0326814e35209419d3 | | | x64 | openethereum-windows-v3.0.0.zip | c58b9d2d2a7f2111485f370bbfffe89ecd275cfc631f28978fc9097f5eb92bac | | | | | | | System | Option | - | Resource | | | Docker | - | hub.docker.com/r/openethereum/openethereum |
Source code(tar.gz)
Source code(zip)
openethereum-linux-v3.0.0.zip(19.69 MB)
openethereum-macos-v3.0.0.zip(18.93 MB)
openethereum-windows-v3.0.0.zip(19.57 MB)
v2.7.2(Feb 6, 2020)
Parity Ethereum v2.7.2-stable is a patch version release of parity-ethereum. Starting in the 2.7.x series of releases, parity-ethereum is switching to a single stable release track. As a result, any clients that currently receive updates from the beta track should switch to the stable track. Due to database format changes, upgrading from 2.5.x or 2.6.x is one-way only.

The full list of included changes:

[eth classic chainspec]: remove balance = 1 (#11458)

backwards compatible call_type creation_method (#11450 + #11455)

chore: remove unused dependencies (#11432)

Cargo.lock: new lockfile format (#11448)

rlp_derive: cleanup (#11446)

Avoid long state queries when serving GetNodeData requests (#11444)

update kvdb-rocksdb to 0.4 (#11442)

Remove dead bootnodes, add new geth bootnodes (#11441)

goerli: replace foundation bootnode (#11433)

fix: export hardcoded sync format (#11416)

verification: fix race same block + misc (#11400)

update classic testnet bootnodes (#11398)

gcc to clang (#11453)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | e91815a9caecee0ab3504ea92c0845348432501b166f7da03c7b41ff66b97072 | | | x64 | parity | 2d0de1bf66f5ae693e44c474065fc9a24957463ee33c075731b06ce930139a61 | | | x64 | parity | fe992f0c9b229a4406e82b9ff6d388f4acb4d6ce2782cb79b7bc379e7965ae34 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.7.2 |
Source code(tar.gz)
Source code(zip)
v2.6.8(Dec 31, 2019)
Parity Ethereum v2.6.8-beta is a security release. Valid blocks with manipulated transactions (added/replaced) cause the client to stall.

The full list of included changes:

Make sure to not mark block header hash as invalid if only the body is wrong (#11356)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | b057d996da8af4d708d3d9258b633d42afe04883c2b7f4706b06c62564b74798 | | | x64 | parity | fe7a8dd36aed3081706fc5a48e4cd63b5ef4fccfeb7bf0a668230edfacb62285 | | | x64 | parity | 299f928503cb3b8d44d95a0f592e32358542ec854842c277e3eeaee2a3478a28 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.6.8 |
Source code(tar.gz)
Source code(zip)
v2.5.13(Dec 31, 2019)
Parity Ethereum v2.5.13-stable is a security release. Valid blocks with manipulated transactions (added/replaced) cause the client to stall.

The full list of included changes:

Make sure to not mark block header hash as invalid if only the body is wrong (#11356)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 7ff4a7929bcf6b4d3dfdea23657813a70c6c34b8fe3fadb6a5d35ca4b3564f90 | | | x64 | parity | 64da3acaa2121d176f53703ee32483a8b6e330536c7bfcbf146faa192ffe5435 | | | x64 | parity | e133fb316c7829d9291bb73ceb3053409053d03603565a2b4d2a582c9ad4c84b | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.13 |
Source code(tar.gz)
Source code(zip)
v2.6.7(Dec 16, 2019)
Parity Ethereum v2.6.7-beta is a patch release that adds Istanbul hardfork block numbers for POA and xDai networks, implements ECIP-1056 and implements EIP-2384/2387 - Muir Glacier.

The full list of included changes:

Enable EIP-2384 for ice age hard fork (#11281)

ethcore/res: activate agharta on classic 9573000 (#11331)

Istanbul HF in xDai (2019-12-12) (#11299)

Istanbul HF in POA Core (2019-12-19) (#11298)

Istanbul HF in POA Sokol (2019-12-05) (#11282)

Activate ecip-1061 on kotti and mordor (#11338)

Enable basic verification of local transactions (#11332)

Disallow EIP-86 style null signatures for transactions outside tests (#11335)

SecretStore database migration to v4 (#11322)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 95a42cafb7357df41f3c89e30825835066e88d26a97a4d3e28628820969a8b6d | | | x64 | parity | a2aa2123d46c4b40900eae546ad6e6c31009c7c5f9b99f4218f18129bac73e95 | | | x64 | parity | bbda5f6e12eb60fbd9ac9fd6bcf182cbbe32c8535dcda2b5a088dbcd65af80c2 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.6.7 |
Source code(tar.gz)
Source code(zip)
v2.5.12(Dec 16, 2019)
Parity Ethereum v2.5.12-stable is a patch release that adds Istanbul hardfork block numbers for POA and xDai networks, implements ECIP-1056 and implements EIP-2384/2387 - Muir Glacier.

The full list of included changes:

Enable EIP-2384 for ice age hard fork (#11281)

ethcore/res: activate agharta on classic 9573000 (#11331)

Istanbul HF in xDai (2019-12-12) (#11299)

Istanbul HF in POA Core (2019-12-19) (#11298)

Istanbul HF in POA Sokol (2019-12-05) (#11282)

Activate ecip-1061 on kotti and mordor (#11338)

Enable basic verification of local transactions (#11332)

Disallow EIP-86 style null signatures for transactions outside tests (#11335)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | ff5031b6de4b9a24c8484a804b051ee6b0362e57a8144a2a7d6a9ee7144ddacc | | | x64 | parity | 776b10da9ce3a452487b80fc70c68bb8dd4ea2556670b4ee1f4b872f6fec0ca8 | | | x64 | parity | cdde772ed07bb1f9a4e67e76974c386e207b0fae34509baefbe7ca3a38314a00 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.12 |
Source code(tar.gz)
Source code(zip)
v2.6.6(Dec 5, 2019)
Parity Ethereum v2.6.6-beta is an emergency patch release that adds the missing eip1344_transition for mainnet - Users are advised to update as soon as possible to prevent any issues with the imminent Istanbul hardfork

The full list of included changes:

[chainspec]: add eip1344_transition for istanbul (#11301)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 2aa75efd83e2dd1439aa955578f4192804cfbc51589a6046a6c68f6385f47853 | | | x64 | parity | e74078171251bb4653982f4da87fcd1c228d714091a9d7d6b60eecb2d209dac4 | | | x64 | parity | 4449d10146ae257f20fc9c39380bde32bed5f049564209e8faec916783c3b75a | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.6.6 |
Source code(tar.gz)
Source code(zip)
v2.5.11(Dec 5, 2019)
Parity Ethereum v2.5.11-stable is an emergency patch release that adds the missing eip1344_transition for mainnet - Users are advised to update as soon as possible to prevent any issues with the imminent Istanbul hardfork

The full list of included changes:

[chainspec]: add eip1344_transition for istanbul (#11301)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | a6f466fda1a7b1989fe8345661c89e7aa71298636a799b907a9730ba2451416e | | | x64 | parity | 829de731e081fe4eccd5b1ae70297b2ded7f9e712d36ed63aa6e8b1066f35073 | | | x64 | parity | 20fba204357758008a4f2fac29da552e79863980424a98d1c20fc228690e33a4 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.11 |
Source code(tar.gz)
Source code(zip)
v2.6.5(Nov 13, 2019)
Parity Ethereum v2.6.5-beta is a patch release that adds block numbers for activating the Istanbul hardfork on mainnet, as well as a large number of various bugfixes, QoL changes, some code cleanup/refactoring and other miscellaenous changes.

This release removes legacy aliases for the mainnet. If you specify --chain homestead, --chain frontier or --chain byzantium, this will need to be changed to one of: --chain eth, --chain ethereum, --chain foundation or --chain mainnet.

This release includes important changes to how snapshots are produced. The size of the Ethereum account state means that producing a snapshot takes a long while; most nodes today are not able to finish before the relevant state is pruned. Starting with v2.6.5, pruning is paused while a snapshot is underway, hopefully fixing the current dearth of recent snapshots. The downside to this is that memory usage goes up while a snapshot is produced.

The full list of included changes:

[CI] check evmbin build (#11096)

Correct EIP-712 encoding (#11092)

[client]: Fix for incorrectly dropped consensus messages (#11082) (#11086)

Update hardcoded headers (foundation, classic, kovan, xdai, ewc, ...) (#11053)

Add cargo-remote dir to .gitignore (?)

Update light client headers: ropsten 6631425 foundation 8798209 (#11201)

Update list of bootnodes for xDai chain (#11236)

ethcore/res: add mordor testnet configuration (#11200)

[chain specs]: activate Istanbul on mainnet (#11228)

[builtin]: support multiple prices and activations in chain spec (#11039)

[receipt]: add sender & receiver to RichReceipts (#11179)

[ethcore/builtin]: do not panic in blake2pricer on short input (#11180)

Made ecrecover implementation trait public (#11188)

Fix docker centos build (#11226)

Update MIX bootnodes. (#11203)

Insert explicit warning into the panic hook (#11225)

Use provided usd-per-eth value if an endpoint is specified (#11209)

Cleanup stratum a bit (#11161)

Add Constantinople EIPs to the dev (instant_seal) config (#10809) (already backported)

util Host: fix a double Read Lock bug in fn Host::session_readable() (#11175)

ethcore client: fix a double Read Lock bug in fn Client::logs() (#11172)

Type annotation for next_key() matching of json filter options (#11192)

Upgrade jsonrpc to latest (#11206)

[dependencies]: jsonrpc 14.0.1 (#11183)

Upgrade to jsonrpc v14 (#11151)

Switching sccache from local to Redis (#10971)

Snapshot restoration overhaul (#11219)

Add new line after writing block to hex file. (#10984)

Pause pruning while snapshotting (#11178)

Change how RPCs eth_call and eth_estimateGas handle "Pending" (#11127)

Fix block detail updating (#11015)

Make InstantSeal Instant again #11186

Filter out some bad ropsten warp snapshots (#11247)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 961238cf3d0f31df4c5bd1f6aa70e6a2d443bbd3375fd884879de33cc5e27beb | | | x64 | parity | bd9fa27358ad4043175d97b5e3b6e7274e5db11b32df6eff5cc5781621752380 | | | x64 | parity | 62762f424ffcc9ea939f3e09904d64600c4966045a865cfd94f23cf967213a0d | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.6.5 |
Source code(tar.gz)
Source code(zip)
v2.5.10(Nov 13, 2019)
Parity Ethereum v2.5.10-stable is a patch release that adds block numbers for activating the Istanbul hardfork on mainnet, as well as a large number of various bugfixes, QoL changes, some code cleanup/refactoring and other miscellaenous changes.

This release removes legacy aliases for the mainnet. If you specify --chain homestead, --chain frontier or --chain byzantium, this will need to be changed to one of: --chain eth, --chain ethereum, --chain foundation or --chain mainnet.

The full list of included changes:

ropsten #6631425 foundation #8798209 (#11201)

[stable] builtin, istanbul and mordor testnet backports (#11234)

ethcore-builtin (#10850)

[builtin]: support multiple prices and activations in chain spec (#11039)

[chain specs]: activate Istanbul on mainnet (#11228)

ethcore/res: add mordor testnet configuration (#11200)

Update list of bootnodes for xDai chain (#11236)

ethcore: remove test-helper feat from build (#11047)

Secret store: fix Instant::now() related race in net_keep_alive (#11155) (#11159)

[stable]: backport #10691 and #10683 (#11143)

Fix compiler warning (that will become an error) (#10683)

Refactor Clique stepping (#10691)

Add Constantinople eips to the dev (instant_seal) config (#10809)

Add cargo-remote dir to .gitignore (?)

Insert explicit warning into the panic hook (#11225)

Fix docker centos build (#11226)

Update MIX bootnodes. (#11203)

Use provided usd-per-eth value if an endpoint is specified (#11209)

Add new line after writing block to hex file. (#10984)

Type annotation for next_key() matching of json filter options (#11192) (but no FilterOption in 2.5 so…)

Upgrade jsonrpc to latest (#11206)

[CI] check evmbin build (#11096)

Correct EIP-712 encoding (#11092)

[client]: Fix for incorrectly dropped consensus messages (#11086)

Fix block detail updating (#11015)

Switching sccache from local to Redis (#10971)

Made ecrecover implementation trait public (#11188)

[dependencies]: jsonrpc 14.0.1 (#11183)

[receipt]: add sender & receiver to RichReceipts (#11179)

[ethcore/builtin]: do not panic in blake2pricer on short input (#11180)

util Host: fix a double Read Lock bug in fn Host::session_readable() (#11175)

ethcore client: fix a double Read Lock bug in fn Client::logs() (#11172)

Change how RPCs eth_call and eth_estimateGas handle "Pending" (#11127)

Cleanup stratum a bit (#11161)

Upgrade to jsonrpc v14 (#11151)

SecretStore: expose restore_key_public in HTTP API (#10241)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 5f3b4ffaaa0bc88952d556064f245d7ed7944183a139a71c095bee63d4f393b7 | | | x64 | parity | 54bd6393263b7437a21059927a47ef9f7cc0748f1d8d11439268d7e348eaf5a9 | | | x64 | parity | 9a746fa8a480e8c8828f7b9f54b74e102db5624f121a3b4f7329a380382cf032 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.10 |
Source code(tar.gz)
Source code(zip)
v2.6.4(Sep 26, 2019)
Parity Ethereum v2.6.4-stable is a patch release that adds the block numbers for activating the Istanbul hardfork on test networks: Ropsten, Görli, Rinkeby and Kovan.

A full list of included changes:

ethcore/res: activate Istanbul on Ropsten, Görli, Rinkeby, Kovan (#11068)

cleanup json crate (#11027)

[json-spec] make blake2 pricing spec more readable (#11034)

Update JSON tests to d4f86ecf4aa7c (#11054)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 768cfff4b3e445c22699237bf4ef0758b5c54f80d68c6158292fb249565bf5b6 | | | x64 | parity | aad27cd7b02391259477ed2b4841de7a9d496e61d09868c4b7379bd844d106f7 | | | x64 | parity | 1b5fb1a33eba1f4549d7b33a1e8eba049c98fd1f45b901573ed72623cede05ea | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.6.4 |
Source code(tar.gz)
Source code(zip)
v2.5.9(Sep 26, 2019)
Parity Ethereum v2.5.9-stable is a patch release that adds the block numbers for activating the Istanbul hardfork on test networks: Ropsten, Görli, Rinkeby and Kovan.

The full list of included changes:

ethcore/res: activate Istanbul on Ropsten, Görli, Rinkeby, Kovan (#11068)

[json-spec] make blake2 pricing spec more readable (#11034)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 95ecb2738bc71e82b14e841b77a4a8670a053ca6c8726bdb9b183bc18e364e43 | | | x64 | parity | 545b57d452137225e259b196ba6a34e05cb0fa28585ca10c91ac27efc8157405 | | | x64 | parity | 3089290d2ec46f324e6331b9cee0adc91a039bd6173bb2b3a0d70291281cb7f7 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.9 |
Source code(tar.gz)
Source code(zip)
v2.6.3(Sep 16, 2019)
Parity Ethereum v2.6.3-beta is a patch release that improves security, stability and performance.

The most noteworthy improvement in this release is incorporating all the EIPs required for the Istanbul hard fork.

This release also fixes certain security and performance issues, one of which was suspected to be consensus-threatening but turned out to be benign. Thanks to Martin Holst Swende and Felix Lange from the Ethereum Foundation for bringing the suspicious issue to our attention.

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 26e4b8d77dc93a43d5f0ffb593f4b6e7532b80199b4404fb8b4835f7a75dc5b7 | | | x64 | parity | 7cea9bfbbc7a9b9fb6649c4598288fb5bd3e20475817bd616f7bae3e490b6f34 | | | x64 | parity | 39ff22d3bb45100d21f517e2595edce51029f2e1586abfe03a5ab558359537bd | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.6.3 |

A full list of changes can be found in the CHANGELOG.md
Source code(tar.gz)
Source code(zip)
v2.5.8(Sep 16, 2019)
Parity Ethereum v2.5.8-stable is a patch release that improves security, stability and performance.

The most noteworthy improvement in this release is incorporating all the EIPs required for the Istanbul hard fork.

This release also fixes certain security and performance issues, one of which was suspected to be consensus-threatening but turned out to be benign. Thanks to Martin Holst Swende and Felix Lange from the Ethereum Foundation for bringing the suspicious issue to our attention.

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 3994f711841d0cce6dbccc1fb4f66c46bdb9131e2ea471b9dd0d655e1fa6c3fa | | | x64 | parity | 249d8740568a1de091e63e9676c00a2e2a594b5421ec347e5136ad71960b41d0 | | | x64 | parity | 2d8f0e0b785124ca3c569502280d615d28dfaf47e313d98d2376dd89a49eef7b | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.8 |

A full list of changes can be found in the CHANGELOG.md
Source code(tar.gz)
Source code(zip)
v2.6.2(Aug 29, 2019)

Parity Ethereum v2.6.2-beta is a bugfix release that fixes a potential DoS attack in the trace_call RPC method. This is a critical upgrade for anyone running Parity nodes with RPC exposed to the public internet (and highly recommended for anyone else). For details see this blog post.

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 7dc6e81ee7237bdb23c3eff36e19c1c3aaa2077c1aa743bacfa94165836a0f34 | | | x64 | parity | a45da1e83248dc5f6394d426abe6eb57757b77d17eece86bc6b3898ca22f0988 | | | x64 | parity | 593c2f622fbb04a4baccd3388b66d2d1b1a5bd207201335ab5b26a3ed95d182f | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.6.2 |
Source code(tar.gz)
Source code(zip)
v2.5.7(Aug 29, 2019)

Parity Ethereum v2.5.7-stable is a bugfix release that fixes a potential DoS attack in the trace_call RPC method. This is a critical upgrade for anyone running Parity nodes with RPC exposed to the public internet (and highly recommended for anyone else). For details see this blog post.

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 970b7e7b6a2a4b782a83e87ef48e28a3a053baa66a6505cc8cca4e414fcf2402 | | | x64 | parity | 2ca943b20350285c2bac1e8ce4747e42f5ac45b9ed5bacf58cb4b0273b70e501 | | | x64 | parity | 733943599b64b38f9fb580394ce7486d0d028bf3241a37e1ca59fa14c4683c79 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.7 |
Source code(tar.gz)
Source code(zip)
v2.6.1(Aug 15, 2019)
Parity-Ethereum 2.6.1-beta is a patch release that improves stability.

This release includes:

Allow specifying hostnames for node URLs

Fix a bug where archive nodes were losing peers

Add support for Energy Web Foundations new chains 'Volta' and 'EWC', and remove their deprecated 'Tobalaba' chain.

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | dbad6dc6b0b0a90a6fdb9110c9feb796919fcf2c8fff2704d8b2f4cdc1cec927 | | | x64 | parity | 476817293dedabc05f3eb7f8d0e172d9fb0fe82087c120ac1f2e547e7abf2b8e | | | x64 | parity | 2178a9ee9656dd7669ba7528bec7ec0d54c93c54c5b693a39efa83fefa496348 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.6.1 |

The full list of included changes:

Add support for Energy Web Foundation's new chains (#10957)

Kaspersky AV whitelisting (#10919)

Avast whitelist script (#10900)

Docker images renaming (#10863)

Remove excessive warning (#10831)

Allow --nat extip:your.host.here.org (#10830)

When updating the client or when called from RPC, sleep should mean sleep (#10814)

added new ropsten-bootnode and removed old one (#10794)

ethkey no longer uses byteorder (#10786)

docs: Update Readme with TOC, Contributor Guideline. Update Cargo package descriptions (#10652)

Source code(tar.gz)
Source code(zip)
v2.5.6(Aug 13, 2019)
Parity-Ethereum v2.5.6-stable is a bugfix release that improves stability.

The release includes:

Allow specifying hostnames for node URLs

Fix a bug where archive nodes were losing peers

Add support for Energy Web Foundations new chains 'Volta' and 'EWC', and remove their deprecated 'Tobalaba' chain.

The full list of included changes:

Add support for Energy Web Foundation's new chains (#10957)

Kaspersky AV whitelisting (#10919)

Avast whitelist script (#10900)

Docker images renaming (#10863)

Remove excessive warning (#10831)

Allow --nat extip:your.host.here.org (#10830)

When updating the client or when called from RPC, sleep should mean sleep (#10814)

added new ropsten-bootnode and removed old one (#10794)

ethkey no longer uses byteorder (#10786)

Do not drop the peer with None difficulty (#10772)

docs: Update Readme with TOC, Contributor Guideline. Update Cargo package descriptions (#10652)

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 5a8624c17af25669ef42cfd76af084318f174407007c76ca0a03dc49154f0391 | | | x64 | parity | 81352b111872304466868c9193a881fccc76864dbf571b18e7bebf4d8cdbaadc | | | x64 | parity | af32e320226c1559cad4e47c1c0edaf7b50ae55822a99fd17f3001ceb08c3e97 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.6 |
Source code(tar.gz)
Source code(zip)
v2.6.0(Jul 8, 2019)
Parity-Ethereum 2.6.0-beta is a minor release that stabilizes the 2.6 branch by marking it as a beta release.

This release includes:

Major refactoring of the codebase

Many bugfixes

Significant improvements to logging, error and warning message clarity.

SecretStore: remove support of old database formats (#10757)

This is a potentially breaking change if you have not upgraded for quite some time.

As of today, Parity-Ethereum 2.4 reaches end of life, and everyone is encouraged to upgrade.

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 7ffb0d0e014724fcb3167801cf50a9176b9fc54ceba7dce4c3ea4f8a3a62520f | | | x64 | parity | 30b48765fa3d811e17552cc90e400690b7c88907f9b5f172b285b322100e452c | | | x64 | parity | 1b50cabc8ce54983d1b10be4c4f5887ff4ecfe63177e6c49cde819a563fb9d96 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.6.0 |

A full list of changes can be found in the CHANGELOG.md
Source code(tar.gz)
Source code(zip)
v2.5.5(Jul 8, 2019)

Parity-Ethereum is a minor release that improves performance and stability. This release stabilises the 2.5 branch.

As of today, Parity-Ethereum 2.4 reaches end of life and everyone is encouraged to upgrade.

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 16e2bd319f7dd6efa3daac15e2c8e6b3ef811873f6f80db080d28dc80ec9986d | | | x64 | parity | 9c1934728da62b0246af5cc189fe760b77e60b6811da0dbb536d1958d92153ad | | | x64 | parity | 1deb0d9dcf3eef2fee32867a200ddb65c9343071b6e4e39660d8837184b164e3 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.5 |
Source code(tar.gz)
Source code(zip)
v2.5.4(Jul 1, 2019)

Parity Ethereum v2.5.4-stable is a security update that addresses servo/rust-smallvec#148

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | f5fabe8e315e751fea90902073b294c10a73648060e3477ec97d1647afa315ab | | | x64 | parity | 9574fc3a61c883816bcaeea252f1e979c8aa2d4da11b1152698d745dbc3b3047 | | | x64 | parity | 504946e2cc8fe954343cfdb6b856316308743ecec89b749bcb705badf86bd085 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.4 |
Source code(tar.gz)
Source code(zip)
v2.4.9(Jul 1, 2019)

Parity Ethereum v2.4.9-stable is a security update which addresses servo/rust-smallvec#148

| System | Architecture | Binary | Sha256 Checksum | |:---:|:---:|:---:|:---| | | x64 | parity.exe | 711f1deef0db9c44ca3f888a902d1d86b09a1b00c110c3ea8825e53506ab0e1a | | | x64 | parity | c9caea16de8293a242f67730a4c0e98b6ced89fc2f3bf6987e2a429abc7ce328 | | | x64 | parity | 0d60bc6aea55619268c597049ebae404e4da6263f5eb465b53b56ca73bf46c00 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.4.9 |
Source code(tar.gz)
Source code(zip)
v2.5.3(Jun 26, 2019)
Parity-Ethereum 2.5.3-beta is a bugfix release that improves performance and stability.

EthereumClassic: activate the Atlantis Hardfork

Clique: fix time overflow

State tests: treat empty accounts the same as non-existant accounts (EIP 1052)

Networking: support discovery-only peers (geth bootnodes)

Snapshotting: fix unclean shutdown while snappshotting is under way

| System | Architecture | Binary | SHA256 Checksum | |:---:|:---:|:---|:---| | | x64 | parity.exe | 5369e45d6ba1ef8916a51119beb6dc8c34eb44433040307d92b2f41c4420d017 | | | x64 | parity | 136284a143ec6665f7c9ebb7d81a913120e7ec1177b0c1b29d1d2c458df42e17 | | | x64 | parity | 3037fe9dea18bfd103e7587814930fd9a82cf4f852890fd8402768d124e7ba51 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.3 |
Source code(tar.gz)
Source code(zip)
v2.4.8(Jun 26, 2019)
Parity-Ethereum 2.4.8-stable is a bugfix release that improves performance and stability.

Blockchain: fix reset chain

State tests: treat empty accounts the same as non-existant accounts (EIP 1052)

Aura: fix Timestamp Overflow

Networking: support discovery-only peers (geth bootnodes)

Snapshotting: fix unclean shutdown while snappshotting is under way

| System | Architecture | Binary | SHA256 Checksum | |:---:|:---:|:---|:---| | | x64 | parity.exe | 58fa07915e5014e6f1375884dbc533eb34a19edc42afb6e8d5f9b96e6830a802 | | | x64 | parity | 69f1ccf4231d66949e57e5713e2adf405d29a3b42561a6c1251846f3fced03d6 | | | x64 | parity | 03cfeff55d3ae0a1c12c0df0a5643b12fe5c5cc7b9a0989d94a1bb764dad5e9d | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.4.8 |
Source code(tar.gz)
Source code(zip)
v2.5.2(Jun 12, 2019)

Parity-Ethereum 2.5.2-beta is a bugfix release that improves performance and stability.

Among others, it enables the Atlantis hardfork on Morden and Kotti Classic networks.

| System | Architecture | Binary | SHA256 Checksum | |:---:|:---:|:---|:---| | | x64 | parity.exe | 298a842e834f215582f232d8a1e9a0c8cd1251613c55daddb57c2f83ddc2d187 | | | x64 | parity | a60aa8bee22af443289225f51f03991a3e659501cc1f0569128a1e041a231454 | | | x64 | parity | c43b1b6e208cc505e75ec7e38e4b13064f9a5237e9deb4204d9ad158659b5bb5 | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.2 |
Source code(tar.gz)
Source code(zip)
v2.4.7(Jun 12, 2019)

Parity-Ethereum 2.4.7-stable is a bugfix release that improves performance and stability.

Among others, it enables the Atlantis hardfork on Morden and Kotti Classic networks.

| System | Architecture | Binary | SHA256 Checksum | |:---:|:---:|:---|:---| | | x64 | parity.exe | 500ea9a75b627f7b3708cc267f966249d0b931c2a02cb20dfce531421387b4e3 | | | x64 | parity | 1e9ef307105cb82efd1870ac2b5622162e72c72e26a45e52769246feb38c488a | | | x64 | parity | 8c9211a202750d9d655c6ab819a86774e0fb4086f2c6ad2d14d2df0e45898f8a | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.4.7 |
Source code(tar.gz)
Source code(zip)
v2.5.1(May 14, 2019)

Parity-Ethereum 2.5.1-beta is a bugfix release that improves performance and stability.

Among others, it enables the Petersburg hardfork on Rinkeby and POA-Core Network, as well as the Kovan Network community hardfork.

| System | Architecture | Binary | SHA256 Checksum | |:---:|:---:|:---|:---| | | x64 | parity.exe | 34fd3baf53dc9deebf50cb362ab22ae120061099d90bdebba8bed867141b294f | | | x64 | parity | 17c7e7622585e0561bd810e9fb5dc2348909033545b7c1008476ef45817f059e | | | x64 | parity | 0def1ae3444486e035d2a05d11abc18f61e4dfa1da6f2aab4dcb2046db846e8a | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.1 |
Source code(tar.gz)
Source code(zip)
v2.4.6(May 14, 2019)

Parity-Ethereum 2.4.6-stable is a bugfix release that improves performance and stability.

Among others, it enables the Petersburg hardfork on Rinkeby and POA-Core Network, as well as the Kovan Network community hardfork.

| System | Architecture | Binary | SHA256 Checksum | |:---:|:---:|:---|:---| | | x64 | parity.exe | 27a81a77d722341bdbc8cb4117edaf1f1a934930a174d4857a7e9bd2e6ec7a1d | | | x64 | parity | ddb8259333e7ebb87b483305449987d6d6d03689d244ae04e1b853eceeb50f49 | | | x64 | parity | e0a249d586aad506ba2ea886416c3b247a841c615c8dcc51e1b18b343f9439cf | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.4.6 |
Source code(tar.gz)
Source code(zip)
v2.5.0(Apr 9, 2019)
Parity-Ethereum 2.5.0-beta is a minor release that improves performance and stabilizes the 2.5 branch by marking it as beta release.

This release adds support for the Clique consensus engine (#9981)

This enables Parity-Ethereum users to use the Görli, the Kotti Classic, and the legacy Rinkeby testnet. To get started try parity --chain goerli; note that light client support is currently not yet fully functional.

This release removes the dead chain configs for Easthub and Ethereum Social (#10531)

As of today, Parity-Ethereum 2.3 reaches end of life and everyone is encouraged to upgrade.

| System | Architecture | Binary | SHA256 Checksum | |:---:|:---:|:---|:---| | | x64 | parity.exe | 67570f7118954ffc832058f2283ec8edc0755a85194fcd4d2876c601001d85c6 | | | x64 | parity | 86c0db1952bafeafa832cf84010928902bfbff90e29c0f301cf5c6dd76630531 | | | x64 | parity | 8f2d65f135b8515c51ed0667759a13368bb61af8be605e20ec3749d200e0051a | | | | | | | System | Option | - | Resource | | | Homebrew | - | github.com/paritytech/homebrew-paritytech | | | Snapcraft | - | snapcraft.io/parity | | | Docker | - | hub.docker.com/r/parity/parity | | | All binaries | - | vanity-service.parity.io/parity-binaries?version=v2.5.0 |

The full list of included changes can be found in the CHANGELOG.md
Source code(tar.gz)
Source code(zip)

The fast, light, and robust client for Ethereum-like networks.

Related tags

Overview

The Fastest and most Advanced Ethereum Client.

Table of Contents

1. Description

2. Technical Overview

3. Building

3.1 Build Dependencies

3.2 Build from Source Code

3.3 Simple One-Line Installer for Mac and Linux

3.4 Starting Parity Ethereum

Manually

Using systemd service file

4. Testing

5. Documentation

Viewing documentation for Parity Ethereum packages

Contributing to documentation for Parity Ethereum packages

6. Toolchain

7. Community

Join the chat!

8. Contributing

Contributor Code of Conduct

9. License

Comments

Please help ...

Releases(v3.0.1)

v3.0.1(Jun 1, 2020)

v3.0.0(May 11, 2020)

v2.7.2(Feb 6, 2020)

v2.6.8(Dec 31, 2019)

v2.5.13(Dec 31, 2019)

v2.6.7(Dec 16, 2019)

v2.5.12(Dec 16, 2019)

v2.6.6(Dec 5, 2019)

v2.5.11(Dec 5, 2019)

v2.6.5(Nov 13, 2019)

v2.5.10(Nov 13, 2019)

v2.6.4(Sep 26, 2019)

v2.5.9(Sep 26, 2019)

v2.6.3(Sep 16, 2019)

v2.5.8(Sep 16, 2019)

v2.6.2(Aug 29, 2019)

v2.5.7(Aug 29, 2019)

v2.6.1(Aug 15, 2019)

v2.5.6(Aug 13, 2019)

v2.6.0(Jul 8, 2019)

v2.5.5(Jul 8, 2019)

v2.5.4(Jul 1, 2019)

v2.4.9(Jul 1, 2019)

v2.5.3(Jun 26, 2019)

v2.4.8(Jun 26, 2019)

v2.5.2(Jun 12, 2019)

v2.4.7(Jun 12, 2019)

v2.5.1(May 14, 2019)

v2.4.6(May 14, 2019)

v2.5.0(Apr 9, 2019)

Owner

OpenEthereum

Ethereum (and Ethereum like) indexer using P2P message to fetch blocks and transactions

A crate for working with Ethereum beacon chain light client protocol messages. `no_std` friendly!

Parity-Bridge — Bridge between any two ethereum-based networks

Substreams development kit for Ethereum chains, contains Firehose Block model and helpers as well as utilities for Ethereum ABI encoding/decoding.

A library to help you sew up your Ethereum project with Rust and just like develop in a common backend

Zero Knowledge Light Client Implementation by Zpoken team.

Rust client to Opensea's APIs and Ethereum smart contracts

The Fastest and most Advanced Ethereum Client

Rust client to Seaport's APIs and Ethereum smart contracts(WIP)

Rust Ethereum 2.0 Client

Next-generation implementation of Ethereum protocol ("client") written in Rust, based on Erigon architecture.

Ethereum JSON-RPC multi-transport client. Rust implementation of web3 library

An experimental fork of a16z's Helios Ethereum client which can run its network traffic over the Nym mixnet

A simple and secure rust command-line tool to protect your text by encrypting and decrypting it using the robust AES-256 algorithm.

Foundry is a blazing fast, portable and modular toolkit for Ethereum application development written in Rust.

Darwinia networks' tracing runtime override collections

Tiny CLI for submitting large calldata transactions to EVM networks to stress test the networking layer. Main motivation: EIP4844blobs.

Tiny CLI for submitting large calldata transactions to EVM networks to stress test the networking layer

Rapid, reliable and robust template management

Using `systemd` service file