| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 9 Sept 2026 |
| Buy tax | 0% | Contract | 9 Sept 2026 |
| Sell tax | 0% | Contract | 9 Sept 2026 |
| Admin mint | Not present | Contract | 9 Sept 2026 |
| Transfers pausable | Not present | Contract | 9 Sept 2026 |
| Address blacklist | Not present | Contract | 9 Sept 2026 |
| Upgradeable proxy | No | Contract | 9 Sept 2026 |
| Source verified | Yes | Block explorer | 9 Sept 2026 |
| Top-10 holders | 34.1% | Holder distribution | 9 Sept 2026 |
| Liquidity locked | No | LP holders | 9 Sept 2026 |
| Holders | 8190 | Token contract | 9 Sept 2026 |
| Deployed by | 0x51389f…cb6ab7 |
| Current owner | None — ownership renounced |
| Holders | 8,190 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x73d8bd…4946db | 17.35% |
| #2 | 0x8743d3…335893 | 2.54% |
| #3 | 0xddeb5d…b09881 | 2.41% |
| #4 | 0x4f945b…d2c5d8 | 2.05% |
| #5 | 0x9793a9…a8dcee | 2.03% |
This automated check of FLORK on BSC returned 17 out of 18, with a transfer simulation showing the token can be sold, and no buy or sell tax detected at the time of the check. No admin minting function, no transfer-pausing mechanism, no address blacklist capability, and no upgradeable proxy pattern were found in the contract code. In practice, this means the contract owner does not currently appear to hold the ability to mint new tokens at will, freeze wallets, block specific addresses from trading, or swap out the contract's logic after deployment. The source code is also verified on the block explorer, meaning it can be read and checked by anyone rather than existing only as opaque bytecode.
Two findings deserve closer attention. Top-10 holders control 34.1% of supply, which is a meaningful concentration — if a small number of wallets decide to sell at the same time, it can move the price sharply regardless of how the contract itself behaves. Separately, liquidity is not locked, meaning whoever supplied the trading pool on the decentralised exchange retains the technical ability to withdraw it. This does not mean withdrawal will happen, only that the contract and pool configuration do not prevent it, and no time-locked or burned liquidity was detected on the date of this check.
It's worth being clear about what this check does not cover. It reads contract mechanics and on-chain data only — things like tax rates, mint functions, pause switches, and holder distribution. It says nothing about who the team behind FLORK is, whether they are anonymous, what their track record might be, how the token's supply and incentives are structured long-term, or whether any legal or regulatory claims made about the project hold up. Intent cannot be inferred from bytecode: a contract can look clean today and still be attached to a project with weak fundamentals, poor communication, or plans that change without notice.
Before considering any transaction, it would be reasonable to look at the liquidity pool directly on-chain to see who controls it and whether a lock exists elsewhere that this check didn't pick up, to review the top-10 holder wallets individually for signs of a single controlling entity, and to search for any independent commentary, audits, or team disclosures tied to this specific contract address. Checking whether the BSC explorer shows recent contract changes or renounced ownership can also add useful context. None of this substitutes for independent judgement, and this summary is not investment advice.
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 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.