Updated 18 November 2026 · DN permission-first guide
What matters
The safest way to monitor an on-chain portfolio is to give the tracker an address, not the ability to spend. Portfolio visibility and transaction authority are separate capabilities. Never upgrade a monitoring task into a signing session simply because an interface calls it ‘Connect wallet’.
The permission ladder: where monitoring becomes control
| Connection | What it does | DN risk test |
|---|---|---|
| Public-address import | Portfolio read/track | No spending authority; exposes address linkage |
| Public API / explorer | Balances, events, allowances | No signing; API limits and third-party logging |
| Wallet session / WalletConnect | Varies by request | Do not assume read-only; inspect requested method |
| Exchange API with trade/withdraw scope | Can place orders or move funds depending on permissions | Too much authority for portfolio tracking |
| Token approval or typed-data signature | May grant allowance, session authority or order rights | Not part of passive monitoring |
| Recovery phrase or private key | Full account control | Never give to a tracking service |
Three tools, three distinct jobs
- CoinStats: a multi-wallet overview; its official support documents a manual public-address import and states that MetaMask portfolio connections request view/read-only permissions. Verify the exact prompt on your own device and the current chain coverage.
- Koinly: portfolio transaction reconciliation and tax-record preparation. Import addresses and read-only data when possible, then review transfers, cost basis and supported jurisdictions.
- Ledger: a hardware-signing boundary rather than a promise of privacy. A hardware wallet does not stop address clustering or a user from approving a malicious transaction.
Always compare each provider’s supported networks and protocols against your actual positions. A tracking dashboard is an interpretation layer, not your canonical balance sheet.
DN Cross-Chain Reconciliation Checklist
For each wallet and chain, make one dated record and complete every item before acting on displayed totals:
The privacy cost of read-only tracking
Read-only is not private. Public addresses can reveal exposures, flows and counterparties, and linking several addresses to one cloud account may correlate them. Use separate monitoring identities where appropriate; minimise personal information and telemetry; enable MFA on tracker accounts; avoid sharing the full dashboard URL. Read-only prevents spending authority but not data leakage.
A practical reconciliation routine
- Start from the chain explorer and record the native token, block height and UTC timestamp.
- List protocol claims: lent principal, debt, LP interests, staking receipt tokens and pending withdrawals. Prevent double-counting underlying assets and receipt tokens.
- Mark stale prices, thin-liquidity marks and unredeemable or locked positions explicitly.
- Compare two independent valuation sources. When they disagree, explain the delta; do not average away an accounting problem.
- Export a dated snapshot and maintain a correction log, especially around bridged funds and tax lots.
Sources and commercial disclosure
- CoinStats: connect by public wallet address (official help, 2026).
- CoinStats: MetaMask view/read-only statement (official help, September 2026).
- Koinly official product information; check current integration, security and jurisdiction support.
- Ledger Academy for hardware wallet and recovery phrase practices.
Method: Product roles and permissions are grouped by capability. We have not independently penetration-tested these products, audited their code, or proven every chain integration works. Recheck providers’ permissions on the actual connection screen before use.
Affiliate disclosure: DN may have commercial relationships with listed services. Product presence is not a custody/security endorsement; no affiliate links are added until partner attribution is verified.
Frequently asked questions
Can a portfolio tracker steal crypto just by knowing my public address?
A public address alone cannot sign transactions. However, sharing addresses reveals holdings and transaction relationships; beware later requests for signatures, recovery phrases or spend approvals.
Is WalletConnect always read-only?
No. A wallet connection can later request signatures and contract approvals. Inspect every permission and transaction instead of assuming a connection implies read-only operation.
Why do two DeFi trackers show different portfolio values?
They may differ in chain coverage, debt treatment, LP valuation, staking derivatives, prices, timestamps, spam filtering and bridge pending-state accounting.