import BigNumber from 'bignumber.js'; import { NextCheckpoints } from '../../../../../api/entities/Asset/Fungible/Checkpoints/types'; import { CheckpointSchedule, Context, FungibleAsset, Namespace } from '../../../../../internal'; import { CreateCheckpointScheduleParams, ProcedureMethod, RemoveCheckpointScheduleParams, ScheduleWithDetails } from '../../../../../types'; /** * Handles all Asset Checkpoint Schedules related functionality */ export declare class Schedules extends Namespace { /** * @hidden */ constructor(parent: FungibleAsset, context: Context); /** * Create a schedule for Checkpoint creation (e.g. "Create a checkpoint every week for 5 weeks, starting next tuesday") * * @note ⚠️ Chain v6 introduces changes in how checkpoints are created. Only a set amount of points can be specified, infinitely repeating schedules are deprecated * * @note due to chain limitations, schedules are advanced and (if appropriate) executed whenever the Asset is * redeemed, issued or transferred between portfolios. This means that on an Asset without much movement, there may be disparities between intended Checkpoint creation dates * and the actual date when they are created. This, however, has no effect on the Checkpoint's accuracy regarding to balances */ create: ProcedureMethod; /** * Remove the supplied Checkpoint Schedule for a given Asset */ remove: ProcedureMethod; /** * Retrieve a single Checkpoint Schedule associated to this Asset by its ID * * @throws if there is no Schedule with the passed ID */ getOne({ id }: { id: BigNumber; }): Promise; /** * Retrieve all active Checkpoint Schedules */ get(): Promise; /** * Retrieve the maximum allowed Schedule complexity for this Asset */ maxComplexity(): Promise; /** * Retrieve the cached next Checkpoint information for this Asset, aggregated across all of its active Schedules * * @returns `null` if the Asset has no active Schedules */ getNextCheckpoint(): Promise; } //# sourceMappingURL=Schedules.d.ts.map