Resolve the asset before its price
Build an asset record with the network, contract or mint identifier, display name, and amount scale. Match the oracle's base and quote assets to that record. In a hypothetical dashboard, an underlying token and a receipt representing it should not share a price assumption without a documented conversion. A recognizable logo cannot establish that the identifier, rights, or data source matches the intended asset.
Make the arithmetic traceable
Show how raw amounts become readable quantities and how those quantities combine with a quoted value. A fictional amount using six decimal places requires a different conversion from a price using eight. Keep exact transaction quantities separate from rounded display values. Review small amounts and boundary values, and document the direction of any rounding. The oracle validation article provides a worked example of tracking units.
Inspect permission independently
ERC-20 defines an allowance that lets a spender transfer tokens through an authorized workflow. In the wallet review, distinguish that permission from the amount intended for one purchase. State the exact spender and requested scope. If an interface advertises an oracle condition, identify where that condition is enforced. A price target described on a screen should not be treated as proof that the spender is technically limited by it.
Separate holder rights from issuer controls
Ask which authorities the particular token implementation exposes and who controls them. Review issuance, transfer restrictions, or configuration changes where they apply; do not assume every token supports the same mechanisms. For a tokenized claim, document what the token represents and the conditions for exercising that claim. The RWA wallet topic extends this review beyond an asset's market label and balance.
