Open thewhaleking opened 1 week ago
This is the list we use that we consider valid hyperparams:
serving_rate_limit min_difficulty max_difficulty weights_version weights_rate_limit max_weight_limit immunity_period min_allowed_weights activity_cutoff network_registration_allowed network_pow_registration_allowed min_burn max_burn adjustment_alpha rho kappa difficulty bonds_moving_avg commit_reveal_weights_interval commit_reveal_weights_enabled alpha_values liquid_alpha_enabled
However, getting the hyperparams for subnet 23 on testnet reveals these:
rho kappa immunity_period min_allowed_weights max_weight_limit tempo min_difficulty max_difficulty weights_version weights_rate_limit adjustment_interval activity_cutoff registration_allowed target_regs_per_interval min_burn max_burn bonds_moving_avg max_regs_per_block serving_rate_limit max_validators adjustment_alpha difficulty commit_reveal_weights_interval commit_reveal_weights_enabled alpha_high alpha_low liquid_alpha_enabled
Discrepancies: Existing on old:
network_registration_allowed network_pow_registration_allowed alpha_values
Existing on new:
tempo adjustment_interval registration_allowed target_regs_per_interval max_regs_per_block max_validators alpha_high alpha_low
This prevents setting hyperparameters in the "Existing on new" list.
This is the list we use that we consider valid hyperparams:
However, getting the hyperparams for subnet 23 on testnet reveals these:
Discrepancies: Existing on old:
Existing on new:
This prevents setting hyperparameters in the "Existing on new" list.