Skip to content

Reference

getOpenAndIssuingMiningRounds

Snapshot open versus issuing mining rounds powering rewards dashboards referencing Canton sequencer timelines.

getOpenAndIssuingMiningRounds enumerates contract blobs referencing payout schedules consumed elsewhere (getMemberTrafficStatus).

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

Minimal example

const snapshot = await canton.validator.getOpenAndIssuingMiningRounds();
console.log(snapshot.open_mining_rounds.length);

Parameters

None.

Returns

Payload exposing:

  • open_mining_rounds — Each element bundles canonical ledger contracts referencing mining governance artifacts alongside payload timestamps (opensAt) plus enumerated round counters.
  • issuing_mining_rounds — Lightweight issuance tuples referencing contract identifiers still emitting coupons.

Errors and pitfalls

  • Validator outages propagate generic HTTP failures—retry referencing Canton ops dashboards.

Auth and party

Authenticated bearer token referencing Validator scan-proxy GET semantics—party involvement unnecessary purely informational read.

See also

Source

src/clients/validator-api/operations/v0/scan-proxy/get-open-and-issuing-mining-rounds.ts on GitHub.