6 Commits (222d0c981633c67e085019c4d41c1bf0f211576b)

Author	SHA1	Message	Date
Leo Chen	82307820d5	[resharding] add resharding epoch ... Signed-off-by: Leo Chen <leo@harmony.one>	5 years ago
Leo Chen	4bde201697	[resharding] add new node resharding/game support ... Signed-off-by: Leo Chen <leo@harmony.one>	5 years ago
Leo Chen	b0ef9ee231	[testnet] add 300 dummy keys to testnet configuration ... Signed-off-by: Leo Chen <leo@harmony.one>	5 years ago
Leo Chen	a7f4ea0374	[testnet] add two set of new dummy keys ... Signed-off-by: Leo Chen <leo@harmony.one>	5 years ago
Leo Chen	5f6a8a12bf	[resharding] add hmyaccount and fnaccount ... use configurable hmyaccount and fnaccount to create genesis block 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