Skip to content
← Open Cap Table Protocol Canton Node SDK

Reference

lookupTransferCommandCounterByParty

GET scan-proxy transfer command nonce counters safeguarding splice-token transfer deduplication semantics per sender party.

lookupTransferCommandCounterByParty pairs with lookupTransferCommandStatus when diagnosing asynchronous transfers referencing commanded workflows.

Setup

import { Canton } from '@fairmint/canton-node-sdk';

const canton = new Canton({
  network: 'devnet',
  provider: '5n',
  partyId: 'OWN_PARTY_ID',
});

Import and receiver

import { Canton } from '@fairmint/canton-node-sdk';

Receiver: canton.validator.lookupTransferCommandCounterByParty.

Minimal example

const { counter } = await canton.validator.lookupTransferCommandCounterByParty({
  party: 'Alice::1220...',
});

Parameters

  • party (required, string) — Sender authority embedded REST path segment referencing hashed ledger identifiers.

Returns

Object exposing:

  • counter (number) — Next nonce expectation enforced server-side before accepting additional asynchronous commands.

Errors and pitfalls

  • Unknown parties produce REST failures identical canonical semantics—ensure hashed identities mirror ACS watchers.

Auth and party

Authenticated bearer token referencing Validator scan-proxy GET semantics—must observe whichever visibility Canton grants caller referencing asynchronous pipeline statuses.

See also

Source

src/clients/validator-api/operations/v0/scan-proxy/lookup-transfer-command-counter-by-party.ts on GitHub.