useTransferFeeCollectorRole
Transfer the FEE_COLLECTOR_ROLE to newCollector.
@tokenops/sdk/fhe-vesting/react{ mutate, mutateAsync, isPending, error, data }Description
Transfer the FEE_COLLECTOR_ROLE to newCollector. The current
fee-collector calls this; the new collector gains immediate role membership.
Signature
function useTransferFeeCollectorRole(options: ManagerHookOptions): UseMutationResult<Hex, Error, UseTransferFeeCollectorRoleArgs>;Parameters
Shape of the object you pass to .mutate(args).
| Property | Type | Description |
|---|---|---|
| newCollectorrequired | Address | |
| account | Account | Address |
Example
"use client";
import { useTransferFeeCollectorRole } from "@tokenops/sdk/fhe-vesting/react";
export function Example() {
const { mutate, isPending } = useTransferFeeCollectorRole();
return (
<button disabled={isPending} onClick={() => mutate(/* args */)}>
{isPending ? "Sending…" : "TransferFeeCollectorRole"}
</button>
);
}Auto-generated from the hook's shape (the SDK doesn't carry a TSDoc @example here yet).
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 Vesting › 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 transferFeeCollectorRole = useTransferFeeCollectorRole(/* options */);
transferFeeCollectorRole.mutate(args, {
onSuccess() {
// Coarse invalidation: refresh every cached read on this product surface.
queryClient.invalidateQueries({
queryKey: ["tokenops-sdk", "fhe-vesting"],
});
},
});See also
Other Roles · RBAC hooks in vesting:
useHasRoleRead AccessControl: is account a member of role on this manager? The role hashes are stable across deployments — see useRoleConstants if you need to look them up dynamically.useGrantRoleAccessControl: grant role to accountTarget.useRevokeRoleAccessControl: revoke role from accountTarget.useRenounceRoleAccessControl: renounce role from msg.sender.