Commission
Research
All research areas →

Agent Evaluation and Coordination

Generated-Code and GPU-Kernel Correctness

Federated Learning and Privacy

Decentralised Systems and Protocol

Methods
Papers
Collaborate
About Contact Bring a technical claim

Research topic · DePIN

Does the incentive actually produce the infrastructure?

A decentralised physical infrastructure network pays independent operators to deploy and run hardware. Whether it works depends on assumptions about those operators, about verification and about demand — assumptions that can be written down, modelled and stress-tested.

The situation

Which assumptions and simulations are needed to assess whether a physical-infrastructure incentive mechanism behaves as intended?

What you leave with

Written mechanism assumptions, an agent model, a sensitivity analysis over its uncertain parameters and a simulation others can re-run.

For: Protocol researcher; mechanism-design sponsor

Established background

The following is general field knowledge, stated cautiously.

DePIN (decentralised physical infrastructure networks) describes systems in which a protocol rewards independent operators, usually in tokens, for deploying and running physical hardware — wireless coverage, storage, compute, sensors or mapping. Three parts recur: a way to verify that service was provided, a reward rule that pays for it, and a demand side that is supposed to eventually pay for the service rather than rely on emissions alone.

Questions that come up repeatedly in discussion of such systems include whether verification can be spoofed, whether rewards attract supply where it is needed or merely where it is cheap, and what happens to operator behaviour when the reward’s value changes.

My result: the Generalised DePIN Protocol

Generalised DePIN Protocol: A Framework for Decentralized Physical Infrastructure Networks (sole author, arXiv 2311.00551, November 2023, preprint) proposes a general framework for DePIN systems: it identifies the components such networks share and formalises how they interact, so that different networks can be described in one structure. It is a design framework. It does not, on its own, simulate operator behaviour or test a specific network’s incentives — which is where the questions below begin.

Centralized Intermediation in a Decentralized Web3 Economy (preprint) is relevant background: decentralised infrastructure does not guarantee decentralised economic outcomes.

Open evaluation questions

These are research directions, not results.

  • Mechanism assumptions. Which assumptions in a reward rule are load-bearing, and which can be relaxed without changing the outcome?
  • Agent models. How simple can an operator model be and still predict entry, exit and gaming? When does adding bounded rationality or collusion change the conclusion?
  • Sensitivity analysis. Over what ranges of operator cost, verification error and demand does the mechanism still meet its stated objective?
  • Simulation. What should a reproducible DePIN simulation publish — code, seeds, parameter files, calibration data — so that two groups can disagree about assumptions rather than about implementation?

Illustrative example — not a client engagement. A sensor-network design claims its rewards will produce even geographic coverage. The study writes down operator cost, an assumed verification error rate and two operator types (honest, location-spoofing). A sweep shows coverage stays even while spoofing is rare, but above a threshold error rate rewards concentrate in dense areas. The report states that threshold, notes it rests on an assumed cost model, and recommends measuring verification error before launch.

Useful if

  • Your mechanism's claims depend on how operators respond to rewards, and nobody has varied those responses systematically.
  • You are funding or reviewing a DePIN design and want the conditions under which it fails stated before deployment.
  • An academic group wants a collaborator on DePIN mechanism modelling.

Not the right fit if

  • You need a token-price forecast or investment recommendation. A mechanism study models behaviour under assumptions; it does not predict markets.
  • You need a smart-contract security audit. That is a different discipline.
  • The mechanism is not yet specified enough to write down who is paid, for what, and how the work is verified.

What this produces

  • Assumption register. Every assumption the mechanism relies on — operator costs, entry and exit, verification accuracy, demand, reward schedule — with its source and how confident anyone is in it.
  • Agent model. Participant types (honest operators, profit-maximisers, Sybil or spoofing attackers, users), what each observes and how each decides.
  • Sensitivity analysis. Which parameters the intended outcome is sensitive to, and the ranges over which it holds or breaks.
  • Reproducible simulation. Code, configuration and seeds so a third party can re-run every reported scenario, published if the terms allow.

What you need before starting

  • Mechanism specification. Reward rules, verification or proof-of-service method, emission schedule and any slashing or penalties.
  • The intended outcome. What the mechanism is meant to achieve, stated measurably — coverage, uptime, cost per unit of service.
  • Available evidence. Any operator cost estimates, testnet data or demand assumptions, with their provenance.

Protocol

  1. 1
    Restate the claim. Turn 'the incentives align' into a testable statement about outcomes under named conditions.
  2. 2
    Write the assumptions. List them before modelling, and agree which are fixed and which will be varied.
  3. 3
    Build the agent model. Start with the simplest participant types that could break the claim, then add complexity only where it changes results.
  4. 4
    Sweep and stress. Vary the uncertain parameters, including adversarial strategies such as spoofed work, and record where the outcome changes.
  5. 5
    Report. State where the mechanism behaves as intended, where it does not, and which assumptions those conclusions rest on.

Limits and unfavourable results

  • A simulation shows behaviour under its assumptions. Real operators, regulation and markets can differ in ways the model does not capture.
  • Verifying physical work (location, uptime, coverage) is often the weakest link; a model can only treat it as a parameter unless real verification data is available.
  • My DePIN paper is a framework preprint. It is not, by itself, an empirical validation of any live network.

A study may conclude the mechanism fails under plausible conditions. That finding is reported in full, and a commissioned study's fee does not depend on it.

Evidence behind this page

Questions

What is the Generalised DePIN Protocol?

A framework paper, sole-authored and posted to arXiv in November 2023 (2311.00551), that sets out the common components and interactions of decentralised physical infrastructure networks as a general design. It is a preprint and had 9 citations on Google Scholar as of October 2026.

How do you validate a DePIN incentive model?

Write down the assumptions, encode them in an agent model, vary the uncertain ones in a sensitivity analysis, include adversarial strategies such as spoofed proofs of work, and publish the simulation so others can re-run it. Where real operator or testnet data exists, calibrate against it.

Can a simulation prove a DePIN mechanism works?

No. It can show the mechanism behaves as intended across the conditions modelled, and identify where it fails. The conclusion is conditional on the assumptions, which is why they are written down first.

Do you evaluate specific live DePIN networks?

Only where the mechanism is documented well enough to model and conflicts are disclosed. I do not publish claims about a live network's economics without a study behind them.

See also

Commission a scoped study

Send the mechanism specification, the outcome it is meant to produce and the assumptions you are least sure of. Public documents are enough to scope.

Last reviewed 2026-10-07.