Evaluate a portfolio tracker

Start with: token, lending.

A portfolio tracker aggregates balances and positions across addresses or networks. A read-only tracker usually needs public addresses, not spending permissions. Prefer the least access needed for the task.

Questions to compare

Question	Why it matters
Which networks and protocols are covered?	Missing coverage makes totals incomplete
How are token prices chosen?	Thin markets can create misleading values
Are debts and receipt tokens reconciled?	Poor accounting can double-count value
Are inactive positions and rewards shown?	A headline total may omit position state
When was each value updated?	Stale data can hide current risk

A dashboard can double-count a deposited asset and its receipt, omit debt, or assign a price from a thin market. A total is only as useful as the accounting behind it.

Reconcile one position

Choose a lending position you understand. Compare the tracker's collateral and debt with the protocol and explorer. Check the units and price timestamps. Then ask whether the displayed net value could actually be withdrawn after repayment and fees.

Unknown spam tokens may appear with large invented values. Do not follow their embedded links to “unlock” the balance. Hide them from your view without interacting onchain when the interface permits it.

warning — Viewing a public balance should not require a transaction, token approval or recovery phrase.

Privacy and permissions

Combining public addresses into one profile reveals relationships that may not otherwise be obvious. Understand what the service stores and shares. A wallet connection can disclose addresses even when it cannot spend.

Do not sign a transaction or grant a token allowance just to view a public balance. If a tracker also offers swaps or claims, evaluate those as separate financial actions. Keep your own list of positions and exit instructions so a dashboard outage does not remove your only overview.

Sources

• Ethereum explorers and indexed data
• Aave supply receipts