| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No data | Transfer simulation | 13 Oct 2026 |
| Buy tax | 0% | Contract | 13 Oct 2026 |
| Sell tax | 0% | Contract | 13 Oct 2026 |
| Admin mint | No data | Contract | 13 Oct 2026 |
| Transfers pausable | No data | Contract | 13 Oct 2026 |
| Address blacklist | No data | Contract | 13 Oct 2026 |
| Upgradeable proxy | No data | Contract | 13 Oct 2026 |
| Source verified | No | Block explorer | 13 Oct 2026 |
| Top-10 holders | 98.1% | Holder distribution | 13 Oct 2026 |
| Liquidity locked | 100% burned | LP holders | 13 Oct 2026 |
| Holders | 596 | Token contract | 13 Oct 2026 |
| Deployed by | 0xab65c9…7ed7c7 |
| Holders | 596 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0xab65c9…7ed7c7 | 80.11% |
| #2 | 0x1e10d6…fa936a | 8.38% |
| #3 | 0x73038a…490cf6 | 3.41% |
| #4 | 0xc75c07…4febb2 | 2.45% |
| #5 | 0x759f26…bfffc1 | 0.94% |
This automated check scored ROBO 0 out of 10 on BNB Chain, which signals that the indicators available on the date of the check were largely unfavourable or simply unavailable. Because the contract's source code is not verified, the system could not read the actual logic behind the token — it only has the compiled bytecode to go on, which means standard risk functions (whether the owner can mint new tokens, pause transfers, blacklist addresses, or sell tokens through a simulated transfer) could not be scored and are reported as "no data" rather than "clear." This is an important distinction: unscored does not mean safe, it means unknown. What is known is that the top 10 holders control 98.1% of the supply, which means a very small number of wallets could sell in a way that significantly affects the token's available liquidity and price, regardless of what the contract code permits. On a more favourable note, the liquidity pool shows as 100% burned, meaning the tokens originally paired with BNB in the liquidity pool have been sent to an address with no known private key, which reduces (but does not eliminate) one common method of a rug pull where liquidity is withdrawn by the deployer.
What this check does not and cannot tell you is anything about who is behind ROBO, their intentions, their track record, or whether the project has any real product, partnerships, or roadmap. It does not assess tokenomics design, marketing claims, social media activity, or legal structure. This is a mechanical read of on-chain data and contract behaviour only — it says nothing about the humans running the project, and no person has reviewed this token; the entire assessment is generated automatically from blockchain data sources.
Given the unverified source code and the unscored admin functions, a concrete next step would be to look up the contract on a block explorer such as BscScan and check whether the source has since been verified, since verification allows anyone to read the actual mint, pause, and blacklist logic rather than relying on bytecode alone. It would also be worth examining the top-holder wallets individually to see whether any are known exchange, burn, or locked-liquidity addresses rather than individual holders, since that materially changes what 98.1% concentration implies. Finally, checking whether the contract owner still holds any special privileges (for example, by looking at the contract's "owner" or "admin" address and whether it has renounced ownership) would clarify whether anyone retains the technical ability to alter the contract's behaviour after launch.
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 10 points out of 100.
The other 90 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.