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.

IntrospectionuseMutation

useSetMerkleImplementation

Point future createMerkleAirdrop* calls at a new Merkle implementation.

Import

@tokenops/sdk/fhe-airdrop/advanced/react

Return

{ mutate, mutateAsync, isPending, error, data }

Lifecycle

Introspection

Description

Point future createMerkleAirdrop* calls at a new Merkle implementation.

Requires IMPL_MANAGER_ROLE. Deployed instances are untouched.

Same prediction-drift hazard as `useSetEcdsaImplementation`, with a worse blast radius. Merkle campaigns are commonly immutable-root: a plan whose entries were bound to an address predicted before this write has no on-chain repair, so re-plan rather than re-point.

Invalidates: useFactoryImplementations (fn "implementations"), plus the fn "getMerkleInitCodeHash", "predictMerkleAirdropAddress" and `preflightCreate` PREFIXES - every cached args combination of each.

Signature

@tokenops/sdk/fhe-airdrop/advanced/react

function useSetMerkleImplementation(options?: AirdropClientOptions): UseMutationResult<Hex, Error, SetMerkleImplementationArgs>;

Parameters

Shape of the object you pass to .mutate(args) is the SDK type SetMerkleImplementationArgs. 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 12 ready presets across vesting / airdrop / disperse / faucet — deploy a manager, create a vesting, claim, and run the product equivalents. The deep-link above auto-selects the closest preset to useSetMerkleImplementation; pick another from the dropdown if you'd rather start there.

Example

@tokenops/sdk/fhe-airdrop/advanced/react · @example

tsx

const setMerkleImpl = useSetMerkleImplementation();
await setMerkleImpl.mutateAsync({ implementation: newMerkleImpl });

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 Airdrop v2 › 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 setMerkleImplementation = useSetMerkleImplementation(/* options */);

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