Portfolio Trackers
Portfolio trackers consolidate balances, positions and valuations across exchanges, wallets and protocols. Their purpose is to create a coherent exposure view, but aggregation introduce
Reading progress — saved on this device
Learning objectives
- Reconcile assets, liabilities and derivative exposures across venues.
- Avoid double counting wrappers, LP claims and collateralised positions.
- Use pricing and source timestamps that reflect executable reality.
What it is and why it matters
A portfolio tracker maps heterogeneous positions into a common reporting currency. Spot assets are straightforward until wrappers, staking receipts, LP tokens, lending claims and borrowed liabilities enter the portfolio.
Economic exposure differs from token balance. Holding an LP token represents claims on underlying reserves; holding a liquid-staking token embeds staking exposure plus basis and protocol risk. Counting both the receipt token and its underlying value separately creates false NAV.
Derivatives require delta or notional treatment rather than simple wallet balance. A short perpetual can offset spot beta even though collateral appears as a positive stablecoin balance.
Valuation needs price-source rules. Illiquid tokens may have a displayed market price that cannot support the portfolio size. Risk reporting can use liquidity-adjusted or conservative marks for such positions.
Operational framework
| Check | Purpose | What to verify |
|---|---|---|
| Position model | Defines exposure | Map spot, debt, LP, staking receipts and derivatives to economic claims. |
| Pricing | Defines NAV | Record source, timestamp and fallback for stale/illiquid assets. |
| Reconciliation | Tests completeness | Compare tracker balances with exchange statements and on-chain wallets. |
| Risk grouping | Reveals hidden concentration | Aggregate by asset, chain, stablecoin issuer, venue and protocol. |
Evidence, data quality and limitations
Read-only API integrations still create privacy and security considerations. Keys should use minimum scopes and no withdrawal permissions where the provider permits it. On-chain address tracking exposes portfolio composition to the tracker.
Trackers can lag corporate actions such as token migrations, forks, airdrops or redenominations. Reconciliation breaks should be investigated rather than manually forced to match without explanation.
Worked example and thought exercise
A portfolio holds £50k ETH and £50k of an ETH liquid-staking token. Reporting £100k as two independent asset classes overstates diversification because both are primarily exposed to ETH.
A lending position contains £20k collateral and £12k debt. Counting only the collateral overstates net asset value by £12k and understates leverage.
Thought exercise: Why can a portfolio tracker show the correct token balances but still report the wrong economic exposure?
Common mistakes and practical workflow
- Counting receipt tokens and underlying claims twice.
- Ignoring debt and derivative liabilities.
- Using one last-trade mark for an illiquid portfolio position.
- Granting third-party tracker APIs more permissions than necessary.
Practical workflow
- Inventory every exchange, wallet and protocol account.
- Map each token or contract position to its economic exposure and liabilities.
- Set price-source and stale-price rules.
- Reconcile totals against independent statements or explorers.
- Group risk by underlying asset, venue, chain and counterparty rather than ticker alone.
Knowledge checkpoint
- Why can LP or staking tokens be double-counted?
- How should liabilities affect NAV?
- Why can last price be misleading for illiquid assets?
- What API scope is appropriate for a tracker?
FAQs
❓ Should a tracker have withdrawal access?
Generally no; use read-only or minimum necessary permissions.
❓ What is NAV?
Net asset value: the value of assets minus liabilities under the chosen valuation policy.
❓ Why group by underlying asset?
Wrappers and derivatives can create multiple instruments with the same core economic exposure.
❓ Can trackers replace exchange statements?
No. Independent reconciliation remains important for accounting and error detection.
Summary
Portfolio trackers are exposure models, not merely balance screens. Correct aggregation requires liabilities, derivative and wrapper treatment, disciplined pricing and regular reconciliation.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →