go-tangerine - Tangerine full node (https://github.com/tangerine-network/go-tangerine)

	Commit message (Collapse)	Author	Age	Files	Lines
*	dex: implement recovery mechanism (#258)	Wei-Ning Huang	2019-04-09	1	-4/+26
\| \| \| \| \| \| \| \| \|	* dex: implement recovery mechanism The DEXON recovery protocol allows us to use the Ethereum blockchain as a fallback consensus chain to coordinate recovery. * fix
*	dex: rename IsLatticeSyncing to IsCoreSyncing (#238)	Wei-Ning Huang	2019-04-09	1	-1/+1
\|
*	params: add Yilan network (#207)	Mission Liao	2019-04-09	1	-1/+0
\| \| \| \| \| \|	* Add Yilan network * Fixup: remove dummy log
*	core, dex, internal: block proposer syncing (first iteration) (#96)	Sonic	2019-04-09	1	-0/+201
	* 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.