Airdrop · ABIs · 2
Raw Airdrop ABI exports.
Factory ABI for clone deployment + fee config; per-clone ABI for claims and the EIP-712 verifier. Funding goes through the factory.
Available ABIs
confidentialAirdropFactoryAbi@tokenops/sdk/fhe-airdropFactory contract: createConfidentialAirdrop, createAndFundConfidentialAirdrop, fundConfidentialAirdrop, fee config, roles.
22 fns8 eventsconfidentialAirdropCloneableAbi@tokenops/sdk/fhe-airdropPer-airdrop clone: claim, EIP-712 domain separator, extend window, withdrawals, role mgmt.
33 fns13 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-airdrop
ts
import { getContract } from "viem";
import { confidentialAirdropCloneableAbi } from "@tokenops/sdk/fhe-airdrop";
// 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: confidentialAirdropCloneableAbi,
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.