TokenStandardClient
CIP-0056 token standard client: holdings, two-step transfers, and the pending-instruction inbox — the read/write surface a wallet renders.
Reads go straight to the ledger (ACS filtered by the standard's interfaces, so any compliant asset shows up with no per-asset integration). Writes are externally signed: registry context via TransferRegistryClient, then prepare → sign → execute through InteractiveSubmissionClient.
Tracking: CIP-0112 (Token Standard V2 — batch settlement, account-based holdings) will extend this surface; V1 remains the interop baseline.
Types
Tunables shared by every client; only clockSkewAllowance so far.
One committed update's effect on a party's holdings: created holdings carry full views (credits); archived holdings surface as contract ids, and — when their creation was seen earlier in the stream — as resolved archived holdings with amounts and owners. summary is the transfer-level reading (direction, counterparty, signed net amount, memo) when one is derivable.
Functions
Cancels the party's active preapproval — the receiver archives it unilaterally (TransferPreapproval_Cancel), signed on-device. No registry context needed: the receiver is a signatory, so the contract is in its ACS.
Initiates a transfer as party (externally signed). Returns the update id is not yet surfaced — track completion via the instruction appearing in the receiver's inbox or the sender's ACS delta.
Accept/reject (receiver) or withdraw (sender) a pending instruction.
The party's holdings history between two offsets: every committed update that created or archived one of its CIP-0056 holdings, oldest first, with transfer-level HoldingsChange.summary rows. Defaults to genesis → current ledger end (a finite read).
Active holding UTXOs visible to partyId, any CIP-0056 instrument.
Pending two-step transfers visible to partyId — the wallet inbox. The receiver acts on TransferPendingReceiverAcceptance entries; the sender may withdraw anything still pending.
Requests a transfer preapproval for party (externally signed): once provider — typically the party's validator operator — accepts and pays, transfers to this party settle directly with no inbox round-trip. Track acceptance via ScanClient.transferPreapprovalByParty.