WriteuseMutation Curated

useInitiateVestingTransfer

Recipient initiates a two-step transfer of a vesting position to another recipient.

Import

@tokenops/sdk/fhe-vesting/react

Return

{ mutate, mutateAsync, isPending, error, data }

Lifecycle

Write

Description

Initiate a two-step transfer of a vesting to a new owner. The new owner must call useAcceptVestingTransfer within transferDurationSeconds or the transfer expires.

After success, invalidate usePendingVestingTransfer({ vestingId }).

Signature

@tokenops/sdk/fhe-vesting/react

function useInitiateVestingTransfer(options: ManagerHookOptions): UseMutationResult<Hex, Error, InitiateTransferArgs>;

Parameters

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

Want to run a similar shape interactively? The Playground ships 8 ready presets across vesting / airdrop / disperse — deploy a manager, create a vesting, claim, and the airdrop / disperse equivalents. The deep-link above auto-selects the closest preset to useInitiateVestingTransfer; pick another from the dropdown if you'd rather start there.

Example

components/useInitiateVestingTransferExample.tsx

tsx

"use client";
import { useInitiateVestingTransfer } from "@tokenops/sdk/fhe-vesting/react";

export function Example() {
  const { mutate, isPending } = useInitiateVestingTransfer();

  return (
    <button disabled={isPending} onClick={() => mutate(/* args */)}>
      {isPending ? "Sending…" : "InitiateVestingTransfer"}
    </button>
  );
}

Auto-generated from the hook's shape (the SDK doesn't carry a TSDoc @example here yet).

Errors

This mutation can reject with SDK-level, product-level, or viem-passthrough errors. Product classes carry the offending value as fields — render them inline instead of a generic "transaction failed." See Vesting › 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 initiateVestingTransfer = useInitiateVestingTransfer(/* options */);

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