Skip to content
← Open Cap Table Protocol Canton Node SDK

Reference

getDsoPartyId

Resolve canonical DSO (`digital sovereign operator`) party backing splice-token deployments routed via validator scan-proxy.

getDsoPartyId answers governance lookups referencing getInstrument metadata referencing instrument admins.

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.getDsoPartyId.

Minimal example

const { dso_party_id } = await canton.validator.getDsoPartyId();

Parameters

None.

Returns

Object exposing:

  • dso_party_id (string) — Canonical operator identifier required when validating splice disclosures offline.

Errors and pitfalls

  • Rare partial outages manifest when validator snapshot caches stale—refresh Canton topology watchers concurrently.

Auth and party

Authenticated bearer token—endpoint sits behind scan-proxy GET semantics identical across deployments.

See also

Source

src/clients/validator-api/operations/v0/scan-proxy/get-dso-party-id.ts on GitHub.