FOUNDATIONS · Last updated: 17 July 2026 · 14 min read · by Jordan, PassivePin Editorial

Node economics, explained

How DePIN projects are actually funded, why token price matters more than your earn rate, and the model we use to decide whether a project is worth your time before you deploy capital.

The flywheel, in one diagram

Every DePIN project is, at heart, a small economy. There are suppliers (operators providing bandwidth, storage, or compute), demand-side buyers (enterprises paying for that infrastructure), a token that prices and settles the exchange, and a protocol that takes a cut. If the economy is healthy, suppliers earn real money, demand keeps growing, and the token accrues value. If it is unhealthy, suppliers earn tokens that no one wants to buy, demand stalls, and the token dies.

The flywheel turns when the four pieces reinforce each other. More operators bring more capacity, which attracts more customers, which generates more revenue, which makes the token more valuable, which attracts more operators. The flywheel stops when any of those four pieces breaks. The most common failure is the third: customer revenue never arrives, the project relies on emissions to pay operators, and the token bleeds. The second most common is the first: operators arrive, but the product is not competitive, so customers do not, and the same outcome.

The four numbers that actually matter

Every project dashboard you read should be reducible to four numbers. If a project hides any of them, treat that as a red flag.

1. Customer revenue (last 30 days, USD). How much did the project actually earn from real customers. Not annualized, not "implied," not "at full utilization" — what the customer paid in the last calendar month. Render reports this; Hivemapper reports this; Helium reports this. The number is on the project dashboard, usually labeled "Revenue" or "Customer payments."

2. Operator payouts (last 30 days, USD equivalent). How much the project paid to operators in the last month. This is what you would have earned as a fraction of the network. For mature projects, this number should be 60-80% of customer revenue. For immature projects, it may be 200%+ of customer revenue, with the difference coming from emissions — meaning you are being paid in newly-minted tokens, not in customer cash.

3. Active operators (last 30 days, paid). How many distinct addresses or machines received a payout. This is the denominator. Divide payouts by operators and you get average revenue per operator per month, in USD. That is your expected earn. The honest projects publish this; the dishonest ones publish "registered operators" instead, which can be 10x higher than paid operators.

4. Treasury runway (months at current burn). How long the project can keep paying emissions-funded rewards if customer revenue goes to zero. This is the project's "land on a desert island" number. Helium's runway in mid-2024 was over 60 months; some smaller projects were under 6 months. Runway under 12 months is a high-risk indicator; the team may be forced to sell treasury tokens to keep the lights on, which suppresses the price.

Why emissions-funded projects eventually die

A project that pays you in tokens it mints today is, in effect, paying you with a promise: this token will be worth something tomorrow because other people will want to buy it. The promise holds as long as the project keeps adding new operators and new buyers. The promise breaks when the operator growth slows, because new buyers (speculators) need a steady stream of new supply (operators) to keep buying.

Every emissions-funded project has a clock. The clock starts when the project launches and the token is worth something because of speculative demand. The clock ticks down as emissions dilute existing holders. The clock ends when either (a) customer revenue grows to cover operator payouts, breaking the cycle, or (b) the price drops to a level where emissions-funded yields are no longer attractive, and operators leave, and the price drops further, and the cycle accelerates.

The 2022 bear market was an extreme example of this. Helium, the most famous DePIN project at the time, was paying operators almost entirely in emissions. When the broader crypto market fell 80%, new buyers dried up, the HNT price fell 95%, and many operators turned off their hotspots. The project survived because it had a real product (LoRaWAN coverage) and a real customer base (IoT networks), but the operators who joined in 2021 and sold in 2022 lost most of what they had earned.

Why revenue-funded projects can still fail

A project with real customer revenue is in a much stronger position than one without, but it is not bulletproof. The most common failure modes:

Customer concentration. If 50%+ of revenue comes from a single customer, the project is one contract renewal away from collapse. Hivemapper had this risk in 2024 when a single mapping customer was 60% of revenue; the team has since diversified.
Token overhang. Even with revenue, a project with a large locked supply of tokens that unlocks over the next 12-24 months will face sell pressure regardless of fundamentals. We look at the unlock schedule as carefully as we look at revenue.
Competitive pressure. A project with a working product and a customer base today may be disrupted tomorrow by a cheaper alternative. Helium's IoT business is now competing with several new LoRaWAN networks; Render's GPU business competes with AWS, GCP, and a dozen DePIN competitors .
Operational risk. A smart contract vulnerability, a key compromise, or a regulatory action can wipe out a project's revenue overnight. The October 2024 Radiant exploit drained $50M+ from a DeFi project in a single transaction; the equivalent in DePIN would be a customer data breach or a node exploit that breaks customer trust.

Our model for scoring a project

The scoring rubric on our methodology page is informed by these four numbers, but it is not a pure mechanical formula. The judgment calls are:

Revenue-to-payout ratio > 0.6 (i.e., at least 60% of operator payouts come from customer revenue, not emissions). Projects below this threshold get a 2/5 on longevity. Projects above 1.0 get a 4/5 or 5/5.

Operator growth > 0% month-on-month, with no single month below -10%. Flat or growing operators mean the project is still attracting supply. Sharp drops signal a problem.

Top customer < 30% of revenue. We penalize customer concentration. The exact threshold is a judgment call; a single 35% customer is a yellow flag, not a red one.

Treasury runway > 24 months. Below 12 months is a red flag; 12-24 is yellow; above 24 is healthy. We compute this at the project's current burn rate, not at a hypothetical "lean" burn.

Unlocked supply < 15% of circulating per month. If more than 15% of the circulating supply unlocks in any given month, the sell pressure is large enough to be worth pricing in.

No project scores 5/5 on every factor; the weighted average is what determines the directory ranking. A project can score 5/5 on revenue and 2/5 on transparency and still rank well overall, but we publish the sub-scores so you can decide which factors matter to you.

Practical steps before you deploy

Before you run a node, stake a token, or buy a piece of hardware for a DePIN project, do these five things.

Read the project's last 6 months of treasury reports. If they do not publish them, assume the worst.
Look up the top-customer concentration. If you can find it on Token Terminal, Dune, or the project's own dashboard, great. If you cannot, ask the team in their Discord. If they refuse to answer, that is the answer.
Compute the implied earnings yourself. Take last month's operator payouts in USD, divide by active operators, multiply by your expected share (which depends on capacity, location, or stake). If the number is 10x your cost in tokens and 0.1x in revenue, you are looking at a yield that will not last.
Check the token unlock schedule. Most projects publish this in their docs. If the next 6 months have 20%+ supply unlocking, the price is going to face headwinds regardless of operational performance.
Test with the smallest possible commitment first. Run one bandwidth project for a month before you buy a $499 dashcam. Stake the minimum before you buy a GPU. The first 30 days are diagnostic, not profitable.

If a project passes all five checks and you still want to deploy, you are probably making a good decision. If it fails two or more, the risk-adjusted return is not worth it, even if the headline rate looks attractive. DePIN is a category where the boring projects (mature, revenue-funded, transparent) outperform the exciting ones (high yield, new, narrative-driven) over a 12-24 month horizon.

Continue learning: Evaluating an airdrop before you farm it →