Tokenized Infrastructure and Revenue-Share Tokens Explained

Tokenized infrastructure typically uses revenue-share tokens: instead of buying equity in the company that owns a solar farm, toll road, or data center, a token holder buys a right to a defined share of the cash the project generates, for as long as the token structure specifies. This is a meaningfully different claim from equity. An equity holder owns part of the company and its residual value; a revenue-share token holder owns a slice of the cash flow stream and generally nothing beyond it. That difference changes what can go wrong and how.

This article explains how infrastructure tokenization is generally structured, why revenue-share tokens are not equity, and the risks specific to this category.

What Infrastructure Tokenization Generally Looks Like

Infrastructure assets — renewable energy projects, toll roads, telecom towers, data centers, water treatment facilities — typically generate long-lived, contracted or regulated cash flows. A solar project, for example, may sell power under a long-term power purchase agreement (PPA); a toll road collects tolls from usage; a data center collects lease payments from tenants.

Tokenizing this kind of asset usually means a special purpose vehicle (SPV) holds rights to the project's cash flows — or a defined portion of them — and issues tokens that represent a proportional claim on distributions from that vehicle. The underlying physical infrastructure keeps operating under its existing ownership and operating structure; the token layer sits on top, distributing a share of what the project earns to token holders according to the terms set out in the offering documents.

Tokenization here is mainly an access and distribution mechanism. It can lower the minimum size needed to get exposure to a single infrastructure project and can make distributions and record-keeping more transparent, similar to how tokenization works for other real-world assets. It does not change the underlying project's engineering, contracts, or operating risk.

Revenue-Share Tokens Are Not Equity

This is the distinction that matters most in this category, and it is worth being precise about.

An equity holder in an infrastructure company owns a share of the company itself: its assets, its liabilities, its residual value if the company is sold, and (usually) some form of voting or governance right. If the project does better than expected, equity value can rise; if the company is sold, equity holders share in the sale proceeds after debt is repaid.

A revenue-share token holder, by contrast, typically has a contractual right to a defined share of specific cash flows — a percentage of revenue, or of a defined profit measure — for a set period or until a cap is reached, but usually has no ownership claim on the underlying asset, no residual claim if the asset is sold, and no governance rights over how the project is run.

Because a revenue-share token is a cash-flow claim, not an ownership claim, reading the token terms closely — what percentage, of what defined revenue or profit measure, for how long, and under what conditions the right can be reduced or terminated — matters more than reading a company's balance sheet.

How the Cash Flow Actually Moves

For a revenue-share token to pay out, several steps have to work in sequence, and each one is a place where the expected distribution can fall short of what was projected.

1. The underlying asset has to perform. A solar project has to generate the forecast amount of electricity; a toll road has to see the forecast traffic volume. Weather, demand, maintenance downtime, and broader economic conditions all affect this.
2. The offtake or revenue contract has to hold. If a power purchase agreement counterparty defaults, renegotiates, or the contract expires without renewal on similar terms, revenue can fall even if the asset itself performs physically as expected.
3. Operating costs and senior obligations get paid first. Maintenance, insurance, taxes, and any senior project debt are typically paid ahead of revenue-share distributions. Revenue-share tokens usually sit behind these obligations, similar to how capital structure seniority determines who gets paid first in any layered structure.
4. The SPV distributes what remains, per the token terms. Only after the steps above does the defined revenue-share percentage flow to token holders, on whatever schedule the documents specify.

A shortfall at any step reduces or eliminates the distribution for that period. There is no guarantee that a missed distribution is made up later unless the token terms specifically provide for that.

What to Check in the Offering Documents

Because a revenue-share token is defined entirely by its contract terms, the documents matter more here than in an equity investment where a balance sheet and audited financials give an independent read on value. A few questions are worth answering before treating any projected distribution as a realistic number:

