WriteuseMutationencrypts input Curated

useCreateVesting

Open a new vesting schedule on a manager — encrypts the amount client-side, submits the tx.

Import

@tokenops/sdk/fhe-vesting/react

Return

{ mutate, mutateAsync, isPending, error, data }

Lifecycle

Write

Description

Create a single confidential vesting schedule. The SDK encrypts the plaintext amount into an externalEuint64 and submits it with an input proof — callers never handle ciphertext.

Encryptor resolution. The hook-level encryptor (from ManagerHookOptions) is forwarded lazily to the SDK client. You can also pass encryptor per-mutation via args.encryptor to override it. If neither is present, the SDK throws Missing encryptor — pass encryptor… verbatim.

After a successful create, invalidate read queries that depend on recipient/vesting state:

const queryClient = useQueryClient();
const create = useCreateVesting({ address: managerAddress });
create.mutate(args, {
  onSuccess: () => {
    queryClient.invalidateQueries({ queryKey: ["tokenops-sdk", "fhe-vesting"] });
  },
});

Signature

@tokenops/sdk/fhe-vesting/react

function useCreateVesting(options: ManagerHookOptions): UseMutationResult<Hex, Error, CreateVestingArgs>;

Parameters

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

Run it

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

Interactive · live Sepolia tx

Manager clone addressDeploy one first via useCreateManager.RecipientAmount (bigint)Encrypted to euint64 client-side before submit.

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 create = useCreateVesting({ address: managerAddress, encryptor: () => useZamaSDK() });
create.mutate({
  params: { recipient, startTimestamp, endTimestamp, cliffSeconds: 0,
            releaseIntervalSecs: 86400, timelockSeconds: 0,
            initialUnlockBps: 0, cliffAmountBps: 0, isRevocable: false },
  amount: 1_000_000n,
});

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 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 createVesting = useCreateVesting(/* options */);

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