There's an uncomfortable conversation happening behind closed doors at every crypto infrastructure project that's been through a token generation event.

It goes something like this: "We need to raise more capital. But the only way to do that is by selling the token. And every time we sell the token, we make the problem worse."

This isn't a bug in a particular project's tokenomics. It's a structural failure in how the entire category is funded.

I've spent years advising crypto infrastructure protocols on capital structure, and the pattern is now unmistakable. Projects aren't dying because their technology is bad. They're dying because the way they're funded creates an unavoidable, self-reinforcing collapse in token value — one that no amount of "better tokenomics" can fix.

At the heart of the problem is a simple but uncomfortable truth: Post-TGE, most crypto infrastructure projects have only one viable way to raise capital: selling their own token.

That single constraint is what ultimately destroys treasuries, wipes out communities, and turns promising protocols into cautionary tales.

The Two Funding Models That Dominate Crypto Infrastructure

Nearly all crypto infrastructure startups today rely on one of two capital structures:

  1. Direct Token Sales via a Foundation. The foundation sells tokens to fund development at a separate DevCo.
  2. The Bifurcated DevCo + Foundation Model. Venture capitalists invest in a private DevCo via equity or SAFEs. In parallel, they receive token warrants issued by a foundation or offshore entity (typically Cayman Islands or BVI).

On paper, this looks like alignment. The DevCo builds the technology, the foundation stewards the protocol, and investors are exposed to both equity and token upside.

In reality, it is not.

The Incentive Nobody Talks About

Venture investors in crypto infrastructure do not underwrite these deals for equity returns.

They underwrite them for token liquidity.

The DevCo equity has no realistic IPO path, no dividend profile, and no M&A market. It exists primarily for governance, control, and information rights. The token, by contrast, has a clear liquidity event at TGE, trades continuously, can be exited in tranches, and is the only credible path to returning capital.

Once you understand this, everything that follows becomes inevitable.

At TGE, the entire capital structure collapses into a single economic reality: The token is the investment. Everything else is structurally illiquid.

This means venture lockups are not alignment mechanisms — they're timing mechanisms. Post-unlock selling is rational, not malicious. And the DevCo becomes economically irrelevant as a return-generating entity.

From this moment on, the token is forced to perform two incompatible roles: a utility asset for the network and a liquidity instrument for capital providers.

No asset can sustainably do both.

The Infrastructure Token Death Spiral

Once a project reaches TGE, the following sequence unfolds with remarkable consistency. I call it the Infrastructure Token Death Spiral, and I've watched it play out dozens of times.

Step 1: Post-TGE Selling Begins

As vesting unlocks, VCs sell tokens to return capital, early investors rebalance risk, and unlock schedules become predictable sell events. This selling is structural, not emotional. It's rational portfolio management.

Step 2: Persistent Downward Price Pressure

Infrastructure tokens do not benefit from reflexive speculation the way consumer or meme assets do. Demand is functional, budget-constrained, and highly sensitive to price declines. As selling overwhelms organic demand, token prices grind lower — often regardless of network growth.

Step 3: Staking Becomes a Sell Mechanism

Most infrastructure protocols rely on staking yields (typically 6–10%) to stabilize participation. But yields are meaningless when the underlying token depreciates 25–50% annually. Node operators must sell rewards to cover costs. Staking rewards themselves become continuous sell pressure. Staking stops being a security mechanism and becomes a distribution pipeline.

Step 4: The DevCo Has No Revenue

Infrastructure protocols rarely generate off-chain operating revenue. Fees remain on-chain. Treasuries are denominated in a depreciating asset. Expenses are denominated in fiat. With no sustainable revenue stream, the DevCo has only one option: sell tokens to survive. This accelerates dilution and compounds price pressure.

Step 5: Builders and Communities Capitulate

As token prices fall, builder margins collapse, growth fails to translate into income, and participation becomes economically irrational. Even if transaction volumes grow 25% annually, a token declining 50% per year guarantees lower real earnings, reduced incentives, and community attrition.

Eventually, treasuries are depleted, development slows, talent leaves, and the protocol stagnates. Not because the technology failed — but because the capital structure ate itself.

Token Economies Are Eating Themselves From Within

This is the core failure mode of crypto infrastructure: Projects are forced to fund growth by liquidating the very asset whose value underpins their ecosystem.

This is not sustainable. It is not fixable with better emissions schedules. It is not fixable with longer lockups.

It is a capital markets problem.

The projects that recognize this are the ones with a chance to break the cycle. The ones that keep tweaking vesting schedules and staking rewards are rearranging deck chairs on a sinking ship.

Why Pure DATs Don't Solve the Problem

Over the past few years, Digital Asset Trusts (DATs) emerged as what looked like a promising bridge between crypto and public markets. The idea was simple: wrap tokens in a publicly traded vehicle, give traditional investors exposure, and unlock institutional capital for the crypto ecosystem.

But pure DATs — vehicles that simply hold tokens on their balance sheet — have a fundamental limitation. They function like token ETFs: valuation is driven by mark-to-market NAV, there's no operating revenue, and there's no sustainable funding model for the underlying protocol.

DATs expose investors to the problem. They don't solve it.

A trust that holds depreciating tokens still holds depreciating tokens. The infrastructure death spiral continues underneath, and the DAT simply gives public market investors a front-row seat to the decline.

The Missing Structure: Revenue-Generating Subsidiaries

