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 CreateManagerResult = { hash, manager } — both the tx hash and the deployed clone address, parsed from the ManagerCreated event in the receipt.

Internally: createManagerwaitForTransactionReceiptparseEventLogs({ eventName: "ManagerCreated" }).

useCreateManagerAndGetAddress is a direct alias and behaves identically.

After a successful create, invalidate factory queries that depend on per-creator state:

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

Signature

@tokenops/sdk/fhe-vesting/react
ts
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
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 });
// create.data → { hash, manager }

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 › 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
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"],
    });
  },
});

See also

Other Setup · deploy hooks in vesting: