5 Commits (24f3a7524ab82299c4cf99d95cc3e45b9c318819)

Author	SHA1	Message	Date
Leo Chen	d1f7091127	[epoch] add IsLastBlock in shardingSchedule ... Signed-off-by: Leo Chen <leo@harmony.one>	5 years ago
Leo Chen	b7c34f37e7	[epoch] dynamically calculate the epoch number ... Signed-off-by: Leo Chen <leo@harmony.one>	5 years ago
Leo Chen	378c043778	[config] use a constant to define large block per epoch ... Signed-off-by: Leo Chen <leo@harmony.one>	5 years ago
Leo Chen	d6e091ce74	[config] make blocks per epoch configurable on network type ... Signed-off-by: Leo Chen <leo@harmony.one>	5 years ago
Eugene Kim	13b4e03674	Make sharding configuration flexible ... This is done by introducing two concepts: sharding configuration instance and sharding configuration schedule. A sharding configuration instance is a particular set of sharding parameters in effect, namely: - Number of shards; - Number of nodes/shard; and - Number of Harmony-operated nodes per shard. A sharding configuration schedule is a mapping from an epoch to the corresponding sharding configuration for that epoch. Two schedules are provided and to be maintained in the long term: Mainnet sharding schedule (4 shards, 150 nodes/shard, 112 Harmony-operated nodes/shard) and public testnet sharding schedule (2 shards, 150 nodes/shard, 150 Harmony-operated nodes/shard). Harmony node binary uses one of these for each -network_type=mainnet and -network_type=testnet respectively. In addition, for -network_type=devnet, a fixed sharding schedule can be specified with direct control over all three parameters (-dn_num_shards, -dn_shard_size, and -dn_hmy_size). The mainnet schedule code includes a commented-out example schedule.	5 years ago