useAccessMerkleClaimAmount
Submits a transaction. Previews the outstanding amount for a proof-bearing Merkle entry as an encrypted handle.
@tokenops/sdk/fhe-airdrop/react{ mutate, mutateAsync, isPending, error, data }Description
Submits a transaction. Previews the outstanding amount for a proof-bearing Merkle
entry as an encrypted handle. Pass data.handle to the Zama relayer's userDecrypt.
entry.account selects the leaf. A leaf someone else already settled previews as an
encrypted zero; see MerkleClaimArgs.entry.
`entry.account` is the only party that can decrypt the result, not the submitter.
The contract grants the outstanding handle with _outstandingOf(account, account, …),
so a third-party submitter gets back a valid handle it learns nothing from - never
offer it a userDecrypt action. This is the opposite of
useAccessEcdsaClaimAmount, whose preview is ACL'd to msg.sender.
Invalidates: nothing. The preview consumes no accounting and no per-leaf state, so no cached read changes value - the same entry still pays the same amount afterwards.
Signature
function useAccessMerkleClaimAmount(options: AirdropInstanceClientOptions): UseMutationResult<EncryptedViewResult, Error, GetClaimAmountArgs>;Parameters
Shape of the object you pass to .mutate(args) is the SDK type GetClaimAmountArgs. Inspect the type for the full shape (discriminated unions collapse to a tagged variant at call time).
Example
const preview = useAccessMerkleClaimAmount({ address: airdropAddress });
const { handle } = await preview.mutateAsync({ entry });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 accessMerkleClaimAmount = useAccessMerkleClaimAmount(/* options */);
accessMerkleClaimAmount.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:
useDiscloseHandleToPartyGrant ACL on a single ciphertext handle to a third party (e.g. an auditor).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.