Claim token

Reading depth

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

BeginnerCore purpose and mental modelPractitionerAdds mechanisms and economicsEngineer or auditorAdds state and verification

Dependency check

Advanced detail assumes prerequisite knowledge

Before using practitioner mechanisms or engineer and auditor checks, review any unfamiliar dependency. These paths come from canonical depends_on relationships; Web3 Academy does not track completed lessons.

Review 4 dependencies

• AssetRequired through Asset versus claim

  1. Claim token
  2. Asset versus claim
  3. Asset

• ClaimRequired through Asset versus claim

  1. Claim token
  2. Asset versus claim
  3. Claim

• TokenRequired through Asset versus claim

  1. Claim token
  2. Asset versus claim
  3. Token

• Asset versus claimDirect prerequisite

  1. Claim token
  2. Asset versus claim

A claim token records a transferable or account-bound entitlement to assets, income, redemption, governance, or another protocol-defined benefit.

Category: Money and assetsCircle category cue

System record

Start with the economic purpose, participants, resources, and entitlements before studying implementation detail.

Why it exists

Claim tokens make financial positions legible to software so wallets and protocols can account for, transfer, combine, or redeem those positions.

Traditional-finance analogy

Fund share, receipt, or account certificate is the closest comparison recorded for this concept.

Where the analogy stops

• Contract code can automate issuance and redemption, but the entitlement still depends on the issuer, backing, accounting, and applicable control rules.
• Transferability does not guarantee immediate redemption, fixed value, seniority, or legal recourse.

Main actors

• ActorClaim-token holder
• ActorIssuing protocol or contract
• ActorUnderlying asset provider or obligor
• ActorRedeemer or authorized operator

Assets and claims

Assets — controlled or transformed resources

Assets are resources the mechanism moves, holds, values, or transforms.

• AssetUnderlying or referenced assets
• AssetClaim-token units

Claims — entitlements and corresponding dependencies

Claims are rights to value, repayment, redemption, control, or another party's performance; each depends on an obligation or system that must honor it.

• ClaimReceipt, share, debt, income, redemption, or governance entitlement

A claim token makes a protocol-defined entitlement legible to software as a balance, share, receipt, debt unit, income right, governance right, or other recorded position.

Why it exists

Protocols need to remember what users contributed and what they may later withdraw, redeem, receive, or control. A tokenized record can be accounted for, transferred when permitted, accepted by another protocol, or burned during settlement. That composability is useful precisely because the token is not necessarily the underlying asset.

Traditional-finance analogy

A fund share, warehouse receipt, account certificate, or debt instrument can each be a useful analogy. The analogy stops at the contract and governing rules. Transferability does not guarantee fixed value, immediate redemption, seniority, legal recourse, or even transferability to every account.

Common claim-token roles

Table: Common claim-token roles

Role	Classification	Typical entitlement	Value depends on
Receipt token	Redeemable claim	Return or accounting for deposited assets	Custody and redemption rules
Share token	Pooled share and often redeemable claim	A proportional interest in pooled assets	Net asset value, share accounting, fees, and strategy results
Debt token	Debt claim	A lender’s receivable or borrower’s recorded obligation	Repayment, interest accounting, collateral, and priority
Income token	Debt claim or derivative exposure	A defined future cash-flow component	The payer, maturity, contingency, and settlement rule
Governance token	Governance right	Voting or control rights	Scope, delegation, quorum, execution, and competing admin powers

A single token can combine roles. Analysis should name each entitlement rather than assuming every token is an ownership share.

Mechanism and balance-sheet changes

1. A user contributes an asset, service, or other qualifying right.
2. The issuer records its obligation and mints or credits claim units.
3. The claim may transfer, accrue, rebase, or change exchange rate.
4. A holder presents or burns the claim under the settlement rules.
5. The issuer transfers the asset or benefit and reduces its obligation.

Table: Mechanism and balance-sheet changes

Event	Holder	Issuer or protocol
Deposit and mint	Gives up an asset and receives claim units	Receives an asset and records an obligation
Profit or loss	Claim value may rise or fall	Assets or liabilities change under the accounting model
Transfer	Claim ownership changes	Aggregate obligation usually remains
Redeem and burn	Gives up claim units and receives value	Transfers value and reduces the obligation

Capital flow follows the contributed and redeemed assets. Claim flow follows minting, transfer, and burning. Return flow identifies the borrower, strategy, fee payer, protocol issuance, or other source that changes claim value. Risk flow reaches holders when underlying assets, obligors, accounting, liquidity, or settlement fail.

Return source and loss allocation

The claim token records value; it does not create that value. A borrower may pay interest, a strategy may earn trading fees, an issuer may make contractual payments, or governance may authorize token issuance. Fees, dilution, losses, and senior claims determine what remains for the holder.

Loss may first reach protocol reserves, junior tranches, equity, guarantors, or the claim-token holder. A claim advertised as “yield-bearing” is incomplete without the payer, mechanism, risks, and loss waterfall.

Engineer or auditor lens

Define the accounting model before reviewing code. Test mint and burn authorization, exchange-rate or index updates, decimal conversion, rounding direction, fee and dilution accounting, transfer restrictions, total-claim reconciliation, withdrawal limits, and one-time redemption. A zero-value contribution must not mint valuable claims, and burned claims must not withdraw more than their represented entitlement.

ERC-4626 standardizes an interface for tokenized vault shares, including conversions between assets and shares. It is one concrete claim-token pattern, not a universal accounting model and not evidence that an implementing vault’s assets, strategy, fees, or rounding are safe.

Common misunderstandings

• “A claim token is the deposited asset.” It is a separate position issued in exchange for, or linked to, that asset.
• “Transferable means redeemable.” Markets may trade a claim whose issuer limits, queues, pauses, or cannot satisfy redemption.
• “More units mean more value.” Rebases, exchange rates, dilution, fees, and losses can change value per unit.

Use the asset-versus-claim diagnostic to classify a new token before composing it into another protocol.

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. SP-01Desired · not evaluated

   Minted claim units correspond to value or rights contributed under the stated accounting model

2. SP-02Desired · not evaluated

   Redemption and withdrawal cannot transfer more value than burned claims represent

3. SP-03Desired · not evaluated

   Total claims reconcile with the issuer's recorded obligation or backing

4. SP-04Desired · not evaluated

   Rounding, fees, transferability, and redemption limits are explicit

Prerequisites

Direct dependencies recorded by this concept's canonicaldepends_on relationships.

• TokenPath 3

  A token is a programmable ledger entry that represents units a blockchain system can track and transfer.

• Asset versus claimPath 4

  The asset-versus-claim distinction asks whether a token is the resource itself or a right whose value depends on another asset or obligor.

Learn next

Concepts that directly depend on this one, ranked by the recommended learning path. Check each page for additional prerequisites.

• Lending poolPath 16

  A lending pool aggregates supplied assets, issues supplier claims, and makes available liquidity borrowable under interest and risk rules.

• Liquid stakingPath 66

  Liquid staking pools or delegates staked assets and issues a transferable claim whose value reflects the protocol's controlled stake, rewards, fees, and losses.

• Vault sharePath 68

  A vault share is a proportional claim whose asset value depends on the vault's recognized net assets, eligible share supply, fees, rounding, and redemption rules.

Knowledge check

Quiz

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

What problem does Claim token exist to address?

Model answer

Claim tokens make financial positions legible to software so wallets and protocols can account for, transfer, combine, or redeem those positions.

Mark as understood