spike: define production environment setup steps

[teslashibe]

We have not gone through and e2e production (mainnet) deployment that sets hyperparameters that have been defined in masa-finance/masa-bittensor#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

• Define a min_stake as outlined here spike: research how vtrust and vpermit works masa-bittensor#88 when starting miners/validators
• Investigate number of neuron sample size (https://github.com/masa-finance/masa-bittensor/blob/a5e1c873251f284daa70fbf54af925f5c2a2226b/masa/utils/config.py#L204 - defaults is 50, but reasonable value is 5)
• Mainnet hyperparameters set
• Checklist created for mainnet releases
• Update checklist in here: https://github.com/masa-finance/roadmap/blob/main/.github/ISSUE_TEMPLATE/release-bittensor.md

Notes

For neuron sample size, see context in conversation: https://masafinance.slack.com/archives/C0742F6KXB8/p1721912473863099

[grantdfoster]

This checklist will build upon our current release checklist, and focus primarily on production setup.

Subnet Configuration

Initial Setup

• Establish an owner wallet (coldkey) for the subnet

btcli wallet new_coldkey --wallet.name owner

• Fund owner wallet w/ required TAO for registration. Current cost can be located at the bottom of https://taostats.io/. Right now it is 2592.35𝞃!
• Create the subnet!

btcli subnet create --wallet.name owner

Hyperparameters

• Set 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)

Miner Configuration

• --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

Validator Configuration

• --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

[Luka-Loncar]

@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?