| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| 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 |
| Deployed by | 0xd8b1c9…6e515f |
| Current owner | 0xca143c…350c73 — PancakeSwap V2 factory that created the pool |
| Holders | 21 |
| Rank | Address | Share |
|---|---|---|
| #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% |
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.
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 checked 12 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.