dexon-consensus - DEXON consensus algorithm (https://github.com/dexon-foundation/dexon-consensus)

	Commit message (Collapse)	Author	Age	Files	Lines
*	big-bang: single chain (#446)	Mission Liao	2019-02-19	1	-140/+0
\|
*	db: rename blockdb to db (#367)	Mission Liao	2018-12-13	1	-9/+9
\| \| \| \| \| \| \| \| \| \|	* Rename blockdb package to db * Rename 'BlockDB' to 'DB' * Make all methods in db specific for ''block'. * Rename db.BlockDatabase to db.Database * Rename revealer to block-revealer * Rename test.Revealer to test.BlockRevealer
*	core: syncer: add syncer (#346)	haoping-ku	2018-11-29	1	-2/+2
\|
*	Rename repo to dexon-consensus	Wei-Ning Huang	2018-11-02	1	-7/+7
\|
*	test: add test.Stopper to stop by round (#255)	Mission Liao	2018-10-25	1	-2/+56
\|
*	Rename validator* to node* (#120)	Mission Liao	2018-09-20	1	-21/+21
\|
*	core: move blockdb into core package and minor change on governance ↵	Wei-Ning Huang	2018-09-17	1	-1/+1
\| \| \| \| \| \| \|	interface (#110) Since third party apps will possibly implement their only blockdb class, it make sense for the interface to be in core. Also add GetNumShards into the governance interface.
*	test: add test.Scheduler (#58)	Mission Liao	2018-08-15	1	-0/+86
	When simulating execution of core.Consensus by passing packets through golang-channel or real-socket, we need to utilize time.Sleep and time.Now to simulate the required network/proposing latency. It's problematic when we try to test a simulation with long network latency. Instead, Scheduler would try to execute the event with minimum timestamp, thus time.Sleep is replaced with Scheduler.nextTick, and time.Now is replaced with Event.Time. Changes: - Add test.Scheduler. - Add test.Stopper interface to provide encapsulate different stop conditions for scheduler. - Add a reference implementation for test.Stopper, it will stop scheduler when all validators confirmed X blocks proposed from themselves. - Add a test scenario on core.Consensus that all validators are not byzantine.