Poocoin Rug Check for tracing developer wallet activity

The selected contract determines the ownership trail

The token contract that you select sets the context for the ownership history that Rug Check is designed to follow. The displayed token identity and contract address should describe the same asset. An unrelated contract produces an unrelated ownership trail, even when its token name matches. Automatic owner detection identifies a relationship with that contract; it does not identify everyone behind the project.

Contract ownership is an administrative relationship defined by the token's code, and the owner need not be the deployer or the largest holder. Ownership of liquidity tokens is a separate relationship. These roles can overlap, yet each relationship needs its own support. A holder ranking therefore cannot substitute for ownership history.

Ownership changes and asset transfers answer different questions

The Dev Activity log combines administrative changes with asset movements, so the action type determines what each entry actually establishes.

Ownership transfers

The owner's role concerns permissions on the contract; transferring it does not transfer balances that the previous owner holds. Former-owner transactions may therefore remain economically relevant after control changes. An address that receives assets also does not become the contract owner merely through that receipt.

Open full-size image

Transfers and trades

A token transfer moves a quantity between addresses, while a sale exchanges assets through a market. Those actions have different meanings, even when both reduce the sender's balance. Trading activity needs the associated exchange and asset flows to support a buy or sell interpretation. A transfer may relocate custody without creating a market trade.

BNB is another asset in the wallet log. Its movement must be read separately from the token's transfer amounts.

A blockchain transaction can contain several contract calls and token transfers, with an outer recipient that coordinates the operation. Asset recipients appear in the individual transfer records, which can differ from that outer address. Following those records explains where assets moved within a complex transaction.

LP-token movement changes who holds a pool claim

In pools that issue transferable LP tokens, a transfer changes who holds the pool claim without itself withdrawing pool assets.

Transfers of LP tokens

In a fungible LP-token pool, those tokens represent a provider's proportional share of the pool. They are distinct from the token that traders buy and sell, and moving them changes custody of the pool share. The underlying reserves remain in the pool until an operation moves them. Sending the project token elsewhere does not automatically transfer the sender's LP position, even when both assets belong to the same account.

The LP-token contract identifies the specific pool claim, while the token's other pools have separate positions.

Withdrawals and locked shares

A withdrawal redeems LP tokens for underlying pool assets under the pool's rules, with asset flows that return reserves from that pool. A contract address holding LP tokens does not, by itself, prove that those shares are locked. Locking depends on the receiving contract's withdrawal conditions, the quantity covered, and the applicable unlock time. A wallet transfer and a deposit into a lock contract can look similar at the transfer-event level.

Burning LP tokens during redemption releases the represented pool assets, while sending them to an inaccessible address leaves that share unredeemed. This LP-token interpretation does not automatically apply to pools whose positions use another representation.

Historical recipients reveal distributions that balances can hide

The Top receivers view supplements current holder balances with historical receipts, including tokens that a recipient later forwarded. A transfer from an owner-linked address establishes delivery to the recipient, not that both addresses share a controller. Supply percentages also require the correct denominator. A percentage of reported total supply can differ from a percentage of accessible supply when tokens are genuinely inaccessible.

Does renounced ownership prevent a liquidity rug?

Renounced ownership alone does not prevent a liquidity rug, because token administration and ownership of pool assets are separate relationships. In a conventional single-owner contract, renunciation disables functions that require the owner. The contract's code defines which functions those are. Separate roles or upgrade permissions can remain when the implementation includes them. Relinquishing one permission does not establish that every administrative path disappeared.

LP tokens remain assets with their own holders and withdrawal conditions. Renouncing ownership of the traded token does not itself burn, lock, or transfer those LP tokens. A former owner holding an accessible LP balance can retain the corresponding withdrawal capability under the pool's rules. Conversely, a genuine lock applies only to the shares that it holds and the period that its contract enforces.