- Jan 02, 2018
-
-
Tomasz Drwięga authored
-
- Dec 28, 2017
-
-
Tomasz Drwięga authored
* Updating mainnet bootnodes. * Add additional parity-beta bootnodes. * Restore old parity bootnodes and update foudation bootnodes
-
- 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
-
Nikolay Volf authored
* call augmented, wasm-tests updated * fix all call tests * fix comments
-
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
-
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
-
5chdn authored
-
5chdn authored
-
Konstantin authored
* new warp enodes * added one more warp enode; replaced spaces with tabs
-
- Dec 12, 2017
-
-
Tomasz Drwięga authored
-
- 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
- Dec 05, 2017
-
-
Takehiro Miyao authored
-
* Enable delayed maximum_uncle_count activation. * Fix tests. * Defer kovan HF.
-
- Dec 02, 2017
-
-
Arkadiy Paronyan authored
* Removed ethcore-util dependency * Removed snappy
-
- Dec 01, 2017
-
-
NikVolf authored
-
Takehiro Miyao authored
-
- Nov 26, 2017
-
-
Sergey Pepyakin authored
* Remove blockhash error * Update tests.
-
- Nov 25, 2017
-
-
NikVolf authored
-
- Nov 24, 2017
-
-
Wei Tang authored
It is era 49, and should correspond to ECIP1017/ECIP1039's era 50.
-
Wei Tang authored
-
Svyatoslav Nikolsky authored
-
- Nov 22, 2017
-
-
Svyatoslav Nikolsky authored
-
- Nov 21, 2017
-
-
Sergey Pepyakin authored
-
Sergey Pepyakin authored
-
Sergey Pepyakin authored
-
Sergey Pepyakin authored
-
- Nov 20, 2017
-
-
Svyatoslav Nikolsky authored
-