usePartialClaim
Claim less than the unlocked amount — leaves the remainder encrypted on the clone.
@tokenops/sdk/fhe-vesting/react{ mutate, mutateAsync, isPending, error, data }Description
Partial-claim a specific encrypted amount from a vesting. The SDK encrypts
the plaintext amount (or use args.encryptedInput to bypass).
Amount units: TokenOps confidential (ERC-7984) tokens use a 6-decimals
convention (1 token = 1_000_000 base units), not the 18 decimals typical of
ERC-20. Amount parameters are base units of the token's actual decimals:
for the CTTT test token (6 decimals) 1_000_000n = 1 CTTT, while the
transparent TTT test token uses 18 decimals.
After success, re-run useAccessClaimableAmount / useAccessSettledAmount (they are
mutations that submit a transaction, so there is nothing to invalidate) to get fresh
handles.
Silent-zero transfers. ERC-7984 transfers do not revert when the sender's encrypted balance is insufficient — the transfer succeeds and moves an encrypted zero instead. This is by design: reverting would leak balance information. The transaction receipt alone cannot tell you whether value actually moved.
Signature
function usePartialClaim(options: ManagerHookOptions): UseMutationResult<Hex, Error, PartialClaimArgs>;Parameters
Shape of the object you pass to .mutate(args) is the SDK type PartialClaimArgs. Inspect the type for the full shape (discriminated unions collapse to a tagged variant at call time).
Example
function Component() {
const zamaSDK = useZamaSDK();
const partial = usePartialClaim({ address: managerAddress, encryptor: () => zamaSDK.relayer });
partial.mutate({ vestingId, amount: 50_000n, value: gasFee });
}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 Vesting 2.0 › 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 partialClaim = usePartialClaim(/* options */);
partialClaim.mutate(args, {
onSuccess() {
// Coarse invalidation: refresh every cached read on this product surface.
queryClient.invalidateQueries({
queryKey: ["tokenops-sdk", "fhe-vesting"],
});
},
});See also
Other Write hooks in vesting 2.0:
useCreateVestingOpen a new vesting schedule on a manager — encrypts the amount client-side, submits the tx.useClaimRecipient-side claim. For FeeType.Gas managers pass value (read it with useManagerFeeInfo); omit value for FeeType.DistributionToken.useRevokeVestingAdmin revocation — clears the schedule (revocable variants only) and returns funds.useSplitVestingSplit one vesting into two with custom proportions; both stay encrypted.