go-tangerine/core/vm, branch w-ci

Revert "core: consider reset round when getting config state"

2019-09-17T08:57:31+00:00

This reverts commit 01cb8de88b0697879cc366e3ee962c9523dfcc14.

core: vm: fix DKG nacking threshold

2019-09-17T08:57:31+00:00

DKG nacking threshold should only be t + 1 instead of 2t + 1

core: vm: allow unstake empty staked node

2019-09-17T08:57:31+00:00

core: vm: reject transaction for some gov methods if value > 0

2019-09-17T08:57:31+00:00

core: add p2p whitelist for consortium

2019-09-17T08:57:31+00:00

core: vm: use correct notary set size when verifying CRS

2019-09-17T08:57:31+00:00

params: update testnet config and dMoment

2019-09-17T08:57:31+00:00

core: consider reset round when getting config state

2019-09-17T08:57:31+00:00

Previous config snapshot is determined as follows, for round n: Return the snapshot state of round (n - ConfigRoundShift) However this may cause the system to stuck at a particular round if the DKG for the next round continues to fail (maybe due to node failure). To fix this, instead of using the simple logic above, we consider the reset rounds as a normal round, and use the snapshot of the reset rounds as config. Thus we could gradually push out the broken nodes from nodeset. The snapshot is now determined as follows, for round n: If resetCount < ConfigRoundShift Return the snapshot state of round (n - ConfigRoundShift) Else Reutrn the stateshot state of (n + resetCount - ConfigRoundShift)

core: add GovUtil to unify governance state related access

2019-09-17T08:57:31+00:00

Add GovUtil so we could use the same logic in everywhere that requires access to governance state, such as configuration and CRS.

import: switch consensus core to gitlab.com/tangerine-network/tangerine-consensus

2019-09-17T08:57:30+00:00