Databases cataloging rug pull incidents typically aggregate structural contract patterns known to enable exit scams, such as owner-controlled minting, blacklist functions, or whitelist-only sell restrictions. These patterns mechanically allow a privileged actor to restrict liquidity or inflate supply, which can trap investors or devalue tokens. The database functions as a reference to identify tokens exhibiting these contract capabilities without requiring trade execution. It is important to note that the database records structural potential rather than confirmed exploit events, meaning the presence of a pattern signals capability but not necessarily malicious use.
Risk relevance hinges on whether the contract’s privileged functions are actively modifiable and whether the token’s liquidity context amplifies the impact of these functions. For example, an owner-controlled sell tax that can be raised post-launch poses a higher risk if the owner retains this authority indefinitely, as it can effectively block selling or impose punitive fees. Conversely, some projects retain similar controls for legitimate operational reasons, such as regulatory compliance or staged token releases, which can render these patterns benign if transparently communicated and time-limited. The database alone cannot distinguish intent or operational context, so risk must be inferred cautiously.
Additional signals that would shift the risk assessment include on-chain evidence of function use, such as recorded blacklist additions or sudden mint transactions, which would confirm exploitation or at least active control. Conversely, verified renouncement of mint or freeze authorities, or immutable contract deployment without upgrade proxies, would reduce the risk profile by removing exit-block or supply-inflation capabilities. Observing the token’s liquidity pool depth and trading volume alongside these contract features also matters; deep, active pools can mitigate the impact of restrictive functions by enabling easier exit for holders.
When combined with thin liquidity pools and low market capitalization, the presence of these contract patterns can produce severe outcomes, including rapid price crashes triggered by forced exits or sudden supply inflation. Even small sell orders may cascade into large price moves that are difficult to trade through, exacerbating losses for holders. However, in tokens with robust liquidity and transparent governance, the same patterns may never materialize as exploit events. Thus, the database’s utility lies in flagging structural risk potentials that warrant further contextual analysis rather than serving as definitive proof of imminent rug pulls.