Skip to content

btcli stake child set stopped working after subtensor 8.5.1 upgrade #276

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

Closed
antonr-p2p opened this issue Dec 21, 2024 · 3 comments
Closed

Comments

@antonr-p2p
Copy link

btcli stake child set stopped working after subtensor 8.5.1 upgrade.
It performs all the operations without errors, but nothing changes.
Even output after execution is the same as it was before.
It looks like it's related to the subtensor 8.5.1 upgrade.

Env tested:
CLI version 8.4.2

@antonr-p2p
Copy link
Author

@ibraheem-opentensor @thewhaleking sorry for pinging you directly, unfortunately that's a pretty urgent issue. Because of CR3 enablement some validators are stuck/has low vTrust and there is an urgent need to redelegate validator's stake for many SNs.

@ibraheem-abe
Copy link
Contributor

ibraheem-abe commented Dec 23, 2024

@antonr-p2p Can you confirm that the childkeys get set after 7200 blocks?

There was a recent change which introduces a cooldown period. If you try again within that period, the cooldown will reset.

Please see more detailed explanation here:

opentensor/subtensor#1050
https://discord.com/channels/799672011265015819/799672011814862902/1319417265707286569

Let me know if this answers your query.

@antonr-p2p
Copy link
Author

@ibraheem-opentensor yep, I confirm after 1 day delay it works. Sorry for pinging you, I was confused.

BTW can we improve btcli to show proper info about this? I think it's good to do like this:

  1. For btcli stake child set after finilizing show warning that it would be applied with delay of 1 day
  2. For btcli stake child get if change is in progress - show current and proposed states with time left (if possible)

This change would help others and would stop them from creating such false positive issues.

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

No branches or pull requests

3 participants