| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Start blockproposer only after fast sync is completed (received
ChainHead event), so watchcat is not falsely triggered.
|
| |
|
| |
|
|
|
| |
also modify some debug log
|
| |
|
|
|
|
|
|
| |
In theory BA should tolerant inconsistant start time between every node.
Since the vote cache is limited, we can not keep all the votes and pass
them around all nodes. To fix this, we align the next recovery dmoment
so nodes start at the same time.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* dex: implement recovery mechanism
The DEXON recovery protocol allows us to use the Ethereum blockchain as a
fallback consensus chain to coordinate recovery.
* fix
|
| |
|
|
|
|
|
|
| |
* Add Yilan network
* Fixup: remove dummy log
|
|
* dex, internal: block proposer syncing (first iteration)
* core: find block from db if not in memory
This fix handles stopping proposing and then restarting
* core: no need to reorg when reset
Dexon will not fork. This commit also fix when a block confirm but
its parent is not in db yet, during restarting proposing.
* dex: always accept NewBlockMsg, NewBlockHashesMsg
We need to accept NewBlockMsg, NewBlockHashesMsg to sync current block with
other peers in block proposer mode when syncing lattice data. It's a waste
when the node is synced and start proposing.
Todo: control msg processing on/off more granular, accept NewBlockMsg,
NewBlockHashesMsg when syncing, but stop when synced.
|