Vesting · ABIs · 2
Raw Vesting ABI exports.
Factory ABI for deployment + fee config; manager ABI for the per-clone lifecycle. Both ship as plain JSON arrays consumable by any viem or wagmi flow.
Available ABIs
confidentialVestingFactoryAbi@tokenops/sdk/fhe-vestingFactory contract: createManager / createManagerWithOptions, address prediction, fee config, role mgmt.
28 fns10 eventsconfidentialVestingManagerAbi@tokenops/sdk/fhe-vestingPer-user manager clone: full vesting lifecycle, disclosure, encrypted views, RBAC.
75 fns23 events
Direct viem usage
The SDK client classes are the recommended surface — they handle encryptor resolution, branded ids, retries, telemetry. But the ABIs themselves ship for one-off reads, indexing, or third-party tooling integration.
@tokenops/sdk/fhe-vesting
ts
import { getContract } from "viem";
import { confidentialVestingManagerAbi } from "@tokenops/sdk/fhe-vesting";
// Attach directly to viem if you'd rather skip the SDK client class —
// useful for one-off reads or for surfacing the contract in your own tooling.
const contract = getContract({
address: managerAddress,
abi: confidentialVestingManagerAbi,
client: { public: publicClient, wallet: walletClient },
});
// Now you have a viem-typed contract — every method exists on contract.read /
// contract.write. The SDK client class wraps this with retries, encryptor
// resolution, branded ids — but the underlying ABI is the same.