Skip to main content

Tokenomics

DPO2U treats tokenomics primarily as an incentive design problem, not as a branding exercise around asset symbols.

The public documentation stance should therefore be conservative:

  • the economic model matters
  • the incentive model is part of the protocol thesis
  • not every backend, asset, or settlement rail should be treated as equally live today

Why tokenomics is framed through ESS​

DPO2U's tokenomics is not just a treasury question. It is a question of incentive stability.

A plain Nash equilibrium is not enough. The more demanding question is whether honest validation remains stable when dishonest strategies appear and try to spread.

That is why the relevant framing is evolutionarily stable strategy (ESS).

The target condition is:

honest attestation and honest validation should remain economically robust against defecting strategies.

This remains a research and design program, not a finished theorem.

The stable economic ideas​

Regardless of which settlement backend is active in a given environment, the economic model is trying to preserve a few stable properties:

  1. work should be fundable
  2. validation should be rewardable
  3. dishonest low-effort output should become less attractive
  4. review, challenge, or replay should be cheaper than silent corruption

Economy layer vs execution layer​

The docs should distinguish two economic roles even when the concrete assets or rails evolve:

LayerPurpose
Economy layerpricing work, distributing rewards, carrying incentive logic
Execution layercovering the cost of verification, settlement, or backend transitions

That distinction is more important than any single ticker or chain-specific implementation detail.

Example reward split​

When a compliance task is completed, the system may split compensation asymmetrically between generation and validation.

RecipientExample shareWhy
Expert / generation role40%prepares documents, schemas, or workflow inputs
Auditor / validation role60%bears more adversarial and verification burden

The point of the split is architectural: validation-heavy roles should not be under-incentivized.

Treasury and replenishment model​

The reference self-funding agent on the Midnight preview network implements this loop. The cycle is:

  • Fee booking. For each priced attestation the agent books the fee in PaymentGateway (depositToTreasury).
  • Split. FeeDistributor.distributeComplianceFee accepts only a 40 / 60 split between the expert pool and the auditor pool: the contract asserts expert * 3 == auditor * 2.
  • Execution cost. Each transaction is paid with the agent's own DUST, which regenerates from the NIGHT it holds. A watchdog pauses the agent when DUST is below a floor.
  • Accounting boundary. The treasury and split are on-chain counters tied to real attestations. The client-to-agent NIGHT transfer is a separate step, and ComplianceEscrowV2 is the contract that custodies native NIGHT.

The reference deployment recorded 24 paid cycles on preview. See Self-funding compliance agents for the contracts, the paymaster design, and the read-only scripts that verify this state on the public indexer.

Current limits​

Public docs should be explicit about what is not yet a completed proof:

  • the final stability proof is not complete
  • the optimal penalty/reward ranges remain active research
  • not every environment exposes the same execution-cost backend
  • not every backend path should be treated as universally public

What the docs should claim confidently​

The docs can still claim a lot without overclaiming:

  • DPO2U has a serious incentive-design thesis
  • validation economics matters more than naive task completion economics
  • the system is designed so honest verification can be sustained operationally
  • ESS is the right framing for adversarial incentive analysis

Relationship to the rest of the stack​

Tokenomics should be read together with:

What this page intentionally avoids​

This page does not assume that:

  • one exact token pair is the final public truth forever
  • every settlement rail is equally mature
  • all compensation flows are already hardened end-to-end
  • the mechanism design theorem is finished

That restraint is a feature, not a weakness.