getMiningRoundDetails

getMiningRoundDetails complements getOpenAndIssuingMiningRounds when dashboards drill single epochs.

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

Minimal example

const details = await canton.validator.getMiningRoundDetails({ roundNumber: 42 });
console.log(details.mining_round.status);

Parameters

roundNumber (required, number) — Epoch encoded route segment appended verbatim.

Returns

Nested payload exposing issuance coefficients plus lifecycle transitions enumerated enumerations (open, issuing, closed). Inspect fields:

mining_round.round_number
mining_round.issuance_per_featured_app_reward_coupon
mining_round.issuance_per_unfeatured_app_reward_coupon
mining_round.effective_at
mining_round.status

Errors and pitfalls

Unknown epochs yield HTTP errors surfaced via SDK exception wrappers—cross-check getOpenAndIssuingMiningRounds.

Auth and party

Authenticated bearer token referencing Validator scan-proxy GET semantics.

Source

src/clients/validator-api/operations/v0/scan-proxy/get-mining-round-details.ts on GitHub.