Fee

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. Fee
  2. Asset versus claim
  3. Asset

• ClaimRequired through Asset versus claim

  1. Fee
  2. Asset versus claim
  3. Claim

• TokenRequired through Asset versus claim

  1. Fee
  2. Asset versus claim
  3. Token

• Asset versus claimDirect prerequisite

  1. Fee
  2. Asset versus claim

A fee transfers assets, shares, or economic value from users or a product to a named recipient under an explicit charging base, rate, time rule, and settlement method.

Category: Products and vaultsContainer outline category cue

System record

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

Why it exists

Fees pay operators, managers, protocols, integrators, and service providers, while making the cost and incentive structure of a product part of its accounting.

Traditional-finance analogy

Management, performance, transaction, or redemption charge is the closest comparison recorded for this concept.

Where the analogy stops

• A smart contract can assess fees through asset transfers, share minting, exchange-rate changes, or transaction execution rather than a conventional invoice.
• Public code does not guarantee that users understand the charging base, compounding, high-water mark, governance power, or dilution effect.

Main actors

• ActorDepositor or shareholder
• ActorVault, fund, or protocol
• ActorManager or operator
• ActorFee recipient or treasury
• ActorGovernance or administrator

Assets and claims

Assets — controlled or transformed resources

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

• AssetUnderlying fee assets
• AssetFee shares
• AssetAccrued but unsettled fee value

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.

• ClaimFee recipient entitlement
• ClaimUser claim net of fees and dilution

A fee moves assets, shares, or economic value from a payer to a named recipient under an explicit charging rule.

Why it exists

Products use fees to pay managers, operators, protocols, integrators, custody, administration, and other services. Because fees alter NAV, ownership, or execution, they are part of financial accounting rather than decorative metadata.

Traditional-finance analogy

Management, performance, transaction, and redemption charges are useful analogies. Smart contracts can settle them by transferring assets, minting shares, changing an exchange rate, or taking value during a transaction. Public code does not ensure that a user understands compounding, dilution, or who can change the terms.

Name the complete rule

For every fee, identify the payer, recipient, charging base, rate unit, time basis, trigger, high-water mark or hurdle, settlement asset or shares, rounding, and change authority.

managementFeeValue
= chargingBaseValue * annualFeeRate * elapsedYears

performanceFeeValue
= eligibleProfitAboveHighWaterMark * performanceFeeRate

These equations are only models. A deployed product may use discrete periods, continuous accrual, average assets, ending assets, hurdle rates, crystallization dates, or fee-share formulas designed to produce a target post-mint ownership.

Fee settlement and state changes

Table: Fee settlement and state changes

Settlement	Product change	Holder effect
Transfer fee assets	Net assets leave the product	Share supply stays fixed; value per share falls
Mint fee shares	Net assets stay, supply rises	Existing holders are diluted
Entry or exit fee	Fewer shares or assets reach the user	Execution differs from ideal conversion
Performance fee	Part of eligible profit goes to recipient	Requires a profit base and checkpoint rule

Step-by-step accounting

1. Record the prior accrual checkpoint, NAV, supply, and high-water mark where applicable.
2. Compute only the eligible interval, base, profit, or transaction once.
3. Apply the rate using an explicit fraction, percentage, or basis-point conversion.
4. Convert value into fee assets or fee shares using the stated pre- or post-fee model.
5. Apply rounding in the disclosed direction and update recipient entitlement.
6. Reconcile product NAV, total supply, holder ownership, and the next checkpoint.
7. Report gross and net performance over comparable periods.

Return source and payer

Capital flow transfers fee assets from the payer or product to the recipient. Claim flow instead mints, accrues, or transfers a fee entitlement when settlement uses shares or a receivable. Return flow to the recipient is paid by users or product holders, not created by the fee mechanism. The named payer or diluted product holders absorb a valid charge; fee revenue is therefore a transfer, not an independent source of system-wide value.

Assumptions and failure modes

The model assumes one disclosed charging base, rate unit, time rule, checkpoint, recipient, settlement method, and rounding policy. Risk flow includes double accrual, wrong bases, retroactive changes, fee-on-fee compounding, and dilution hidden by unchanged balances. If code overcharges or charges twice, the payer or diluted holders bear the erroneous loss until a funded recipient refund, reserve, insurer, or other remedy reimburses it.

Engineer or auditor lens

Test zero and maximum rates, first and repeated accrual, elapsed-time boundaries, loss then recovery, high-water marks, deposits and withdrawals around checkpoints, profit before and after fees, share-mint algebra, rounding, decimals, recipient changes, governance delays, pauses, upgrades, and reentrancy. A fee charge must be idempotent for an already-accounted interval or profit amount.

Investor.gov’s fee bulletin shows how recurring and transaction charges can reduce investor value. ERC-4626 also distinguishes ideal conversions from fee-inclusive operation previews; neither source defines every on-chain fee formula.

Common misunderstandings

• “No asset transfer means no fee.” Minted fee shares dilute existing holders.
• “Two percent management fee means two percent of profit.” The base may be assets or NAV, not profit.
• “Gross APY can be compared across products.” Fees, costs, compounding, incentives, and valuation must be normalized first.

See how fees affect NAV and vault-share accounting.

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.

1. Equation 1

   $$\mathrm{managementFeeValue} = \mathrm{chargingBaseValue} \times \mathrm{annualFeeRate} \times \mathrm{elapsedYears}$$

   Plain-text equation: managementFeeValue = chargingBaseValue * annualFeeRate * elapsedYears

   Variables and units for equation 1

   Symbol	Meaning	Unit
   managementFeeValue	Management Fee Value	selected valuation unit (for example, USD)
   chargingBaseValue	Charging Base Value	selected valuation unit (for example, USD)
   annualFeeRate	Annual Fee Rate	fraction per year (1 = 100% per year)
   elapsedYears	Elapsed Years	years

2. Equation 2

   $$\mathrm{performanceFeeValue} = \mathrm{eligibleProfitAboveHighWaterMark} \times \mathrm{performanceFeeRate}$$

   Plain-text equation: performanceFeeValue = eligibleProfitAboveHighWaterMark * performanceFeeRate

   Variables and units for equation 2

   Symbol	Meaning	Unit
   performanceFeeValue	Performance Fee Value	selected valuation unit (for example, USD)
   eligibleProfitAboveHighWaterMark	Eligible Profit Above High Water Mark	selected valuation unit (for example, USD)
   performanceFeeRate	Performance Fee Rate	dimensionless fraction (1 = 100%)

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

   Each fee names its payer, recipient, charging base, rate unit, time basis, trigger, settlement asset or shares, and rounding direction

2. SP-02Desired · not evaluated

   A fee cannot be charged twice for the same interval, profit, deposit, withdrawal, or transaction

3. SP-03Desired · not evaluated

   Fee-share minting and fee-asset transfers preserve total ownership and NAV accounting after explicit dilution

4. SP-04Desired · not evaluated

   Rate, recipient, high-water mark, accrual checkpoint, and governance changes are authorized, bounded, and observable

Prerequisites

Direct dependencies recorded by this concept's canonicaldepends_on relationships.

• 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.

• FundPath 42

  A fund is a pooled investment product defined by an objective, eligible assets, management and control rules, valuation, fees, redemptions, and profit-and-loss allocation.

• VaultPath 67

  A vault is an on-chain asset container that accepts or controls assets, applies accounting and access rules, and may deploy capital through one or more strategies.

Knowledge check

Quiz

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

What problem does Fee exist to address?

Model answer

Fees pay operators, managers, protocols, integrators, and service providers, while making the cost and incentive structure of a product part of its accounting.

Mark as understood