← blog
Tokenomics · Defensibility

Honest tokenomics: 8 safety rails on PCP.

Yoshi · 2026-04-17

Every DePIN token that has ever shipped has been compared to Pokt, The Graph, Ankr, and Helium. Most of them end up failing in exactly one of those four ways. If you are going to ship a DePIN token in 2026 — we shipped PCP — you owe a public defense of why your design does not collapse into one of the canonical failure modes. This is that defense.

I am writing this to argue with, not to sell. Where I think our design could still be wrong, I will say so.

The four canonical failure modes

PCP has to avoid all four. Here are the eight rails we designed to keep that promise. They are documented in tokenomics, stake, burn, and governance — this post is the argument, those pages are the spec.

Rail 1: emissions tied to paid work, not self-reported work

Pokt’s original mistake was that operators reported relay counts and got paid per reported relay. PCP emissions are tied to signed, paid calls. A call is only earning-eligible if it has a matching payment receipt from a real payer and a matching signed result (see the EIP-712 piece). Self-traffic between two operator-controlled wallets does not earn. Emissions track real paid demand. Where we could still be wrong: operators can recruit real payers into a collusive ring. We mitigate with rail 2.

Rail 2: payer-side attestation with distinct staker

Every paid call has two parties in the receipt: the operator signer and an independent payer-side attester. For collusion to earn PCP, both parties have to coordinate, both have to stake PCP, and both get slashed if the payment turns out to be a ring. This is expensive for attackers. Still not impossible; this is why rail 3 exists.

Rail 3: stake slashed on verifiable dishonesty

Operators post PCP stake proportional to the revenue they intend to earn. If a receipt they signed is proven forged — independently reproducible, any third party can replay the call and get a different result — the stake is burned, not redistributed. Burning, not redistribution, matters: if you redistribute slashed stake to snitches, you create a market for false accusations. We prefer the stake to simply disappear. Details in stake.

Rail 4: no ongoing subsidy past cohort year 1

The Graph’s issue was indexer subsidies that lived longer than real indexer revenue. PCP operators get a launch-cohort reward in their first year and nothing guaranteed after that. From month 13, they survive on fees only. If the fee floor cannot sustain them, they should leave. That is a correct economic signal, not a product failure. We would rather have 200 sustainable operators than 2,000 subsidized ones.

Rail 5: treasury cannot buy back tokens

Ankr-style tokens with centralized core infra often get propped up by treasury buybacks that the market eventually sees through. PCP treasury cannot purchase PCP on the open market. Ever. It can earn PCP through fees, and it can burn PCP that it earns, but it cannot buy. This removes the temptation to paper over structural demand weakness with a buyback headline.

Rail 6: fee floor is in stablecoins

A module that sells a call for 0.01 USD gets paid 0.01 USD. The router converts a portion to PCP for the burn-and-earn cycle, but the operator’s revenue is denominated in stables. This breaks the Helium pattern where the operator’s “revenue” depended entirely on token price. If PCP goes to zero, operators still earn stables as long as callers keep paying.

// Per-call economic flow
caller pays 0.010 USDC
   -> 0.0088 USDC to operator (88%)
   -> 0.0010 USDC to treasury (10%)
   -> 0.0002 USDC routed to PCP burn (2%)
operator also earns PCP dividend from burn, proportional to stake

Rail 7: burn is demand-sourced, not scheduled

A lot of tokens hide supply growth behind a “deflationary” burn that happens on a fixed schedule. PCP burn is 100% demand-sourced: 2% of every paid call’s USD value is used to buy PCP from the AMM and burn it. If nobody uses the router, nothing burns. If the router does a lot of business, the burn is large. This makes the token’s deflationary pressure a direct function of usage, with no way to fake it.

Rail 8: governance requires earned, not bought, weight

Helium got captured by large hardware holders. PCP governance votes are weighted by earned PCP held for minimum duration, not by bought PCP. You can buy the token and use it for payments, staking, or operator rewards, but governance power requires a track record of earning, which in turn requires operating honestly. This is hard to game because you have to actually serve real calls for months to accumulate voting weight. See governance.

Where we might still be wrong

I do not think this is airtight. Three residual risks.

  1. Payer-collusion at scale. If a sophisticated attacker runs a fake merchant AND fake operators AND fake payers, our defenses are layered but not infinite. Economic cost of attack is high; not infinite.
  2. Fee-floor races. If a competitor subsidizes below floor cost, operators may leave. Our defense is that attested routing beats unattested routing for any paying enterprise, and enterprises are where the revenue is.
  3. Governance capture via long-horizon accumulation. A well-funded actor could legitimately earn governance weight over many months. We treat this as a feature: if you actually operated for months without cheating, you earned your vote.
The defensibility page has the same argument side-by-side with each of Pokt, Graph, Ankr, and Helium. If you can break the argument, email us — anonymously is fine.

What we would undo if we could start over

One honest regret. Our initial supply schedule was a little front-loaded to fund the launch-cohort rewards. If we were launching today we would taper month 1 through 6 more aggressively so the first-year emissions do not look like a cliff. We cannot change this now without a hard fork we have no appetite for, so we compensate with treasury-side discipline — no buyback, no “strategic sales,” boring custody.

The rest, we would ship the same.

The Graph state-of-network — Messari
Pocket Network public postmortems
DePIN 2026 coverage — CoinDesk