* Ask about used network in issue template

* Update Riot-References

* Uppercase Parity

* Byzantium Update for Expanse

Here the changes go. Hope I didnt miss anything.

* expip2 changes - update duration limit

* Fix missing EXPIP-2 fields

* Format numbers as hex

* Fix compilation errors

* Group expanse chain spec fields together

* Set metropolisDifficultyIncrementDivisor for Expanse

* Revert #7437

* Add Expanse block 900_000 hash checkpoint

* Cleanup certifications

* Add key for accounts

* Upgrade markdown-loader & marked

* Align UglifyJS (wallet/shell)

* Add ethereumjs-util Babel compilation

* Remove status from tabs

* Update js-shared, add dapp-status

* Remove unused layout

* Update to use pending from Redux

* Update @parity/shared

Remove expanse chain

Strict config parsing

* kvdb-rocksdb: update to RocksDB 5.8.8

* kvdb-rocksdb: tune RocksDB options

* Switch to level-style compaction
* Increase default block size (16K), and use bigger blocks for HDDs (64K)
* Increase default file size base (64MB SSDs, 256MB HDDs)
* Create a single block cache shared across all column families
* Tune compaction settings using RocksDB helper functions, taking into account
  memory budget spread across all columns
* Configure backgrounds jobs based on the number of CPUs
* Set some default recommended settings

* ethcore: remove unused config blockchain.db_cache_size

* parity: increase default value for db_cache_size

* kvdb-rocksdb: enable compression on all levels

* kvdb-rocksdb: set global db_write_bufer_size

* kvdb-rocksdb: reduce db_write_bufer_size to force earlier flushing

* kvdb-rocksdb: use master branch for rust-rocksdb dependency

Fix tracing failed calls.

Problem: sending any Whisper message fails

Wait for future blocks in AuRa

Fix final feature.

Use RwLock for state DB

Amaury Martiny authored Jan 02, 2018 and Jaco Greeff committed Jan 02, 2018

* Update packages

* Update pictures for v1

The error is "PoW too low to compete with other messages"

This has been previously reported in #7144

Solution: prevent the move semantics

The source of the error is in PoolHandle.relay
implementation for NetPoolHandle.

Because of the move semantics, `res` variable is in fact
copied (as it implements Copy) into the closure and for
that reason, the returned result is always `false.

* Add Changelog for 1.7.11

* Add Changelog for 1.8.5

* Markdownify issue links

Added checking tx-type using transactions permission contract for miners