- Jan 17, 2018
-
-
Marek Kotewicz authored
-
- Jan 14, 2018
-
-
Marek Kotewicz authored
* ethereum-types refactor in progress * ethereum-types refactor in progress * ethereum-types refactor in progress * ethereum-types refactor in progress * ethereum-types refactor finished * cleanup bloom mess * simplify usage of Bloom in few places * removed obsolete util/src/lib.rs * removed commented out code * ethereum-types 0.1.4 * updated ethereum-types and tiny-keccak
-
- Jan 11, 2018
-
-
* Move miner away from ethcore. * Fix ethcore to use miner/transaction. * Fix tests and warnings. * fixed incorrect merge of the test in the documentation
-
- Jan 10, 2018
-
-
* ethereum-types refactor in progress * ethereum-types refactor in progress * ethereum-types refactor in progress * ethereum-types refactor in progress * ethereum-types refactor finished * removed obsolete util/src/lib.rs * removed commented out code
-
tzapu authored
* intial add trace_replayBlockTransactions * cleanup timing calls add execution proof * WIP implementing changes * fix for trace_replayBlockTransactions rpc call * cleanup comments * cleanup, proof, can't workout lifetime issues yet * Fix lifetimes issue. * naive rpc test * updated docs
-
- Jan 09, 2018
-
-
- Jan 08, 2018
-
-
* Advance AuRa step as far as we can. * Wait for future blocks.
-
- Jan 05, 2018
-
-
Afri Schoedon authored
* 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
-
- Jan 03, 2018
-
-
5chdn authored
-
André Silva authored
* 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
-
- Jan 02, 2018
-
-
Tomasz Drwięga authored
-
- Dec 29, 2017
-
-
Tomasz Drwięga authored
-
- Dec 26, 2017
-
-
Nicolas Ochem authored
* created the dir crate in util * moved code from ethstore/src/dir/paths.rs to dir crate * rename dir module in ethstore to accounts_dir to distinguish it from the dir crate * changes after @tomusdrw on #6952
-
- Dec 22, 2017
-
-
Vlad Lupashevskyi authored
-
Vlad Lupashevskyi authored
-
Vlad Lupashevskyi authored
-
Vlad Lupashevskyi authored
-
Marek Kotewicz authored
* parity-version module split from util removed unused util deps and features trigger buildbot again only kvdb links rocksdb snappy linker issues * rm snappy * fixed old version imports
-
-
- Dec 21, 2017
-
-
Vlad Lupashevskyi authored
-
Tomasz Drwięga authored
-
Tomasz Drwięga authored
-
Yurii Rashkovskii authored
Firstly, `Step.duration_remaining` casts it to u32, unnecesarily limiting it to 2^32. While theoretically this is "good enough" (at 3 seconds steps it provides room for a little over 400 years), it is still a lossy way to calculate the remaining time until the next step. Secondly, step duration might be zero, triggering division by zero in `Step.calibrate` Solution: rework the code around the fact that duration is typically in single digits and never grows, hence, it can be represented by a much narrower range (u16) and this highlights the fact that multiplying u64 by u16 will only result in an overflow in even further future, at which point we should panic informatively (if anybody's still around) Similarly, panic when it is detected that incrementing the step counter wrapped around on the overflow of usize. As for the division by zero, prevent it by making zero an invalid value for step duration. This will make AuRa log the constraint mismatch and panic (after all, what purpose would zero step duration serve? it makes no sense within the definition of the protocol, as finality can only be achieved as per the specification if messages are received within the step duration, which would violate the speed of light and other physical laws in this case).
-
NikVolf authored
-
Tomasz Drwięga authored
-
- Dec 15, 2017
-
-
asynchronous rob authored
* detect different node, same-key signing in aura * reduce scope of warning
-
- Dec 08, 2017
-
-
* reduce max block timestamp drift to 15 seconds * add test for block timestamp validation within allowed drift
-
- Dec 07, 2017
-
-
asynchronous rob authored
* Fix Aura difficulty race * fix test key * extract out score calculation * fix build
-
- Dec 06, 2017
-
-
Ellaismer authored
-
- Dec 05, 2017
-
-
Takehiro Miyao authored
-
* Enable delayed maximum_uncle_count activation. * Fix tests. * Defer kovan HF.
-
- Dec 01, 2017
-
-
Takehiro Miyao authored
-
- Nov 24, 2017
- Nov 16, 2017
- Nov 10, 2017
-
-
asynchronous rob authored
-
- Nov 09, 2017
-
-
keorn authored
-
- Nov 07, 2017
-
-
Arkadiy Paronyan authored
-
- Nov 03, 2017
-
-
* Allow to include all queue transactions in pending block. * Fix tests.
-