Crypto infrastructure projects are missing a fundamental component that every mature industry relies on: independent, revenue-generating operating companies with real investor demand for equity.

Infrastructure DevCos should not rely exclusively on token issuance for capital. Instead, they should create wholly or partially owned subsidiaries, build revenue-generating applications on top of their own infrastructure, and structure those subsidiaries as companies investors actually want to own.

Most importantly: Those subsidiaries must be capable of going public.

This isn't a novel concept in traditional markets. It's how every major technology ecosystem actually works. AWS doesn't fund itself by issuing "cloud tokens." Microsoft Azure doesn't rely on diluting a protocol treasury. They generate revenue, attract equity investors, and use that capital to fund continued development.

Crypto infrastructure needs the same structure.

Why Public Equity Changes Everything

Public markets solve the exact problem crypto infrastructure cannot.

A publicly listed subsidiary provides liquidity via stock, not tokens. It attracts institutional capital with defined exit paths. It allows investors to recycle capital without touching the token. It creates ongoing demand for equity, not emissions.

This single shift breaks the death spiral.

With a revenue-generating public subsidiary, capital is raised through equity issuance, not token sales. The infrastructure token is no longer the primary funding mechanism. Token dilution slows dramatically. Sell pressure collapses. Builders retain margins. Communities remain economically aligned.

Meanwhile, the public subsidiary can contract with the infrastructure DevCo. The DevCo earns real revenue. Developers are paid from operating income, not treasury liquidation. Core protocol development continues sustainably.

The token is finally allowed to do what it was designed to do: secure and coordinate the network — not fund the company.

Enter the Hybrid DAT Strategy

This is where the model becomes concrete.

A Hybrid DAT combines material digital assets on its balance sheet (for listing compliance) with real-world, revenue-generating operations. It holds yield-producing token exposure while maintaining equity-based capital formation.

Under this model, the public company holds infrastructure tokens as strategic assets. Those tokens generate yield through staking, fees, and protocol incentives. But critically, the company also operates revenue-generating applications built on top of the infrastructure it supports.

Profits can fund operations, expansion, or dividends. Investors get liquidity through equity markets — not token dumping.

This aligns founders, builders, token holders, and public market investors for the first time. Everyone has a path to returns that doesn't require liquidating the token.

How This Fixes Tokenomics at the Infrastructure Layer

The downstream effects on the token economy are significant.

When a protocol has a revenue-generating public subsidiary, the DevCo no longer needs to sell tokens to fund operations. Treasury burn rate drops. The constant overhang of "when is the next token sale?" disappears. Token holders can finally evaluate the asset based on network utility rather than capital structure anxiety.

Staking economics start making sense again. When node operators aren't watching their rewards depreciate faster than they can earn them, participation becomes rational. Security budgets become predictable.

And builders — the people actually creating value on these networks — can finally capture the upside of their work. Growth translates into income, not just protocol metrics on a dashboard while their token compensation melts.

What This Looks Like in Practice

The framework I've been developing with clients has a few key components:

The Infrastructure Protocol continues to operate as designed: decentralized governance, token-based security, on-chain fee capture. Nothing changes at the protocol layer.

The DevCo shifts from a capital-consuming cost center to a contracted service provider. It earns revenue from the public subsidiary for continued development, maintenance, and technical services.

The Public Subsidiary operates applications that generate real revenue. It holds tokens on its balance sheet (both for yield and strategic reasons), but its value proposition to equity investors is the operating business, not just token exposure.

Token Holders benefit from reduced sell pressure, sustainable development funding, and a healthier overall ecosystem. Their tokens are no longer subsidizing the entire capital structure.

Equity Investors get exposure to crypto infrastructure economics through a vehicle they understand: a public company with revenue, margins, and a clear value creation story.

A Framework for Evaluating This Model

Not every protocol can or should pursue this structure. When I evaluate whether a project is a good fit, I'm looking at several factors:

Why This Is Inevitable

Crypto infrastructure cannot scale on token emissions alone.

The projects that survive the next cycle will be the ones that stop pretending otherwise. They'll build real businesses, attract real equity capital, and let their tokens do what tokens are actually good at: coordinating decentralized networks.

The projects that keep trying to paper over structural funding problems with creative tokenomics will continue the death spiral. They'll announce new staking programs, longer lockups, and "sustainable" emissions schedules. And their treasuries will continue to bleed out until there's nothing left.

Capital markets exist for a reason. Liquidity structures exist for a reason. Equity exists for a reason.

The question isn't whether crypto infrastructure will eventually adopt these structures. The question is which projects will figure it out first — and which will be cautionary tales for the ones that follow.

The Takeaway

Crypto infrastructure does not have a technology problem. It has a funding problem.

The dominant capital structure — DevCo equity that no one wants plus tokens that everyone has to sell — is designed to fail. Post-TGE, projects are trapped in a liquidation cycle that erodes value regardless of how good the underlying technology is.

The way out is straightforward in concept, even if it's complex in execution: decouple operating capital from token issuance. Build revenue-generating subsidiaries that can access public equity markets. Let the token be a coordination mechanism, not a piggy bank.

The protocols that figure this out will be the infrastructure layer of the next decade. The ones that don't will be footnotes in a long list of projects that had great technology and terrible capital structure.

And until the industry confronts this honestly, no amount of tokenomics innovation will save what is fundamentally a broken funding model.