Sam Macpherson, chief executive of the decentralized finance protocol Spark, has made a public case for sub-DAOs as a governance fix, according to a report from CryptoBriefing. The proposal targets long-standing weaknesses in how decentralized autonomous organizations, or DAOs, make decisions and manage resources.
DAOs were designed to let token holders govern protocols collectively, without a central authority. In practice, many have struggled. Voter turnout is often low. A small group of large token holders frequently ends up steering outcomes. Proposals can take weeks or months to move through discussion, voting, and implementation, even for routine operational matters.
Macpherson's argument centers on breaking a single, monolithic DAO into smaller sub-DAOs, each focused on a specific function or business line. The idea is that narrower scopes let contributors specialize, move faster, and reduce the coordination overhead that comes with governing an entire protocol through one voting body.
This structure is not entirely new to decentralized finance. Similar concepts have circulated in the space for years, often framed as a way to let protocols scale without forcing every decision through a single governance pipeline. Supporters argue sub-DAOs can isolate risk, since a problem in one unit does not automatically threaten the rest of the organization.
Critics of sub-DAO models have raised concerns of their own. Splitting governance into multiple units can create duplicated infrastructure, inconsistent standards across units, and new coordination challenges between the sub-DAOs and the parent organization. There is also a question of how token holders retain meaningful oversight once decision-making authority is distributed across several bodies.
Spark operates as a lending and stablecoin-focused protocol within the broader decentralized finance sector, where governance design has become a recurring point of debate. As protocols grow in size and complexity, many teams have looked for structures that preserve decentralization while improving the speed and quality of decision-making.
Macpherson's comments add to an ongoing industry conversation about whether traditional, single-DAO governance can keep pace with protocols that manage growing amounts of user funds and increasingly complex product lines. The debate touches on core questions about decentralization, accountability, and operational efficiency that have followed DAOs since their earliest use in crypto.
Market Impact
Governance structure changes typically have an indirect effect on token markets, since they influence how quickly a protocol can adapt to competitive pressure or respond to risk events. If Spark or peer protocols move toward sub-DAO models, it could shape how other decentralized finance teams structure their own governance going forward.
Any near-term market impact from Macpherson's remarks is likely to be limited, since no protocol changes, votes, or timelines were described in the reporting. Token holders and developers watching the decentralized finance governance debate may nonetheless view this as a signal of where design conversations are heading across the sector.
The proposal reflects a broader, ongoing effort within decentralized finance to make DAO governance faster and more accountable, without abandoning the decentralization that defines the model.
Frequently Asked Questions
What is a sub-DAO?
A sub-DAO is a smaller decentralized organization that operates under a parent DAO, typically focused on a specific function, product line, or business unit.
Why are DAOs seen as having governance problems?
Many DAOs face low voter turnout, concentration of voting power among large token holders, and slow decision-making, which can hinder a protocol's ability to respond quickly to challenges.
What is Spark?
Spark is a decentralized finance protocol focused on lending and stablecoin activity, led by chief executive Sam Macpherson.
Has Spark announced any concrete plans to adopt sub-DAOs?
The reporting describes Macpherson making a governance argument for sub-DAOs, but no specific implementation plan or timeline was detailed.