Token Eligibility Rule

Overview

Token Eligibility Rule is a condition that determines whether an address, person, institution, jurisdiction, asset, or transaction may participate in a token lifecycle action. Rules can cover holding, transfer, minting, redemption, staking, voting, or access to distributions. For token integrations, the relevant rule can exist in smart-contract code, an upgradeable module, an issuer policy, or an off-chain compliance service. Systems should therefore inspect both the deployed implementation and the current administrative configuration instead of relying on a token name or interface label.

It is the logical criterion, while an allowlist or denylist is one possible data structure used to implement the criterion. It should be read alongside Token Allowlist, Token Geographic Restriction, and Token Holding Restriction. These related concepts describe different parts of the lifecycle, so substituting one label for another can hide who has authority, which balance is measured, or what action is actually permitted.

Operationally, rules should specify data inputs, evaluation time, responsible authority, privacy handling, expiration, override, appeal, and behavior when an external identity or compliance service is unavailable. A production system should preserve the applicable network, contract or asset identifier, units and precision, rule version, responsible role, effective timestamp, and the transaction or source record used to make the decision. Changes should be observable and reconciled rather than inferred from a wallet display alone.

The principal risks are that incorrect, inconsistent, or non-transparent rules can create discriminatory outcomes, failed settlement, regulatory exposure, and composability failures. Teams should test normal and exceptional paths, including failed transactions, delayed external services, upgrades, role changes, unavailable redemption or transfer routes, and inconsistent data between blockchain, market, legal, and accounting systems.