2.0 RC docsView 1.x docs
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.
Setup · deployuseMutation Curated

useCreateManagerAndGetAddress

Deploy a manager and wait for the receipt — returns the deterministic clone address.

Import
@tokenops/sdk/fhe-vesting/react
Return
{ mutate, mutateAsync, isPending, error, data }
Lifecycle
Setup · deploy

Description

Recommended factory entry point. Deploy a new ConfidentialVestingManager clone and resolve its address from the ManagerCreated event in the tx receipt — in one call.

Internally: createManager → waitForTransactionReceipt → parseEventLogs({ eventName: "ManagerCreated" }).

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

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

For Safe / multisig signers, pass waitForReceipt: false; see ReceiptMode.

Signature

@tokenops/sdk/fhe-vesting/react
ts
function useCreateManagerAndGetAddress(options?: BaseHookOptions): UseMutationResult<CreateManagerResult | PendingCreateManagerResult, Error, CreateManagerArgs & ReceiptMode>;

Run it

Connect your wallet and click Deploy a 2.0 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 = useCreateManagerAndGetAddress();
create.mutate({ token, userSalt });
// create.data → { hash, manager } (or a pending result with waitForReceipt: false)

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
ts
import { useQueryClient } from "@tanstack/react-query";

const queryClient = useQueryClient();
const createManagerAndGetAddress = useCreateManagerAndGetAddress(/* options */);

createManagerAndGetAddress.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 2.0: