useAirdropRenounceRole
Give up a role on an airdrop instance yourself.
@tokenops/sdk/fhe-airdrop/react{ mutate, mutateAsync, isPending, error, data }Description
Give up a role on an airdrop instance yourself.
Self-only by construction: the contract's renounceRole(role, callerConfirmation)
reverts AccessControlBadConfirmation unless the confirmation is the sender,
so there is no holder to pass - the headless client fills it from the
resolved sending account. To remove a role from somebody else use
useAirdropRevokeRole.
Renouncing runs the same on-chain floors as a revoke, so it is not an escape
hatch from them: the sole remaining DEFAULT_ADMIN_ROLE holder cannot
renounce (LastAdmin). Grant a successor first.
Invalidates: every useAirdropHasRole entry for this instance (prefix,
all role/holder pairs), plus its useAirdropRoleMembers entry for role.
The prefix is deliberate - the holder here is whichever account the wallet
client resolves at submit time, which need not match any (role, holder)
pair a component happens to have cached, and a narrower key would invalidate
nothing while throwing nothing. Still scoped to this instance.
Signature
function useAirdropRenounceRole(options: AirdropInstanceClientOptions): UseMutationResult<Hex, Error, AirdropRenounceRoleArgs>;Parameters
Shape of the object you pass to .mutate(args) is the SDK type AirdropRenounceRoleArgs. Inspect the type for the full shape (discriminated unions collapse to a tagged variant at call time).
Example
const renounce = useAirdropRenounceRole({ address: airdropAddress });
await renounce.mutateAsync({ role: roles.DEFAULT_ADMIN_ROLE });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 airdropRenounceRole = useAirdropRenounceRole(/* options */);
airdropRenounceRole.mutate(args, {
onSuccess() {
// Coarse invalidation: refresh every cached read on this product surface.
queryClient.invalidateQueries({
queryKey: ["tokenops-sdk", "fhe-airdrop"],
});
},
});See also
Other Roles · RBAC hooks in airdrop v2: