.svg)
Key Takeaways
- Disappointing payouts usually aren't a sign of a scam — they're often the predictable result of how a reward model is structured.
- Three structural causes explain most of the gap between what people expect to earn and what they actually receive: pool dilution, concentration among top contributors, and retrospective lump-sum payouts.
- These issues can affect even commercially successful, legitimate networks.
- A short checklist at the end lets you evaluate any bandwidth-sharing network's reward model before you commit your connection to it.
The Gap Between Expectation and Payout
If you've shared your bandwidth through a dePIN network and ended up with far less than you expected, you're not alone, and it's probably not because the network lied to you outright. More often, the disappointment comes from how the reward model is built. Recent discussions around platforms like Grass have raised exactly this question — not whether the network is legitimate, but whether contributors can clearly see the value they're creating before they commit their connection to it.
There are three structural patterns behind most of this disappointment. None of them requires bad intent. All of them are worth understanding before you plug your bandwidth into anything.
For scale, MystNodes' network currently spans 135 countries, 31,000+ participating IPs, and has paid out $568,019 in total network earnings to date — real money already distributed, not a projected figure. Worth keeping in mind as you read the causes below, since it shows these dynamics play out across networks operating at real size, not just hypothetical ones.
Cause 1: Reward Pools Dilute as the User Base Grows
Many networks pay out of a fixed or semi-fixed reward pool rather than a fixed rate per unit of bandwidth. The pool is split among everyone who qualified that period, which means the value of your individual share depends not just on what you contributed, but on how many other people also contributed.
This creates a structural problem: growth for the network is dilution for the individual contributor. A network that successfully signs up ten times as many users doesn't have ten times the reward pool to match, usually — it has the same pool, or one that grows more slowly than the user base does. Your point, your share, your allocation — whatever it's called — is worth less simply because more people showed up, regardless of whether you did anything differently.
This isn't unique to any one platform, and it isn't necessarily a red flag on its own. It's a mathematical property of pool-based systems. The problem is when it isn't disclosed clearly, so contributors are surprised by a shrinking payout instead of expecting it.
This is exactly why MystNodes structures things the way it does: your base bandwidth earnings are a fixed rate per service, not a share of a pool, so they don't dilute as more people join. The optional reward system layered on top is still pool-based, and we're upfront that its per-point value moves with participation the way any pool does — but it's a bonus on your earnings, not the earnings themselves.
Cause 2: Payouts Concentrate Among a Small Number of High-Traffic Contributors
Reward systems that weight heavily toward volume, uptime, or stake tend to produce steep power-law distributions rather than even ones. A small number of contributors — those running multiple always-on devices, holding large token balances, or routing unusually high traffic — capture a disproportionate share of the total pool. Everyone else splits what's left.
This is a natural consequence of usage-weighted rewards, and in isolation, it's not unreasonable — someone contributing 50 times the bandwidth arguably should earn more. The disappointment sets in when marketing communicates an average or a best-case number ("earn up to $X") without making clear that the average casual contributor's realistic share is a small fraction of what the top contributors receive. The math isn't dishonest. The framing often is.
A fixed per-GB rate sidesteps this particular problem because your base earnings scale directly with what you contribute rather than with your share of a pool relative to everyone else. On MystNodes, a casual contributor and a multi-node operator are both paid the same transparent rate for what they put in — nobody's payout gets quietly squeezed because someone else joined with more hardware. The optional reward system does weigh toward token holdings and uptime, so it will naturally favor larger participants — we're not claiming otherwise there — but that's the bonus layer, not the base rate everyone earns from.
Cause 3: Rewards Paid in a Lump Sum Instead of Continuously
Some networks calculate and distribute rewards only at the end of a cycle — weekly, monthly, or tied to a broader event like an airdrop — rather than crediting contributors continuously as they earn. This has two compounding effects on how disappointing the experience feels.
First, there's a long gap between contributing and seeing anything for it, during which expectations tend to inflate — people imagine a bigger number than what eventually materializes. Second, and more structurally, retrospective lump distributions are exactly where causes 1 and 2 above do their damage most visibly: the pool-dilution math and the concentration effect both get finalized and revealed at once, in a single number, rather than being visible incrementally as you go. A contributor who could watch a running balance grow in real time would see the dilution happening; a contributor who finds out at the end of the month experiences it as a single disappointing surprise.
Continuous, contributor-initiated payout structures don't eliminate causes 1 and 2 — a pool is still a pool — but they remove cause 3's compounding effect, and they let you see and act on your actual balance rather than waiting for a reveal. MystNodes pays this way by design: base earnings accrue continuously as you contribute, and you decide when to settle — there's no monthly reveal, no waiting on a platform's schedule, and no cycle where the pool math gets finalized behind the scenes before you find out what you got.
A Checklist Before You Commit Your Bandwidth
Before signing up for any bandwidth-sharing or dePIN network, it's worth getting clear, ideally in writing, on:
- Is the payout a fixed rate or a pool share? A fixed rate per GB or per hour is predictable. A pool share is not — its value depends on total participation, which you don't control. MystNodes pays a fixed rate for base earnings, plus an optional pool-based reward system on top — so you get the predictability and the upside, rather than having to choose one.
- If it's a pool, how is the pool sized relative to the user base? Does the network disclose participant counts or pool size anywhere, or is that opaque? Ask any network this directly — including us — and see how clear the answer is.
- How often are rewards calculated and paid? Continuous accrual, which you can check anytime, is a different experience from a lump sum revealed at the end of a cycle. MystNodes rewards accrue continuously rather than on a cycle.
- Who decides when you get paid — you or the platform? A network where you can withdraw or settle on your own schedule behaves very differently from one that pays out on its own timeline. On MystNodes, that decision is entirely yours.
- Is there a minimum payout threshold, and what happens if you never reach it? Balances stuck below a withdrawal floor are earnings you can't access. MystNodes has no enforced minimum.
- Is the payment on-chain and verifiable, or does it rely on the platform's own reporting? On-chain payouts can be independently checked; self-reported numbers can't. MystNodes pays in MYST on-chain.
None of these questions requires you to distrust a network outright. They just move you from hoping the number will be good to knowing, structurally, what kind of number to expect. Run this checklist against whatever network you're considering — MystNodes included. We'd rather you ask it than take our word for it.
