WEBFOUR On-Chain Risk Check

WEBFOUR · BSC · 0xd3987cb8a59e8ef6aab0d95b92254344ed9c3c6f
8 / 18 On-chain Check
Checked 29 Oct 2026. On-chain Check, 18 of the 100-point ChainSift Score — what it covers.

Evidence

Risk factorFindingEvidenceDate
Sellable Yes Transfer simulation 29 Oct 2026
Buy tax 11% Contract 29 Oct 2026
Sell tax 9.2% Contract 29 Oct 2026
Admin mint Not present Contract 29 Oct 2026
Transfers pausable Enabled Contract 29 Oct 2026
Address blacklist Enabled Contract 29 Oct 2026
Upgradeable proxy No Contract 29 Oct 2026
Source verified Yes Block explorer 29 Oct 2026
Top-10 holders 74.8% Holder distribution 29 Oct 2026
Liquidity locked 92% burned LP holders 29 Oct 2026
Holders 10242 Token contract 29 Oct 2026

This contract — WEBFOUR

Deployed by0x4f0cef…ca975b
Current owner0x4f0cef…ca975b
Holders10,242

Largest holders

RankAddressShare
#1 · PancakeV2 · contract 0xd34485…af0e9d 60.60%
#2 · burned 0x000000…00dead 7.04%
#3 0x0cc0c5…f9b588 2.62%
#4 0xa488f4…7e5fc7 0.99%
#5 0x282c9d…71d9ea 0.82%

What this means

This automated check scored WEBFOUR 8 out of 18 on contract mechanics alone. A few things stand out. The contract charges a transfer tax of up to 11%, meaning every time tokens are bought or sold a cut is taken, which eats into returns regardless of price movement. The contract also allows the owner to pause transfers entirely, which means holders could, at the owner's discretion, be temporarily unable to move or sell their tokens. On top of that, the contract supports blacklisting specific addresses, which would let the owner block individual wallets from transacting. None of these behaviours were triggered during this check — a test transfer simulation showed the token was sellable at the time of testing — but the capability to pause transfers and blacklist addresses exists in the code and could be used at any point by whoever controls the contract. Holder concentration is also high, with the top 10 wallets holding 74.8% of total supply, meaning a small number of holders could influence the market by moving large amounts at once. On the more reassuring side, no admin minting function was found, the contract is not an upgradeable proxy, the source code is verified on the block explorer, and 92% of liquidity has been burned, which reduces (but does not eliminate) the risk of liquidity being pulled.

It's worth being clear about what this check does not do. It reads only the mechanics written into the smart contract — what the code technically allows the owner to do. It says nothing about who the team behind WEBFOUR is, whether their stated plans or roadmap are credible, how the token's supply and incentives are structured long-term, or whether there is any legal entity standing behind the project. A contract can look clean on paper while still being tied to a team with no track record, and conversely, mechanics like pausing or blacklisting exist in many legitimate projects for reasons such as regulatory compliance or security response. This check cannot tell you intent.

Before putting money in, it would be worth looking into who operates the project and whether they're identifiable, checking community channels and any independent discussion of the token for red flags, reviewing whether the owner's pause and blacklist privileges are explained anywhere officially, and confirming current liquidity and holder data directly on the block explorer, since on-chain conditions can change after this check was run.

Team, tokenomics and legal structure are not assessed here — that is the other 82 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 18 points out of 100.

The other 82 are where money is usually lost: who the team is, where the tokens sit, what the documents actually say, and what the project chose not to put on its front page.

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 29 Oct 2026. A check describes a contract on the date shown; contracts can be changed afterwards.