v2.0.0-rc.1 release candidate

The API is frozen and later candidates carry fixes only, except the receipt-free and Safe create surface of /fhe-airdrop, which is @beta. Published on the next dist-tag; latest stays on 1.6.0 until 2.0.0.

WriteuseMutation Curated

useClaim

Recipient-side claim. For FeeType.Gas managers pass value (read it with useManagerFeeInfo); omit value for FeeType.DistributionToken.

Import

@tokenops/sdk/fhe-vesting/react

Return

{ mutate, mutateAsync, isPending, error, data }

Lifecycle

Write

Description

Claim the currently-claimable amount on a vesting schedule.

For `FeeType.Gas` managers, pass feeType: FeeType.Gas and value = fee (read it with useManagerFeeInfo). For FeeType.DistributionToken, pass that feeType and omit value.

After success, re-run useAccessClaimableAmount (it is a mutation that submits a transaction, so there is nothing to invalidate) to get a fresh handle, and refresh any UI counts you computed off it.

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

@tokenops/sdk/fhe-vesting/react

function useClaim(options: ManagerHookOptions): UseMutationResult<Hex, Error, ClaimArgs>;

Parameters

Shape of the object you pass to .mutate(args) is the SDK type ClaimArgs. Inspect the type for the full shape (discriminated unions collapse to a tagged variant at call time).

Run it

Connect your wallet and click Preflight and claim — this dispatches a real Sepolia transaction through the same runner the stories use.

Interactive · live Sepolia tx

Manager clone addressvestingId (32-byte hex)

Loading editor…

Edit any input above, then press ⌘↵ to run.

Console0 lines

No output yet. Run the snippet to see logs stream in.

Example

@tokenops/sdk/fhe-vesting/react · @example

tsx

const claim = useClaim({ address: managerAddress });
claim.mutate({ feeType: FeeType.Gas, vestingId, 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).

patterns/invalidation.ts

import { useQueryClient } from "@tanstack/react-query";

const queryClient = useQueryClient();
const claim = useClaim(/* options */);

claim.mutate(args, {
  onSuccess() {
    // Coarse invalidation: refresh every cached read on this product surface.
    queryClient.invalidateQueries({
      queryKey: ["tokenops-sdk", "fhe-vesting"],
    });
  },
});