Skip to content
Reading depth

Each view includes the earlier layers; the complete engineer or auditor page is shown by default.

An incentive is a payment, fee rule, discount, penalty, or token allocation designed to make a participant choose behavior the system needs.

Hexagon category cue

An incentive pays, rewards, discounts, or penalizes measurable behavior so that independent participants have a reason to perform a protocol function.

Protocols need liquidity, lending capital, liquidators, data reporters, validators, voters, and other external actors. Code can define the action but cannot compel participation. An incentive connects useful behavior to an economic consequence.

Performance compensation, a market-making rebate, or a service penalty is a useful analogy. The difference is that permissionless actors and composable contracts can optimize a rule at machine speed, while newly issued token rewards may be funded by dilution rather than operating income.

The payer may be a trader, borrower, protocol treasury, or token issuer. The recipient may supply capital, execute liquidation, report data, validate state, or vote. Fee revenue and reserve assets are existing value; newly issued tokens are new units. An accrued or vesting reward is a claim only under the eligibility and distribution rules.

  1. Define the target behavior and an observable measurement.
  2. Define payer, reward asset, rate, period, cap, and eligibility.
  3. Record eligible capital or work without double counting.
  4. Accrue and distribute or vest rewards under explicit claim rules.
  5. Measure whether the behavior persists and whether adversaries can game the proxy instead of producing the intended outcome.

Capital flow includes participant capital and paid rewards. Claim flow covers accrued rewards. Return flow names the payer: users and protocol revenue pay fees, a treasury spends reserves, or token holders bear dilution. Control flow follows whoever changes weights and eligibility. Risk flow includes sybil behavior, wash activity, bribes, mercenary capital, and reflexive token prices.

If subsidy attracts capital that leaves immediately, the treasury or token holders pay without buying durable service. If the rule is gameable, honest users can face worse liquidity, governance, security, or reward allocation.

Always ask who pays a reward. “Free tokens” can be a temporary subsidy whose market value and dilution change after the campaign ends.

Measure retained liquidity or service after subsidy, marginal cost per desired outcome, emissions versus fees, vesting, caps, recipient concentration, sybil resistance, bribes, wash activity, exit behavior, and governance control over weights.

Curve DAO gauges are one implementation in which protocol issuance is allocated according to gauge weights and eligible liquidity. That design illustrates the need to audit checkpointing, measurement periods, voting influence, boost rules, claim accounting, and emission caps; it is not a generic reward formula.

Bind reward state to one eligible identity, amount, period, and funding source. Test duplicate claims, boundary timestamps, stale checkpoints, self-dealing, sybil splitting, flash capital, ordering, rounding, cap exhaustion, governance changes, and zero-value activity.

  • “High APY proves high productive return.” Issuance and subsidy can dominate fees or external income.
  • “More deposits mean the incentive worked.” Capital can be temporary or economically unproductive.
  • “Users follow the intended behavior.” Rational actors optimize the encoded measurement, including its loopholes.

Read tokenomics. Continue to protocol treasury to identify whether rewards spend reserves or issue new units.

  • Curve, Curve DAO contracts and GaugeController — one gauge-weighted token-incentive implementation (accessed 2026-08-09).
  • The supplied DeFi seed, sections 7–9, 12, and 13 — fees, interest, liquidation bonuses, staking rewards, and token subsidy boundaries.

Machine-readable model

Key equations

Canonical expressions come from the structured concept record. KaTeX renders the notation, while the plain-text expression and variable table keep its meaning and units inspectable without JavaScript. Read the narrative above for the model's domain, assumptions, and rounding rules.

This concept does not require one canonical equation. Its mechanism and state transitions remain the authoritative explanation; do not invent a formula merely to make the topic look quantitative.

Assurance contract

Security properties

These structured statements define desired behavior. Their stable IDs can bind tests, invariants, specifications, audit findings, or proof results without turning descriptive review advice into an assurance claim.

Desired · not evaluated: No test, audit, or proof result is implied until scoped evidence is linked to this property.

  1. Reward eligibility, measurement period, units, funding source, caps, vesting, and claim lifecycle are explicit

  2. One unit of eligible work or capital cannot be counted repeatedly outside the documented rule

  3. Adversarial splitting, self-dealing, ordering, and sybil behavior cannot extract rewards beyond the threat model

  4. Reported return separates fees or external income from token issuance, dilution, and temporary subsidy

Knowledge check

Quiz

Answer in your own words, then open the model answer.

Who pays a newly issued token reward?

Model answer

No existing asset necessarily leaves a payer's account, but current and future holders bear dilution and depend on market demand for the new units.