Returns this address's transaction history, newest first, reconstructed from the
Canton Coin (native) and DTCC registry activity this caller's own resolved party
scope may witness. 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, which is shared across Blockdaemon's Data
Services APIs.

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 movements only, and dtcc additionally
adds DTCC registry transfer receipts. A deployment licensed for nothing returns an
empty page (200, no data), never a 403.

Each item reconstructs one Canton Coin transfer from the Holding contracts its own
ledger transaction consumed/produced, or carries one DTCC ExecutedTransfer receipt
directly — never both for the same underlying movement (a DTCC instrument transfer's
own Holding legs are deliberately excluded from the Canton Coin reconstruction so it is
never double-counted against its own registry receipt).

Several fields are populated with values this network has no real equivalent for yet,
rather than fabricated:

• hash is a synthetic value ("cds1-" + sha256(chainId + ":" + ledgerOffset)),
  not a real Canton updateId.
• block_hash and explorer_link are always absent — Canton has no block-hash
  concept and no block explorer this response can link to.
• status is always the literal string "Confirmed" — settlement here is final, and
  this endpoint has no source for a Pending/Failed value yet.
• Nothing price/FX-related is ever populated (fiat_type is accepted and silently
  ignored) — this service has no price source.

timestamp and block_number are strings carrying int64 values, not JSON
numbers (both would silently lose precision as numbers for some real values).
timestamp is epoch seconds. block_number is this response's synthetic
stand-in for a Canton ledger offset.

amount is always the raw unscaled integer, paired with that same event's
token.decimals — divide amount by 10^decimals to get the human-readable value
(e.g. amount: "150000000000" with decimals: 10 is 15.0000000000). Never parse
amount as a decimal on its own.

total is the number of items actually included in this response's own data —
not a count of every transaction matching this address across every page of
history. Computing a true cross-page total would require an additional, unbounded
scan of this party's entire ledger history this endpoint does not perform (the same
known limitation /dtcc/transfers//token/positions already document for their own
omitted pagination totalCount).