useEcdsaClaimAndUnwrap
Claim a signed encrypted allocation and route it straight into the wrapper's unwrap, making to the underlying ERC-20 beneficiary.
@tokenops/sdk/fhe-airdrop/react{ mutate, mutateAsync, isPending, error, data }Description
Claim a signed encrypted allocation and route it straight into the wrapper's unwrap,
making to the underlying ERC-20 beneficiary.
Reverts FeatureDisabledError on a non-unwrappable campaign - gate the button
on useAirdropConfig().unwrappable. Consumes the same replay guards and EIP-712
digest as useEcdsaClaim, and the same empty-proof rule.
The amount is public from the claim transaction. With the stock wrapper the unwrapped
amount is publicly decryptable at once (the emitted unwrapRequestId is its handle);
finalizeUnwrap only releases the ERC-20. Only a plain claim keeps it confidential.
Resolves to the claim's transaction hash; the underlying ERC-20 moves only at the
wrapper's later finalizeUnwrap. Pass the hash to useUnwrapRequest for the
unwrapRequestId that call takes.
Invalidates: the fn "isSignatureValid" PREFIX for this instance, exactly as
useEcdsaClaim does: the claim consumes the EIP-712 digest, so a cached true
is now a guaranteed replay. Per-claim dedup state itself remains unqueryable.
Signature
function useEcdsaClaimAndUnwrap(options: EcdsaAirdropInstanceClientOptions): UseMutationResult<Hex, Error, EcdsaClaimArgs>;Parameters
Shape of the object you pass to .mutate(args) is the SDK type EcdsaClaimArgs. Inspect the type for the full shape (discriminated unions collapse to a tagged variant at call time).
Example
const unwrapClaim = useEcdsaClaimAndUnwrap({ address: airdropAddress });
await unwrapClaim.mutateAsync({ encryptedInput, dedupId, deadline, signer, signature, to });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 ecdsaClaimAndUnwrap = useEcdsaClaimAndUnwrap(/* options */);
ecdsaClaimAndUnwrap.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.