The Unwritten Constitution: Why Bittensor Needs to Articulate Its Core Design Principles
Before we can truly decentralize governance, we must first agree on what we’re governing toward.
The Hidden Prerequisites of Decentralization
Much of the conversation around decentralizing Bittensor focuses on technical challenges: block validation, eliminating centralized control of sudo keys, implementing stake-weighted voting, and transitioning power to elected Triumvirates. These are real and important hurdles now being actively solved.
But there’s a deeper problem that technical solutions alone cannot address: we haven’t clearly articulated what Bittensor is supposed to be.
When community members debate whether a subnet should be burned, when validators disagree about enforcement mechanisms, when subnet owners clash with stakers over governance—these conflicts often arise not from bad faith, but from genuinely different mental models of what Bittensor is and what it should become.
If we decentralize decision-making without first establishing shared principles, we risk creating a democracy where voters don’t even agree on what country they’re governing.
The Space of Possible Bittensors
Consider that Bittensor’s current design represents just one point in a vast design space of possible systems. Different parameter choices create fundamentally different ecosystems:
- EMA half-life settings determine how “ruthless” the market is—how quickly subnets and miners fail if they’re not winning
- Burn police mechanisms (or their absence) determine who can remove bad actors and how
- The balance between global and local governance determines whether the whole network or individual subnet communities make decisions
- Permissionlessness requirements determine what kinds of projects can even exist as subnets
Some configurations favor rapid innovation and experimentation. Others favor stability and proven value. Some would be friendly to non-AI use cases; others would burn anything not focused on machine intelligence. Some might tolerate speculative dynamics; others would aggressively police extractive behavior.
Which of these Bittensors are we building? The honest answer is: we don’t know. And more troubling: different participants are implicitly building toward different visions.
Core Values in Tension
From extensive discussion, several foundational values emerge—but they exist in genuine tension with each other:
1. Stake as Trust
The principle that stake represents authority and trust in the system. This is the foundation of proof-of-stake: those with skin in the game make decisions. Yet within subnets, subnet owners have fixed privileges (18% cut, sole hyperparameter control) that are not stake-weighted—a contradiction of this principle.
2. Permissionless Participation
The ability to mine or validate anonymously, without asking permission or revealing identity. This is cited as a “core design axiom”—yet it makes many things harder: real-world attestations, supply chain applications, research collaborations, and Sybil resistance. Some subnets (like the quantum subnet) have effectively abandoned permissionlessness entirely. Is that acceptable?
3. Market Sovereignty
The d-TAO market as the arbiter of value—prices and flows determine emissions, not committee decisions. Yet the market has information asymmetry problems, can be slow to respond to extraction, and may not reflect the values the community wants to optimize for.
4. Fixed Supply Scarcity
The commitment to never increasing token supply, creating trust through predictable scarcity. This is separate from decentralization and permissionlessness—you can have any combination. But changing supply, even once for good reasons, sets a precedent that erodes this trust.
5. Innovation vs. Exploitation
The tension between exploring new approaches and exploiting known-best strategies. Ruthless parameters kill innovation by eliminating the breathing room needed for experimentation. Generous parameters allow bad actors to survive longer than they should.
These values genuinely conflict. Permissionlessness makes certain valuable applications impossible. Market sovereignty can be too slow against extraction. Supporting innovation requires tolerating more failure.
A functional governance system requires that participants share enough common understanding to make principled trade-offs—not just vote their immediate financial interests.
The Two Markets Framework
One useful mental model that emerged: Bittensor operates as two overlapping markets:
The Capital Market (d-TAO): Where investors allocate liquidity to subnets, determining prices and emissions. This is where the question “how valuable is this project?” gets answered.
The Labor Market (subnets): Where workers (miners) permissionlessly contribute to tasks and get paid based on performance. This is where the question “how well did you do this work?” gets answered.
Validators straddle both: they judge work quality (labor market) but through stake-weighting also influence capital allocation. Root validators have global influence without subnet-specific investment—which from a subnet owner’s perspective raises legitimacy questions.
Should validators control both markets? Should the entities judging work quality also determine how much that work category is worth? These are design questions we haven’t explicitly decided.
The Governance Bootstrapping Problem
Here’s the recursive challenge: we need governance to decide on principles, but we need shared principles to have legitimate governance.
Current decision-making is caught in a bind. OTF and the Triumvirate have power but are reluctant to use it—because centralized intervention contradicts decentralization values, even when the intervention might be correct. Meanwhile, the community debates without shared axioms, often talking past each other.
The upcoming governance changes (elected Triumvirate, proposal voting) help with legitimacy but don’t solve the underlying problem. Decentralized voting on “should we burn subnet X?” still requires shared understanding of what makes a subnet burnable.
Macro vs. Micro Governance
As Bittensor scales to hundreds or thousands of subnets, global governance cannot handle individual subnet decisions. This suggests a need for micro-governance: each subnet having its own governance mechanisms (DAO contracts, validator councils, bicameral systems with houses for miners/validators/stakers).
The infrastructure for this exists—EVM support was built partly for subnet DAOs—but almost no one has implemented it. Why? Perhaps because subnet owners, having gained power, prefer to keep it. Perhaps because the incentives don’t reward governance experimentation. Perhaps because we haven’t articulated that decentralized subnet governance is actually a goal.
What Would Explicit Principles Look Like?
If we were to write them down, Bittensor’s core principles might include statements like:
-
Stake represents trust. Authority in the network derives from stake. Privileged roles not derived from stake should be minimized or eventually eliminated.
-
Permissionless participation is a core value (or: is an ideal but not absolute). The ability to work anonymously is protected, even when it creates challenges.
-
The market is sovereign (or: is presumptively sovereign but subject to governance override). Emissions follow price signals unless explicitly overruled through legitimate stake-based governance.
-
Supply is sacred. The total token supply will never be increased, regardless of other considerations.
-
Subnets must be verifiable. Work that cannot be scored by Yuma consensus is not legitimate for emissions.
-
Innovation requires slack. The system should not be so ruthless that experimentation is impossible.
-
Subsidiarity applies. Decisions should be made at the most local level capable of addressing them—subnet governance before global governance.
These are examples, not proposals. The point is that some version of explicit principles would give the community a shared language for resolving disputes, evaluating changes, and holding decision-makers accountable.
The Path Forward
Technical decentralization is necessary but not sufficient. Before (or alongside) transferring power to elected bodies, we need to:
-
Articulate the implicit principles that have guided Bittensor’s development. This may require direct engagement with the founders to document their original vision—not because it’s binding, but because understanding the original intent helps explain current design choices.
-
Identify genuine value conflicts and decide how to prioritize when they clash. Not every tension can be resolved, but we can establish which values take precedence in which contexts.
-
Create a shared vocabulary for discussing design decisions. When someone says “this subnet is bad,” what criteria are they applying? When someone says “this is too centralized,” what principle are they invoking?
-
Document the boundaries of the design space we’re willing to inhabit. What would make something not Bittensor anymore? What’s non-negotiable?
-
Build governance infrastructure that references these principles. Proposals should be evaluated against explicit criteria, not just majority preference.
Conclusion
Decentralization is not just about distributing power—it’s about distributing power in ways that produce good outcomes. A democracy needs more than voting mechanisms; it needs a constitution, shared values, and common understanding of what it’s trying to achieve.
Bittensor has made remarkable progress on technical decentralization. But as we prepare to transfer more authority to community governance, we face an uncomfortable truth: we’re asking people to govern a system whose fundamental nature remains implicit and contested.
The work of articulating Bittensor’s core design principles is not a distraction from decentralization—it’s a prerequisite for it. Without shared understanding of what we’re building, decentralized decision-making becomes a Babel of competing visions, each legitimate within its own framework, unable to resolve fundamental disputes.
The founders may have the original vision, but the community will determine the future. For that future to be coherent, we need to know what we’re building toward.
It’s time to write down the unwritten rules.
This piece synthesizes discussions among Bittensor community members working on documentation and education. The tensions and questions raised reflect ongoing debates, not settled conclusions.