All current open and issuing mining rounds, if the request is empty; passing contract IDs in the request can reduce the response data for polling/client-cache-update efficiency.
Documentation Index
Fetch the complete documentation index at: https://cantonfoundation-issue-365-details-history.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
The contract IDs for open_mining_rounds in the response the caller
knows about. If unsure, an empty array is fine; only a performance
penalty is incurred.
The contract IDs for issuing_mining_rounds in the response the
caller knows about. If unsure, an empty array is fine; only a
performance penalty is incurred.
ok
Daml contracts of the templates Splice.Round.OpenMiningRound and
Splice.Round.IssuingMiningRound representing rounds for which rewards
can be registered or are currently being computed, respectively.
Contract IDs in the input serve as input sets for the two
MaybeCachedContractWithStateMaps as described for that structure for
open_mining_rounds and issuing_mining_rounds.
Suggested cache TTL for the response; this should expire before the
opensAt of any open rounds that may not be in this response yet.
Always created with respect to an input set of contract IDs. If an input
contract ID is absent from the keys of this map, that contract should be
considered removed by the caller; if present, contract may be empty,
reflecting that the caller should already have the full contract data
for that contract ID. Contracts not present in the input set will have
full contract data. domain_id is always up-to-date; if undefined the
contract is currently unassigned to a synchronizer, i.e. "in-flight".
Always created with respect to an input set of contract IDs. If an input
contract ID is absent from the keys of this map, that contract should be
considered removed by the caller; if present, contract may be empty,
reflecting that the caller should already have the full contract data
for that contract ID. Contracts not present in the input set will have
full contract data. domain_id is always up-to-date; if undefined the
contract is currently unassigned to a synchronizer, i.e. "in-flight".