Contracts flagged by an "AI rug pull checker" often focus on structural patterns that enable asymmetric transaction permissions, such as honeypot mechanisms. A central pattern is the presence of require() statements in transfer functions that revert sell transactions for non-whitelisted addresses, allowing buys to succeed while blocking sells. This creates a mechanical barrier preventing token holders from exiting positions, despite normal-looking price activity. The pattern is detectable through static contract analysis without executing trades, as it relies on explicit permission checks embedded in the code. Its significance lies in the direct control over liquidity flow, which can trap investors by design.
This pattern becomes risk-relevant primarily when the whitelist or permission list controlling sell access is owner-modifiable after launch, enabling dynamic restriction of exit liquidity. If the contract allows the owner to add or remove addresses from the whitelist arbitrarily, it maintains an exit-block capability that can be activated post-launch. Conversely, if the whitelist is fixed and immutable, or if the contract owner lacks the ability to alter permissions, the pattern may be benign, serving compliance or anti-bot functions. The presence of such a whitelist alone does not confirm malicious intent but signals a structural capability that can be weaponized.
Additional signals that would shift the risk assessment include the presence of owner-controlled adjustable sell tax parameters, which can be raised post-launch to levels that effectively block selling without reverting transactions outright. Detection of upgradeable proxy patterns without timelocks or multisig requirements would also increase risk, as the contract logic could be replaced to introduce or remove such restrictions. Conversely, explicit renouncement of owner privileges over whitelist modification, tax parameters, or upgradeability would reduce concern. Observing on-chain evidence of whitelist changes or tax hikes post-launch would further confirm risk, but absence of these does not guarantee safety.
When this whitelist-based sell restriction pattern combines with other common conditions, outcomes can range from temporary liquidity control to full exit blockage. For example, coupling a whitelist-only exit with an active freeze authority on token transfers can enable selective freezing of wallets, compounding exit difficulty. Similarly, if paired with active mint authority, the owner could dilute holders while preventing their exit, amplifying financial harm. However, if combined with transparent governance mechanisms and immutable restrictions, these patterns can coexist with legitimate operational needs. The realistic risk spectrum thus depends heavily on the interplay of these contract features and the transparency of their governance.