useDiscloseHandleToParty
Grant ACL on a single ciphertext handle to a third party (e.g. an auditor).
@tokenops/sdk/fhe-airdrop/react{ mutate, mutateAsync, isPending, error, data }Description
Grants party decrypt access to a handle you already hold - typically one
returned by useAdminGetCurrentBalance or a claim preview, forwarded to an
auditor without ever revealing plaintext.
Unlike the admin*Disclose* hooks this produces no new handle, so it
returns the transaction hash rather than an EncryptedViewResult; there is
no ACL event to parse.
Two gates apply on-chain: the handle must be persistently user-decryptable by
the caller in this instance's context (a transient allowance from a fresh FHE op
does not count; DISCLOSURE_ADMIN_ROLE bypasses this gate), and the *instance*
must be allowed on it, so a handle minted by an unrelated contract cannot be laundered through
this campaign. A failure of the first surfaces as FheHandleNotAllowedError.
Invalidates: nothing. ACL is append-only and no read hook in this subpath caches who is allowed on a handle.
Signature
function useDiscloseHandleToParty(options: AirdropInstanceClientOptions): UseMutationResult<Hex, Error, DiscloseHandleToPartyArgs>;Parameters
Shape of the object you pass to .mutate(args) is the SDK type DiscloseHandleToPartyArgs. Inspect the type for the full shape (discriminated unions collapse to a tagged variant at call time).
Example
const disclose = useDiscloseHandleToParty({ address: airdropAddress });
await disclose.mutateAsync({ handle, party: auditorAddress });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).
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-airdrop"],
});
},
});See also
Other Encrypted read hooks in airdrop v2:
useAdminBatchDiscloseBalanceToPartiesSubmits a transaction. Discloses the instance's confidential pool balance to several parties at once.useAdminDiscloseBalanceToPartySubmits a transaction. Discloses the instance's confidential pool balance to party.useAdminGetCurrentBalanceSubmits a transaction. Reads the instance's remaining confidential pool balance as an euint64 handle the caller may decrypt - pass data.handle to the Zama relayer's userDecrypt.useRefreshComplianceBalanceSubmits a transaction. Re-grants the compliance-manager clone on the instance's current pool balance and returns the handle it was granted on.