diff options
author | Sonic <sonic@dexon.org> | 2018-12-05 15:17:38 +0800 |
---|---|---|
committer | Wei-Ning Huang <w@byzantine-lab.io> | 2019-06-12 17:27:19 +0800 |
commit | d4183037825fe7a86e2a6653adb5e97ee0d6bbf8 (patch) | |
tree | 51756911df4b00983d1d9678150d1c0c307b4104 /dex/protocol.go | |
parent | 5a75b7ea1e3bd34e2f2de91131d759a41e16cafc (diff) | |
download | go-tangerine-d4183037825fe7a86e2a6653adb5e97ee0d6bbf8.tar go-tangerine-d4183037825fe7a86e2a6653adb5e97ee0d6bbf8.tar.gz go-tangerine-d4183037825fe7a86e2a6653adb5e97ee0d6bbf8.tar.bz2 go-tangerine-d4183037825fe7a86e2a6653adb5e97ee0d6bbf8.tar.lz go-tangerine-d4183037825fe7a86e2a6653adb5e97ee0d6bbf8.tar.xz go-tangerine-d4183037825fe7a86e2a6653adb5e97ee0d6bbf8.tar.zst go-tangerine-d4183037825fe7a86e2a6653adb5e97ee0d6bbf8.zip |
core, dex: polish sync (#75)
- Broadcasting blocks at chain head event is not correct when the full
node is not running in block proposer mode. Introduce NewFinalizedBlockEvent,
this event is post by the full node which runs in block proposer mode when a
block is witnessed and resulting in some blocks are considered finalized.
- Non block proposer node will still broadcast blocks
at the following moment (same as ethereum):
1. a sync with a peer is terminated successfully
2. a block passes the fetcher's header check during inserting blocks
3. a block is successfully inserted by fetcher
- Don't trigger a sync when we are not behind other peers more than
acceptable distance. Fetcher is able to cover this.
Diffstat (limited to 'dex/protocol.go')
-rw-r--r-- | dex/protocol.go | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/dex/protocol.go b/dex/protocol.go index 49bd0cc20..b6d672b7f 100644 --- a/dex/protocol.go +++ b/dex/protocol.go @@ -153,6 +153,11 @@ type governance interface { DKGSet(uint64) (map[string]struct{}, error) } +type dexconApp interface { + SubscribeNewFinalizedBlockEvent( + chan<- core.NewFinalizedBlockEvent) event.Subscription +} + type p2pServer interface { Self() *enode.Node |