A useful fee disclosure makes the final receiving amount reproducible. A list of percentages is insufficient unless the user can tell who pays each fee, which amount it applies to and whether the output already contains the deduction.
The fields that resolve ambiguity
| Field | What it establishes |
|---|---|
| Charge category and recipient | Pool, interface, network or other payment |
| Payment asset | The token or native balance affected |
| Fee base | Input, gross output, surplus or another named amount |
| Inclusion status | Already in output or still charged separately |
| Amount and timing | Estimate, maximum, fixed amount or later reconciliation |
Apply the fields to a hypothetical disclosure
“Service charge: 0.20%” leaves several questions open. “Two output tokens, deducted from 1,000 gross output tokens, resulting in 998 received” establishes the asset, base and inclusion status. A separate network estimate can then be added without deducting the service charge twice.
If a protocol distributes one fee among different recipients, display the allocation as a breakdown rather than suggesting the user pays each allocation again. Uniswap's fee concepts illustrate why recipient-level accounting and trader-level charging are related but different views.
Expose uncertainty honestly
A dynamic fee or variable network estimate should not appear as a fixed guaranteed amount. State which value can change and which transaction constraint, if any, limits the user's spending or receiving result.
For a comparison publication, preserve unresolved fields instead of silently filling them with zero. A missing charge is not proven absent. Conversely, a fee described in documentation is not necessarily payable in every transaction; match the disclosed rule to the actual quoted route and user state. The aim is a ledger that another reader can reconstruct from the same evidence.
Sources & verification (1)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- Fees
Pool fee structure and distinct fee recipients; dynamic fees may vary.
https://developers.uniswap.org/docs/get-started/concepts/fees