BOB / WBNB Pool On-Chain Check

Pancake LPs · BSC · 0x3c79593e01a7f7fed5d0735b16621e2d52a6bc58
This is a liquidity pool, not a token. It is the PancakeSwap V2 pool for BOB / WBNB — the address DEX sites show as “Pair”. Liquidity locked: 100% burned. The check below reads the pool’s own contract; to check the coin you would buy, use its own address.
Check BOB →
12 / 12 On-chain Check
Checked 14 Nov 2026. On-chain Check, 12 of the 100-point ChainSift Score — what it covers. Holder distribution is not scored for a pool: its shares always sit with a few liquidity providers or a locker.

Evidence

Risk factorFindingEvidenceDate
Sellable Yes Transfer simulation 14 Nov 2026
Buy tax 0% Contract 14 Nov 2026
Sell tax 0% Contract 14 Nov 2026
Admin mint No — only pool shares for added liquidity Pool contract 14 Nov 2026
Transfers pausable Not present Contract 14 Nov 2026
Address blacklist Not present Contract 14 Nov 2026
Upgradeable proxy No Contract 14 Nov 2026
Source verified Yes Block explorer 14 Nov 2026
Liquidity locked 100% burned LP holders 14 Nov 2026
Holders 21 Token contract 14 Nov 2026

This contract — Cake-LP

Deployed by0xd8b1c9…6e515f
Current owner0xca143c…350c73 — PancakeSwap V2 factory that created the pool
Holders21

Largest holders

RankAddressShare
#1 · burned 0x000000…00dead 99.96%
#2 0x287752…c20d39 0.03%
#3 · contract 0x55e95a…703704 0.02%
#4 0xc57faf…f9e553 0.00%
#5 0xf6538a…9523c2 0.00%

What this means

This address is a PancakeSwap V2 liquidity pool contract for the BOB/WBNB pair, not a standard token that someone buys to hold. This matters because the automated check's findings describe the pool mechanics itself, and the "holders" figure refers to liquidity providers who deposited into the pool, not holders of a tradeable token. On the date of this check, no mechanism was detected that would let an admin mint new pool shares out of thin air — minting here only happens when someone adds liquidity, which is the normal, expected behaviour of a PancakeSwap pool. No pausable transfer function, no address blacklist, and no upgradeable proxy pattern were detected, meaning there is no on-chain switch found that would let a privileged address freeze the pool or redirect its logic after the fact. The contract source is verified on the block explorer, so the code matches what is publicly visible and was readable for this automated scan. The liquidity recorded against this pool shows as 100% burned, meaning the LP tokens representing claim on the pooled assets were sent to a dead address rather than held by a wallet that could withdraw the underlying BOB and WBNB at will.

None of this tells you anything about the BOB token itself — its tax behaviour, mint permissions, or owner privileges are a separate contract and would need their own check. It also says nothing about who is behind the project, how tokens were distributed before this pool was created, whether there are vesting schedules, marketing claims, or any legal entity standing behind it. Automated contract-mechanics checks like this one cannot assess intent, team reputation, or whether promotional material matches on-chain reality. A clean mechanical read of a pool contract does not speak to the terms, risks, or wisdom of acquiring BOB, WBNB, or LP shares in this pair.

If you're assessing BOB itself, run the token contract address — not this pool address — through the same kind of check, and look specifically at its mint, tax, pause and blacklist functions. Separately, look up who holds BOB's admin or owner keys and whether those permissions have been renounced, check the token's holder distribution for concentration in a few wallets, and look for any independent audit of the token contract rather than just the pool. Cross-check the liquidity lock claim directly on the block explorer or lock-service page rather than relying on a single tool's summary, and treat any project communications about team identity, roadmap, or guaranteed returns as separate claims that this type of contract scan cannot verify one way or the other.

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