woop/internal/configs/sharding/testnet.go

package shardingconfig

import (
	"math/big"

	"github.com/harmony-one/harmony/internal/genesis"
)

// TestnetSchedule is the long-running public testnet sharding
// configuration schedule.
var TestnetSchedule testnetSchedule

type testnetSchedule struct{}

func (testnetSchedule) InstanceForEpoch(epoch *big.Int) Instance {
	switch {
	default: // genesis
		return testnetV0
	}
}

var testnetReshardingEpoch = make([]*big.Int, 0)
var testnetV0 = MustNewInstance(2, 150, 150, genesis.TNHarmonyAccounts, genesis.FoundationalNodeAccounts, testnetReshardingEpoch)
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			`package shardingconfig`

[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			`import (`
			`"math/big"`

			`"github.com/harmony-one/harmony/internal/genesis"`
			`)`
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
			`// TestnetSchedule is the long-running public testnet sharding`
			`// configuration schedule.`
			`var TestnetSchedule testnetSchedule`

			`type testnetSchedule struct{}`

			`func (testnetSchedule) InstanceForEpoch(epoch *big.Int) Instance {`
			`switch {`
			`default: // genesis`
			`return testnetV0`
			`}`
			`}`

[resharding] add resharding epoch Signed-off-by: Leo Chen <leo@harmony.one> 5 years ago			`var testnetReshardingEpoch = make([]*big.Int, 0)`
			`var testnetV0 = MustNewInstance(2, 150, 150, genesis.TNHarmonyAccounts, genesis.FoundationalNodeAccounts, testnetReshardingEpoch)`