Disclose · ACLuseMutation Curated

useDiscloseHandleToParty

Grant ACL on a single ciphertext handle to a third party (e.g. an auditor).

Import

@tokenops/sdk/fhe-disperse/react

Return

{ mutate, mutateAsync, isPending, error, data }

Lifecycle

Disclose · ACL

Description

Grant party persistent FHE ACL on a single handle. Caller must already hold ACL on the handle; FHEVM ACL is append-only — the grant cannot be revoked once committed.

Common use: a fee-collector who decrypted the reserve handle via useGetEncryptedFeeReserve wants to delegate ongoing decrypt access to a downstream accounting service.

Returns { hash, discloser, party, disclosedHandles } parsed from the HandlesDisclosedToParty event.

Signature

@tokenops/sdk/fhe-disperse/react

function useDiscloseHandleToParty(options?: DisperseHookOptions): UseMutationResult<DisclosureResult, Error, DiscloseHandleArgs>;

Parameters

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

Example

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

tsx

const disclose = useDiscloseHandleToParty();
disclose.mutate({ handle, 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 viem-passthrough errors. Product classes carry the offending value as fields — render them inline instead of a generic "transaction failed." See Disperse › 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 discloseHandleToParty = useDiscloseHandleToParty(/* options */);

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