galleon-defi-portfoliolisted

# DeFi portfolio and treasury Answer what the selected accounts own, owe and can access, what changed, and what evidence is missing. A portfolio report or target allocation is not authorization to move funds. ## Define the scope Establish included accounts and chains, ownership boundaries, reporting currency, valuation time, comparison period and purpose. Distinguish a watchlist from the user's own holdings. Preserve smart accounts, multisigs, exchange subaccounts and vault positions as separate identities; do not infer access to private exchange balances from an onchain address. Use [provider interfaces](references/providers.md) to fetch bounded account data through existing official tools. Use filters and pagination deliberately: a wallet-token endpoint may omit protocol positions. Mark unsupported chains, partial pages, delayed indexers and missing accounts as coverage gaps, not zero balances. Record provider retrieval time and position observation time separately. ## Reconcile before aggregating - Identify each position by chain namespace/ID, account, exact token or native-asset identity, protocol deployment, position ID and valuation block/time. Preserve provider IDs as opaque identifiers; a ticker or cross-chain logo is not a key. - Represent quantities as base-unit integers plus decimals, or exact decimal strings. Keep conversion rates, units and sources. Avoid binary float rounding when reconciling raw balances or debt. - Classify wallet holdings, supplied colla