Setup · deployuseMutation Curated

useCreateManager

Deploy a per-user vesting manager clone via the factory.

Import

@tokenops/sdk/fhe-vesting/react

Return

{ mutate, mutateAsync, isPending, error, data }

Lifecycle

Setup · deploy

Description

Deploy a new ConfidentialVestingManager clone via the factory.

Returns only a tx hash — not the manager address. The factory packs the deployment block number into the clone's immutable args, so the address is only knowable after the tx mines.

For the common "deploy a clone and use its address" flow, prefer `useCreateManagerAndGetAddress` — same submission, but it parses the ManagerCreated event from the receipt and returns the address in one call.

After a successful create, you should invalidate any factory-level queries that depend on per-creator state (e.g. useFactoryCustomFee({ creator })):

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

Signature

@tokenops/sdk/fhe-vesting/react

function useCreateManager(options?: BaseHookOptions): UseMutationResult<CreateManagerResult, Error, CreateManagerArgs>;

Parameters

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

Run it

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

Interactive · live Sepolia tx

ERC-7984 token addressDemo ARI on Sepolia. Bring your own ERC-7984 if you have one.userSalt (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 create = useCreateManager();
create.mutate({ token, userSalt });

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 createManager = useCreateManager(/* options */);

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