* Merge pull request #7368 from paritytech/td-future-blocks
Wait for future blocks in AuRa
* Advance AuRa step as far as we can and prevent invalid blocks. (#7451)
* Advance AuRa step as far as we can.
* Wait for future blocks.
* Problem: AuRa's unsafeties around step duration (#7282)
Firstly, `Step.duration_remaining` casts it to u32, unnecesarily
limiting it to 2^32. While theoretically this is "good enough" (at 3
seconds steps it provides room for a little over 400 years), it is
still a lossy way to calculate the remaining time until the next step.
Secondly, step duration might be zero, triggering division by zero
in `Step.calibrate`
Solution: rework the code around the fact that duration is
typically in single digits and never grows, hence, it can be represented
by a much narrower range (u16) and this highlights the fact that
multiplying u64 by u16 will only result in an overflow in even further
future, at which point we should panic informatively (if anybody's
still around)
Similarly, panic when it is detected that incrementing the step
counter wrapped around on the overflow of usize.
As for the division by zero, prevent it by making zero an invalid
value for step duration. This will make AuRa log the constraint
mismatch and panic (after all, what purpose would zero step duration
serve? it makes no sense within the definition of the protocol,
as finality can only be achieved as per the specification
if messages are received within the step duration, which would violate
the speed of light and other physical laws in this case).
* Fix tests.
* detect different node, same-key signing in aura (#7245)
* detect different node, same-key signing in aura
* reduce scope of warning
* Advance AuRa step as far as we can.
* fixed panic when io is not available for export block, closes#7486 (#7495)
* Update Parity Mainnet Bootnodes
* Replace the Azure HDD bootnodes with the new ones :)
* Bump version.
* Reduce max block timestamp drift to 15 seconds (#7240)
* reduce max block timestamp drift to 15 seconds
* add test for block timestamp validation within allowed drift
* Update kovan HF block number.
* Check vouch status on appId in addition to contentHash (#6719)
* Check vouch status on appId in addition to contentHash
* Simplify var expansion
* Merge #6725
* Add updated MethodDecoding from master
* [ci skip] js-precompiled 20171011-183908
* Fix estimate gas if from is not provided. (#6714)
* Display vouched overlay on dapps (#6710)
* Remove .only
* Add vouch overlays to dapps
* Cleanup address
* Only run where we have a contentHash
* GitLab kickstart
* Fix wallet view (#6597)
* Add safe fail for empty logs
* Filter transactions
* Add more logging
* Fix Wallet Creation and wallet tx list
* Remove logs
* Prevent selecting twice same wallet owner
* Fix tests
* Remove unused props
* Remove unused props
* Disallow pasting recovery phrases on first run (#6602)
* Fix disallowing paste of recovery phrase on first run, ref #6581
* Allow the leader of CATS pasting recovery phrases.
* Updated systemd files for linux (#6592)
Previous version put $BASE directory in root directory.
This version clearly explains how to run as root or as specific user.
Additional configuration:
* send SIGHUP for clean exit,
* restart on fail.
Tested on Ubuntu 16.04.3 LTS with 4.10.0-33-generic x86_64 kernel
* Don't expose port 80 for parity anymore (#6633)
* fix modexp bug: return 0 if base=0 (#6424)
* Running state test using parity-evm (#6355)
* Initial version of state tests.
* Refactor state to support tracing.
* Unify TransactResult.
* Add test.
* Byzantium updates
