import { ILogger } from "../onchain/types/logger.js"; import "../onchain/index.js"; import { AnvilClient } from "./createAnvilClient.js"; import { Address } from "viem"; //#region src/dev/securitizeUtils.d.ts interface ClaimDSTokenProps { anvil: AnvilClient; investor: Address; /** * DSToken addresses */ token: Address; /** * USD amount without decimals */ usdAmount?: string; marketConfigurators?: Address[]; rwaFactories?: Address[]; logger?: ILogger; } type ClaimDSTokensProps = Omit & { tokens: Address[]; }; export interface EnableDSTokenBackDatingProps { anvil: AnvilClient; /** * DSToken addresses whose compliance configuration should allow back-dating */ tokens: Address[]; logger?: ILogger; } /** * Restores `disallowBackDating` to its previous value on every compliance * configuration service that was changed. Safe to call more than once. */ export type RestoreDSTokenBackDating = () => Promise; /** * Sets `disallowBackDating` to false on compliance configuration services of * `tokens`, so that the issuance time passed to `issueTokensCustom` is * honoured: DS protocol silently replaces it with `block.timestamp` otherwise, * and freshly minted tokens stay under lock-up. * * Impersonates the DS trust-service admin of each token. Ownable `owner()` of * the compliance configuration service alone is not enough. * * The flag is only read while tokens are issued, so restoring it does not * re-lock tokens minted in the meantime. */ export declare function enableDSTokenBackDating(props: EnableDSTokenBackDatingProps): Promise; export declare function claimDSToken(props: ClaimDSTokenProps): Promise; /** * Helper function to claim DSToken from the faucet. * Works both for MockDStoken and real DSToken connected by securitize-deploy script * @param forkStatus * @param publicClient * @param investor * @returns */ export declare function claimDSTokens(props: ClaimDSTokensProps): Promise; //#endregion export {};