Community-owned providers and what governance actually buys

"Community-owned" is both the most honest and the most elastic label in infrastructure. At its best it means what Lido and Rocket Pool built: protocols where governance is published, parameters are on-chain, and no company can close your account. At its worst it is a token attached to a company. The four live protocols in this population are the real thing - 4 rows, all with published governance artifacts, 100% of them requiring no identity at any point - and this page maps what governance actually gives you and what it cannot.

What governance replaces - and what it does not

The trade you make with community ownership [3][4]:

• You trade counterparty risk for smart-contract risk. A company can vanish with your deposit; a contract can hold your deposit behind a bug. Lido's risk documentation is the honest template for how real this trade is [3].
• You trade contract law for governance process. No one to sue - instead, on-chain parameters, forum debates, and upgrade votes. That is a feature when the process works and a slow-motion hazard when it does not.
• Fees remain real. Community ownership does not mean free: Lido's 10% and Rocket Pool's roughly 14% commission pay for professional node infrastructure [4]. The difference is who the fee is accountable to.

Why fees survive community ownership

The recurring question in this category: if the community owns it, why am I still paying? Because node operators, audits and development are real costs, and community ownership changes who is accountable for them - not whether they exist [3][4]:

• Operator commissions pay professional infrastructure. Liquid-staking commissions fund machines, monitoring and incident response. The commission spread (10% vs roughly 14% in this population) prices different decentralization tradeoffs, not different greed.
• Treasury spending is the honest version of a business model. Instead of margins, a visible treasury with guardrails. Read it like you would read a company's cash flow - the same discipline the mining hub applies to operator margin.
• "Free" community protocols are subsidized somehow. Emissions, grants or volunteer labor - every one of them a schedule you should find before you depend on it.

The four live protocols, honestly

• ENS - the only mainstream on-chain naming system: NFT ownership, deep integration, full governance disclosure - financed by yearly rent, with short names renewing at three-digit annual rates [1].
• Namecoin - the opposite pole: genuinely decentralized, extremely cheap, no company at all - and it demands technical setup, with names that expire without renewal and thin markets behind them [2].
• Lido - the most liquid battle-tested liquid staking, with candid risk disclosure and DAO governance that owns its concentration problem in public [3].
• Rocket Pool - permissionless node operators and open on-chain parameters, at a higher commission, with exits that depend on deposit-pool liquidity [4].

Live from our database - caveats and sources in each linked review.

When community ownership is the wrong answer

The model has real failure modes, and they are not hypothetical [3][4]:

• Governance capture - large token holders voting their interest. Concentration in staking tokens and governance tokens is the same problem wearing different clothes; the staking hub prices the concentration risk directly.
• Crisis response is slow by design. A company patches in hours; a DAO votes in days. When a bug is live, that difference is your deposit.
• Exit is protocol-shaped. Liquid-staking tokens exit at market price - during stress, at a discount. Name registries require moving resolvers. The exit you would use in a crisis is the one to test while everything is calm.

If your threat model fears companies more than committees, this population is the right side of the trade. If the reverse, the company operators in the staking hub give you a counterparty and an SLA - a legitimate choice, not a concession.

How to evaluate governance quality

Three artifacts separate working governance from governance branding [3]:

1. Published risk documentation. The protocol that names its own risks (smart-contract, slashing, governance capture) is the one managing them. The staking hub prices the same disclosure on company operators.
2. On-chain parameter history. Real governance leaves a record - fee changes, upgrades, executed proposals. A governance system with no history is a governance system you are beta-testing.
3. A readable treasury. Who funds development, from what, with what guardrails. The treasury is where "community-owned" either means something or dissolves into a marketing claim.

The open-source hub covers the code side of the same question - and the two overlap heavily here, because in this population the license and the governance are the same trust model viewed from different angles. 0 operators from this vertical sit in our archive; none of the four live protocols above are there, and the reason is visible in their governance artifacts: 100% of the rows carry facts we verified ourselves, and all four publish the process behind their parameters.