perception On-Chain Risk Check

PUBLIC PERCEPTION · BSC · 0x30393497cb2b9c58b8cfe907b30eec683999762d
9 / 12 On-chain Check
Checked 21 Nov 2026. On-chain Check, 12 of the 100-point ChainSift Score — what it covers. Holder distribution was unavailable for this contract, so that signal is excluded from the total.

Free above: contract permissions, sell test and tax when data is available.

Paid report: pool balances, trading activity, large holders and estimated price impact for supported pools.

Evidence

Risk factorFindingEvidenceDate
Sellable Yes Transfer simulation 21 Nov 2026
Buy tax 2% Contract 21 Nov 2026
Sell tax 2% Contract 21 Nov 2026
Admin mint Not present Contract 21 Nov 2026
Transfers pausable Enabled Contract 21 Nov 2026
Address blacklist Enabled Contract 21 Nov 2026
Upgradeable proxy No Contract 21 Nov 2026
Source verified Yes Block explorer 21 Nov 2026
Liquidity locked No LP holders 21 Nov 2026
Holders 0 Token contract 21 Nov 2026

This contract — perception

Deployed by0xc6a51b…307773
Current owner0xc6a51b…307773

What this means

This automated check on PUBLIC PERCEPTION (PUBLIC PERCEPTION, BSC) scored 9 out of 12, with sell transactions working normally in simulation at the time of the check and no admin minting function or upgradeable proxy detected. Several findings are still worth understanding before deciding anything. A transfer tax of up to 2% on both buying and selling means a small percentage of every transaction is deducted automatically — this is a cost, not a security issue on its own. More significant is that transfers can be paused by the owner: this means a wallet with admin rights could, in principle, freeze all movement of the token, including sales, at any time. The contract also supports blacklisting specific addresses, which would let the owner block individual wallets from transacting, again including selling. Neither of these has necessarily been used, but the capability exists in the code as written at the time of this check. On a positive note, the contract source is verified on the block explorer, meaning the code is publicly readable rather than hidden. Liquidity is not locked, which means whoever controls the liquidity pool could withdraw it, and holder count is reported as zero, which is unusual and worth treating as a gap in the data rather than a confirmed absence of holders.

It's important to be clear about what this check does not cover. This is an automated read of the contract's mechanics only — things like pause functions, blacklist capability, tax rates and liquidity lock status. It says nothing about who is behind the project, how tokens are distributed, whether there are vesting schedules or large wallets ready to sell, what claims the team has made, or whether any of this fits together into a plan that benefits or disadvantages buyers. Intent, team reputation and legal structure are outside the scope of a contract-mechanics scan.

Before putting money into this token, it would be worth looking at who holds the liquidity and whether it can be withdrawn unilaterally, checking the distribution of tokens across wallets to see if a small number of addresses control a large share, searching for any history of the pause or blacklist functions being exercised, and trying to verify who the team is and what, if anything, they've publicly committed to regarding liquidity locks or renouncing admin control. Cross-referencing the contract address on multiple independent explorers and community discussions may also surface information this automated check cannot.

Team, tokenomics and legal structure are not assessed here — that is the other 88 points of the ChainSift Score. How this check works and what it misses.

Watch this contract

Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.

We send one confirmation message and nothing else until something changes.

We checked 12 points out of 100.

A deep check also reviews the project's public materials, team, tokenomics and disclosures.

Related guides

Contract data read from GoPlus Security and the BSC block explorer. Scores are calculated by fixed rules from that data — no language model decides them. Last updated 21 Nov 2026. A check describes a contract on the date shown; contracts can be changed afterwards.