Outcomes post child-hotkey update #4
tobiashomie
started this conversation in
General Bittensor Discussion
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've got a question about validator incentives following the update on Sep 9, 2024.
Child hotkey take
In my view, this helps keep the ecosystem more secure from malicious activity in case a validator key is compromised. At least with this setup, other subnets aren’t as vulnerable, as long as the validator uses different hotkeys for each subnet.
However, I’m still wondering what other effects this update might have on the community.
And to be honest, I feel this change also makes it tougher for new subnets to get emissions from validators. Previously, validators needed to set up on each subnet to boost their APY, but now, they no longer have to. As a result, teams behind new subnets will likely have to invest more time into convincing validators to set up on their subnet, rather than focusing purely on development.
Beta Was this translation helpful? Give feedback.
All reactions