Returns this address's current token balances, reshaped from the same aggregation
GET /token/positions serves into the Portfolio wallet-balance shape. This path
carries an embedded v1 and does not follow this service's /native//token//dtcc
prefix convention: it matches the route of the Blockdaemon Portfolio service contract
(see /portfolio/v1/{address}/transactions).

Not gated by commercial tier the way every other path in this document is. Every
caller can reach this endpoint regardless of which tier(s) this deployment is licensed
for; licensed tier instead decides what this response contains, additively: a
native-only deployment reports Canton Coin ("Amulet") only, and dtcc additionally
adds every other (DTCC registry) instrument. A deployment licensed for nothing returns an
empty wallet (200, no accounts), never a 403.

One account per distinct instrument this address holds — address (the account-level
field, not the path parameter) carries the instrument identifier (the literal string
"Amulet" for Canton Coin, or a real DTCC instrumentId), never a wallet address of its
own; nativeAmount (the real proto json_name — unusually camelCase, unlike every other
field in this response) is that instrument's GET /token/positions-equivalent total
(locked + available combined), as a raw unscaled integer paired with this account's own
decimals (a top-level field, not nested under metadata — see that schema's own
description). The same split is available separately via
metadata.canton_token_metadata.locked/.available (added 2026-10-06 — see that schema's
own description) — nativeAmount itself still never splits it out.

timestamp is a per-template-family aggregate (the most recent create/archive event
the service has indexed for that whole instrument family — Canton Coin's own, or the DTCC Holding
template's own), not a precise per-account/per-instrument "last touched" time — GET /token/positions's own aggregation does not retain that detail. Epoch seconds, as a
string carrying an int64 value.