useSignClaimAuthorization
Admin signs the off-chain EIP-712 Claim(address recipient,bytes32 encryptedAmount) message.
@tokenops/sdk/fhe-airdrop/react{ mutate, mutateAsync, isPending, error, data }Description
Sign a v2 Claim(address recipient, bytes32 encryptedAmount, bytes32
dedupId, uint256 deadline) authorization for an ECDSAConfidentialAirdrop
instance. The signer must hold SIGNER_ROLE on that instance.
Never sign with an EIP-7702-delegated key. A delegation switches verification to
ERC-1271 against the delegate, so every outstanding voucher fails although the key
keeps the role. See signClaimAuthorization.
airdrop and chainId come from the hook's own options, so a component
supplies only the claim fields.
Under `perDedupId` and `none` the contract enforces no per-recipient
ceiling. Every mode consumes the EIP-712 digest, so the exact signature
bytes cannot be replayed - but under perDedupId the same ciphertext
signed for two different dedupIds is claimable twice, and under none
every distinct signature is independently claimable with no on-chain
ceiling at all. The signing UI is then the ONLY bound on total payout. See
signClaimAuthorization.
Invalidates: nothing. The signature is produced off-chain and lands no transaction, so no cached read moves until the recipient claims.
Signature
function useSignClaimAuthorization(options: AirdropInstanceClientOptions): UseMutationResult<Signature, Error, SignClaimAuthorizationArgs>;Parameters
Shape of the object you pass to .mutate(args) is the SDK type SignClaimAuthorizationArgs. Inspect the type for the full shape (discriminated unions collapse to a tagged variant at call time).
Example
const sign = useSignClaimAuthorization({ address: airdropAddress });
const signature = await sign.mutateAsync({ recipient, encryptedAmountHandle, dedupId, deadline });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 signClaimAuthorization = useSignClaimAuthorization(/* options */);
signClaimAuthorization.mutate(args, {
onSuccess() {
// Coarse invalidation: refresh every cached read on this product surface.
queryClient.invalidateQueries({
queryKey: ["tokenops-sdk", "fhe-airdrop"],
});
},
});