Asset versus claim
The asset-versus-claim distinction asks whether a token is the resource itself or a right whose value depends on another asset or obligor.
Category: Money and assetsCircle category cue
System record
Start with the economic purpose, participants, resources, and entitlements before studying implementation detail.
Why it exists
The distinction reveals who owes what, which redemption path exists, and where custody, credit, liquidity, or legal risk can enter a position.
Traditional-finance analogy
Banknote versus bank deposit is the closest comparison recorded for this concept.
Where the analogy stops
- The relevant distinction is the actual entitlement and dependency chain, not whether an instrument looks like cash in an interface.
- One token can combine contractual, protocol, governance, or derivative rights that do not fit one traditional instrument exactly.
Main actors
- ActorHolder
- ActorIssuer or protocol
- ActorObligor or custodian when the token is a claim
- ActorAnalyst or integrator tracing dependencies
Assets and claims
Assets — controlled or transformed resources
Assets are resources the mechanism moves, holds, values, or transforms.
- AssetDirectly controlled asset
- AssetUnderlying or backing asset
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.
- ClaimRedemption, share, debt, derivative, or governance entitlement
The most useful question in a layered financial system is not “what is this token called?” but “is this the resource itself, or a claim on something else?”
Why it exists
Section titled “Why it exists”Wallets flatten very different positions into rows of symbols and numbers. A native asset, issuer IOU, pool share, vault share, wrapped token, debt receipt, and derivative can all look similar. Their loss paths are not similar.
Separating asset from claim reveals the backing, obligor, redemption rule, control authority, and loss absorber that would otherwise remain hidden behind the balance.
Traditional-finance analogy
Section titled “Traditional-finance analogy”A banknote-versus-bank-deposit comparison is a useful starting point: one is the settlement asset in its own system, while the other is a claim on an institution. The analogy stops at the actual entitlement and dependency chain. One token can combine contractual, protocol, governance, and derivative rights that do not fit either traditional instrument, and an interface can make an indirect claim look as immediate as a directly controlled asset.
Step-by-step diagnostic
Section titled “Step-by-step diagnostic”For each token or position, answer these questions in order:
- Recorded unit: What exactly does the ledger count?
- Economic object: Is that unit directly useful, or does it reference another asset, payment, service, vote, or price?
- Obligor: Who or what must perform for the holder to receive the benefit?
- Backing and custody: Where is value held, and who controls it?
- Settlement: How, when, and by whom can the position be redeemed or closed?
- Control: Who can mint, freeze, upgrade, revalue, or change eligibility?
- Loss: Who is short when code, backing, markets, custody, or enforcement fails?
Comparison table
Section titled “Comparison table”| Position | Classification | Directly recorded object | Additional claim or dependency |
|---|---|---|---|
| Native network asset | Direct asset | Protocol ledger units | Network validity and key control |
| Fiat-backed stablecoin | Direct asset plus redeemable claim | Issuer-created token units | Conditional redemption and reserve/issuer performance |
| Wrapped token | Redeemable claim | Wrapper units | Conversion into locked or custodied underlying units |
| Lending receipt | Debt claim and redeemable claim | Protocol claim units | Pool liquidity, borrower repayment, and accounting |
| Vault share | Pooled share and redeemable claim | Proportional share units | Vault holdings, strategy results, fees, and withdrawal rules |
| Tokenized off-chain instrument | Depends on documented legal right | On-chain ownership or entitlement record | Legal documents, issuer, custody, servicing, and courts |
| Derivative token | Derivative exposure | Contract position | Collateral, price source, counterparty mechanism, and settlement |
A tokenized off-chain instrument still needs one or more concrete labels. A fund interest can be a pooled share, a bond or receivable can be a debt claim, a contractual conversion right can be a redeemable claim, a price-only instrument can be a derivative exposure, and a voting instrument can carry a governance right. “Tokenized” is a delivery mechanism, not a seventh economic classification.
“Direct” is always relative to a layer. A native asset is direct at the protocol ledger, but access still depends on keys and consensus. A tokenized security can provide a direct on-chain record while remaining an indirect claim on cash flows and legal rights.
Four-flow view
Section titled “Four-flow view”Capital flow tracks the economic value that enters, leaves, or settles the position. Claim flow tracks each entitlement from issuance through transfer, impairment, and settlement. Return flow traces value from a named borrower, user, issuer, strategy, or subsidy source rather than attributing it to the claim itself. Risk flow follows a failed asset, obligor, custodian, market, or control dependency until the shortfall reaches a named loss absorber.
Balance-sheet view
Section titled “Balance-sheet view”When a holder receives a claim token, the holder records an asset. Somewhere else, a protocol or issuer records an obligation or holds backing. If an analysis counts both the backing and the claim as unrelated net wealth, it has ignored the liability connecting them.
| Event | Holder | Issuer or protocol | Underlying layer |
|---|---|---|---|
| Issue claim | Gains claim asset | Adds obligation | Receives or designates backing |
| Transfer claim | Changes holder | Obligation remains | Backing usually does not move |
| Accrue return | Claim value may rise | Obligation increases or assets earn income | Borrower, strategy, or issuer pays |
| Redeem | Gives up claim; receives asset | Obligation falls | Backing leaves custody or protocol |
| Shortfall | Claim loses value | Cannot perform fully | Named party absorbs or socializes loss |
Return path and loss path
Section titled “Return path and loss path”A claim’s return is not evidence that the claim itself produces value. Trace the payment backward: borrowers pay interest, traders pay fees, issuers pay contractual income, and sponsors spend subsidies. Protocol issuance creates new units and can dilute non-recipients; price appreciation is a valuation change until a later buyer pays the realized sale price. Then trace failure forward: the underlying loses value, an obligor defaults, redemption becomes illiquid, and the claim trades below its expected value. Unless funded equity, a reserve, an insurer, or a guarantor takes the shortfall first, the claim holder absorbs it through lower value or incomplete settlement.
Engineer or auditor lens
Section titled “Engineer or auditor lens”Model the claim and backing as separate state domains. Define the conversion function, units, rounding, authorization, supply reconciliation, pause and upgrade behavior, and external trust inputs. Test that issuance cannot create unaccounted claims, redemption cannot settle twice, and insolvency remains visible rather than being hidden by stale prices or optimistic accounting.
Common misunderstandings
Section titled “Common misunderstandings”- “Redeemable means instantly redeemable by everyone.” Eligibility, queues, liquidity, fees, and operating hours can intervene.
- “One-to-one minting means one-to-one market value.” Market access and confidence can still move the traded price.
- “A tokenized asset removes intermediaries.” It may reorganize them into issuers, custodians, validators, administrators, and legal agents.
Primary references
Section titled “Primary references”The BIS tokenisation continuum
describes tokens as combining an ownership-information layer with rules and
governance. ERC-4626 gives a concrete
technical example by defining the underlying asset separately from vault
shares representing a fractional claim.
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.
Every layered token identifies its underlying asset or referenced benefit
Every claim identifies its obligor, redemption or settlement rule, and loss boundary
Interfaces do not describe indirect claims as risk-equivalent to direct control
Knowledge check
Quiz
Answer in your own words, then open the model answer.
What problem does Asset versus claim exist to address?
Model answer
The distinction reveals who owes what, which redemption path exists, and where custody, credit, liquidity, or legal risk can enter a position.