Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix stake weight issues #998

Open
wants to merge 4 commits into
base: feat/rao-devnet-ready-2
Choose a base branch
from

Conversation

ales-otf
Copy link
Contributor

@ales-otf ales-otf commented Nov 19, 2024

Description

This PR fixes issues related to NeuronInfoApi inconsistencies. Currently NeuronInfoLite returns alpha, while NeuronInfo returns stake weight. This issue was discussed with @camfairchild and it was considered to use stake weights for stakes in NeuronInfo/NeuronInfoLite.

The issue was discovered during debugging: #879

No changes needed anymore related to NeuronInfoApi.

Also, during debugging, other issues were discovered (comment in #925 and related issue). This PR fixes these issues by changing initial TAO and Alpha for subnets to 1_000_000_000.

Initially the work were done on fix/neuron-info-lite-stake, but that branch were made from feat/rao-devnet-ready, so this branch just applies the changes to the new feat/rao-devnet-ready-2 branch.

Related Issue(s)

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Other (please describe):

Breaking Changes

As bittensor wallet previously relied on wrong data and for them the issue seemed like API returned stake vs alpha, they should adapt their code to use stake weights instead.

Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have run cargo fmt and cargo clippy to ensure my code is formatted and linted correctly
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants