useEncryptCampaignAmounts
Encrypt a plaintext roster into per-recipient handles, without building a tree.
@tokenops/sdk/fhe-airdrop/react{ mutate, mutateAsync, isPending, error, data }Description
Encrypt a plaintext roster into per-recipient handles, without building a
tree. Use it to persist the ciphertexts before committing to a root; if you
just want a campaign, useBuildMerkleCampaign does both stages.
A mutation rather than a query on purpose: encryption is randomised, so the same roster yields different handles every call and there is no legitimate cache identity to key. Persist what resolves — nothing here is recoverable or reproducible.
One relayer request per 32 recipients, issued concurrently; every leaf is submittable by any address. Split the roster yourself if your relayer rate-limits.
Invalidates: nothing. Pure off-chain relayer work — no contract state moves, so no cached read goes stale.
Signature
function useEncryptCampaignAmounts(options?: UseEncryptCampaignAmountsOptions): UseMutationResult<readonly EncryptedCampaignLeaf[], Error, EncryptCampaignAmountsVariables>;Parameters
Shape of the object you pass to .mutate(args).
| Property | Type | Description |
|---|---|---|
| encryptor | EncryptorSource | Eager or lazy encryptor. Wire it lazily so the live React context is read at submit time rather than captured at mount: const sdk = useZamaSDK() once, then encryptor: () => sdk. |
Example
const encrypt = useEncryptCampaignAmounts({ encryptor: () => sdk });
const leaves = await encrypt.mutateAsync({ instance: airdrop, recipients });Pulled directly from the hook's TSDoc block — the same snippet your IDE shows on hover.
Errors
This mutation can reject with SDK-level, product-level, or generic-fallback errors. Product classes carry the offending value as fields — render them inline instead of a generic "transaction failed." See Airdrop v2 › Errors for the per-class recovery table.
Invalidation recipe
After this mutation succeeds, invalidate the queries it affects so consumer UI re-fetches fresh state. The SDK never auto-invalidates — that's a consumer decision (different apps cache different shapes).
import { useQueryClient } from "@tanstack/react-query";
const queryClient = useQueryClient();
const encryptCampaignAmounts = useEncryptCampaignAmounts(/* options */);
encryptCampaignAmounts.mutate(args, {
onSuccess() {
// Coarse invalidation: refresh every cached read on this product surface.
queryClient.invalidateQueries({
queryKey: ["tokenops-sdk", "fhe-airdrop"],
});
},
});See also
Other Write hooks in airdrop v2:
useFundAirdropTop up an already-deployed instance's pool through the factory.useEcdsaClaimClaim a signed encrypted allocation on an ECDSAConfidentialAirdrop instance.useMerkleClaimClaim the outstanding amount for a proof-bearing entry on a MerkleConfidentialAirdrop instance.useGrantInstanceRolesSplit an airdrop instance's roles after create — one grantRole / revokeRole transaction per requested assignment, submitted in the order planInstanceRoleSplit computes.