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.

Disclose · ACLuseMutation Curated

useBatchDiscloseHandlesToParty

Batch ACL grant across many handles in one tx.

Import

@tokenops/sdk/fhe-disperse/react

Return

{ mutate, mutateAsync, isPending, error, data }

Lifecycle

Disclose · ACL

Description

Batch variant of useDiscloseHandleToParty — atomically grant party persistent ACL on all handles. Reverts on the first handle that fails caller-ACL or contract-ACL checks.

Returns { hash, discloser, party, disclosedHandles } parsed from the HandlesDisclosedToParty event. With waitForReceipt: false (a Safe / multisig signer) it resolves on submission to a PendingDisclosureResult.

Signature

@tokenops/sdk/fhe-disperse/react

function useBatchDiscloseHandlesToParty(options?: DisperseHookOptions): UseMutationResult<DisclosureResult | PendingDisclosureResult, Error, BatchDiscloseHandlesArgs & ReceiptMode>;

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 useBatchDiscloseHandlesToParty; pick another from the dropdown if you'd rather start there.

Example

@tokenops/sdk/fhe-disperse/react · @example

tsx

const batchDisclose = useBatchDiscloseHandlesToParty();
batchDisclose.mutate({ handles, party: accountingAddress });

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 Disperse 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

import { useQueryClient } from "@tanstack/react-query";

const queryClient = useQueryClient();
const batchDiscloseHandlesToParty = useBatchDiscloseHandlesToParty(/* options */);

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

Description

Signature

Example

Errors

Invalidation recipe

See also