• What exact revenue or profit measure is the share calculated on? "Revenue share" can mean gross revenue, net revenue after specific deductions, or a defined profit measure — each produces a different payout for the same underlying performance.
• Is there a cap, and how close is the project's projected lifetime cash flow to reaching it? A token capped well below the asset's expected total output behaves differently than one with no realistic cap.
• What happens if the offtake contract is renegotiated or the counterparty defaults? Some structures specify a floor or alternative revenue source; many do not.
• Who administers the SPV and reports on distributions, and how often? Reporting frequency and independence affect how quickly a shortfall becomes visible to token holders.
• Is there an independent engineering or production estimate behind the projected cash flows, or only the sponsor's own forecast? Third-party technical due diligence is standard in institutional project finance and is a reasonable baseline to expect here too.

None of these questions can be answered from a marketing summary alone. The same discipline used to read any RWA offering document applies directly to revenue-share tokens, arguably more so, since the entire return depends on how precisely the revenue-share right is defined.

Risks Specific to Revenue-Share Structures

Beyond the general risks any infrastructure or project-finance exposure carries (construction delay, technology or equipment failure, regulatory change, counterparty default on offtake contracts), revenue-share tokens carry structural risks tied specifically to the claim design:

• No residual claim. If the project is sold, refinanced, or wound down, revenue-share token holders typically have no automatic right to a share of the sale proceeds unless the terms explicitly say so — the token's value may simply end when the underlying revenue right ends.
• Term and cap limits. Many revenue-share structures run for a defined period or until a cumulative payout cap is reached. Once that point arrives, distributions stop even if the asset keeps generating cash for its actual owner.
• Subordination to project-level costs and debt. Operating expenses, insurance, and any project debt are typically paid ahead of the revenue-share, so a project can be "performing" at the physical level while still paying token holders less than projected due to costs above the revenue-share layer.
• Contract renewal risk. Long-dated offtake agreements (like a 15- or 20-year PPA) eventually expire; what happens to revenue after renewal at potentially different terms is a question worth checking in the documents rather than assuming continuity.
• Limited secondary liquidity. A single-project revenue-share token is a narrow, illiquid instrument; a secondary market for it may be thin or nonexistent, similar to the illiquidity premium priced into other non-listed RWA structures.

You can review how BiFu organizes real-world asset categories, including where structures like revenue-share tokens fit relative to funds, bonds, and equity, at BiFu RWA.

FAQ

Do revenue-share token holders own the infrastructure asset?

No. Revenue-share token holders typically hold a contractual right to a defined share of the asset's cash flows, not an ownership stake in the asset or the entity that owns it. This means no residual claim if the asset is sold, and usually no governance rights, unlike equity ownership.

What happens to a revenue-share token if the underlying project underperforms?

Distributions fall or stop, because the token's payout depends directly on actual cash generated after operating costs and any senior debt are paid. There is generally no fixed payment owed regardless of performance, and a shortfall is not automatically made up in a later period unless the token terms specifically provide for that.

Is a revenue-share token the same as a bond?

No. A bond typically pays a fixed or scheduled coupon regardless of the issuer's project-level performance, backed by a general repayment obligation, while a revenue-share token's payout is tied directly and only to the specific cash flows it references, with no fixed obligation to pay if those cash flows fall short.

How long do revenue-share token structures typically last?

It varies by offering. Some run for a fixed term, others until a cumulative payout cap is reached, and the specific terms are set in each offering's documents rather than following a single market standard. Always check the term, any cap, and what happens at expiration before assuming distributions continue indefinitely.

This content is for educational purposes only and does not constitute financial, investment, legal, tax, or trading advice. RWA products involve risk, including possible loss of principal. Always review product documents and risk disclosures before participating.

Related Reading

• For how seniority determines payment order in any layered structure, see capital structure and seniority.
• For the general tokenization mechanism this category builds on, see what tokenization is and how real-world assets become tokens.
• For a related cash-flow-based RWA vertical, see royalty tokenization for music and IP.