getValidatorUserInfo exposes non-sensitive operator branding consumed by wallets ranking validators.
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.getValidatorUserInfo.
Minimal example
const info = await canton.validator.getValidatorUserInfo();
console.log(info.user_name, info.party_id, info.featured);
Parameters
None.
Returns
GetValidatorUserInfoResponse:
party_id(string) — Validator operator party identifier.user_name(string) — Friendly operator label shown in UI surfaces.featured(boolean) — Whether downstream UX should highlight this validator.
Errors and pitfalls
- Network outages bubble as
ApiError.
Auth and party
Requires bearer token; sensitive deployments may still gate responses—expect graceful degradation.
See also
Source
src/clients/validator-api/operations/v0/get-validator-user-info.ts on GitHub.