Closed teslashibe closed 2 months ago
This checklist will build upon our current release checklist, and focus primarily on production setup.
btcli wallet new_coldkey --wallet.name owner
btcli subnet create --wallet.name owner
weights_version
to 1
, or whatever value / version we are launching the validators as (1 == 0.0.1)
btcli sudo set --param weights_version --value 1 --netuid $(NETUID)
--blacklist.min_stake_required
controls the min stake required by validators for the miner to respond. this setting primarily takes effect in the subnet's infancy, where not all validator slots are filled and/or current validators have a low stake, making it easy for malicious validators to join and participate in the network. Defaults to 10--neuron.sample_size
controls hows many miners to randomly select to do work. this number will vary across validators who may have different use cases / products that they support. Defaults to 5@hide-on-bush-x can you review this please and provide us with some feedback?
Can we move to testnet with this cfg and see how it behaves?
We have not gone through and e2e production (mainnet) deployment that sets hyperparameters that have been defined in https://github.com/masa-finance/masa-bittensor/issues/61. We need to outline a deployment plan and checklist and run through this on mainnet with our current implementation so we can define a mainnet release plan that is used each time we release to mainnet.
Acceptance critereia
min_stake
as outlined here https://github.com/masa-finance/masa-bittensor/issues/88 when starting miners/validators5
)Notes
For neuron sample size, see context in conversation: https://masafinance.slack.com/archives/C0742F6KXB8/p1721912473863099