Bittensor co-founder calls for restarting subnet community voting governance, criticizing Covenant AI founder’s decisions as malicious

TAO-16.59%

Gate News update: On April 10, regarding Covenant AI’s recent exit from the Bittensor network, Jacob Steeves, a co-founder of Bittensor, responded on Discord. He revealed that when the team launched dTAO a year ago, they originally planned to roll out a community-led subnet governance mechanism—namely, that subnet Alpha holders could use their wallets to vote to determine the hyperparameter team. However, because the early stage required giving subnet owners more control, this feature was postponed. Steeves believes that now is the right time to restart this discussion and proposes introducing a community voting mechanism to elect the team and reboot the subnet. He emphasized that, as one of the major holders, supporters, and technical contributors of Bittensor’s top three projects, he will personally participate in this mechanism, recommend suitable candidates, and continue to drive the project goals he initially co-established with Covenant AI founder Sam Dare. Meanwhile, Steeves was direct, saying that Sam Dare’s recent decisions were “clearly driven by malice and greed.” But he also pointed out that such crises often mean a new beginning, with the potential to redefine the subnet’s form and governance approach.

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments