Skip to content

Validators unable to clear/reset axon back to 0.0.0.0 #1679

@CapriciousSage

Description

@CapriciousSage

Describe the bug

Due to various reasons, particularly with subnets changing hands over time, validators may end up with an axon set (often incorrect, set months ago from code long since gone anyway). On some subnets, in some instances, some validators encouter issues setting weights when they have an axon set. Not all the time, not every time, and not consistently, but it's just another thing that can cause headaches for validators.

To resolve this, the ideal would giving validators the ability to either "clear" their current axon or manually set it back to 0.0.0.0. This eliminates a low hanging fruit and speeds up subsequent investigations and diagnostic efforts into why weights are not being set correctly.

To Reproduce

Run various incarnations of subnet code over the years, end up with an axon on your validator, experience strange edge cases where your validator ends up being detected as a miner because it has an axon, and can't set weights properly. While correctly designed subnets should not have this issue, we run the subnet code we have, not the subnet code we wish we had.

Expected behavior

Allowing validators to reset/clear their axon would be a useful diagnostic tool to eliminate potential issues preventing validators from setting weights. This is not a panacea, it is merly another diagnostic and troubleshooting tool for validators to work through edge cases when they arrise.

Screenshots

No response

Environment

Not environment specific

Additional context

No response

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions