| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 21 Nov 2026 |
| Buy tax | 0% | Contract | 21 Nov 2026 |
| Sell tax | No data | Contract | 21 Nov 2026 |
| Admin mint | No data | Contract | 21 Nov 2026 |
| Transfers pausable | No data | Contract | 21 Nov 2026 |
| Address blacklist | No data | Contract | 21 Nov 2026 |
| Upgradeable proxy | No data | Contract | 21 Nov 2026 |
| Source verified | No | Block explorer | 21 Nov 2026 |
| Top-10 holders | 60.7% | Holder distribution | 21 Nov 2026 |
| Liquidity locked | No | LP holders | 21 Nov 2026 |
| Holders | 377 | Token contract | 21 Nov 2026 |
| Deployed by | 0x2f3199…47b5df |
| Holders | 377 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xadc408…16aadc | 45.01% |
| #2 · contract | 0x2f3199…47b5df | 9.91% |
| #3 | 0x32d5c2…c45597 | 1.05% |
| #4 | 0x214b6c…cf6a6d | 1.02% |
| #5 | 0x0ce1b7…0dbda7 | 0.89% |
This automated check simulated a sale of LETA on BSC and found that selling is blocked by the contract — this is what's commonly called a honeypot pattern. In practice, this means an automated test transaction was unable to sell the token back once bought, regardless of the price or market conditions at the time. The contract's source code is not verified on the block explorer, so the check is reading only the deployed bytecode, which limits how much can be confirmed about functions like minting, pausing transfers, or blacklisting specific addresses — these all show as "no data" because they could not be independently verified, not because they were ruled out. Separately, the top 10 holders control 60.7% of the supply, meaning a small number of wallets hold the ability to move large amounts of the token at once, and liquidity is not locked, meaning whoever controls the liquidity pool could withdraw it without a time restriction preventing them from doing so. Because selling was blocked in simulation, the overall score is 0 out of 18 — a token that cannot be sold is treated as the maximum-risk outcome regardless of any other signal.
It's worth being clear about what this check does not do. It reads contract mechanics and on-chain data only, as they existed at the time of the scan. It does not assess who is behind the project, whether the team has a history, what the token is meant to be used for, whether any marketing claims are accurate, or whether there is a legal entity standing behind it. None of that is visible from bytecode or holder data, and no human has reviewed this project — the findings above are generated automatically.
Given that selling was blocked in this check, putting money into this token means that money would likely remain locked in the contract with no simulated path to retrieve it, so no purchase — test-sized or otherwise — is suggested as a way to verify this further. Instead, next steps would involve looking for the contract to be independently verified on the block explorer, checking whether liquidity gets locked with a visible time-lock contract, watching whether holder concentration changes over time, and searching for any independent audits or security reviews published by third parties. Community forums, the project's own disclosures, and repeated checks over time (rather than a single snapshot) can also help build a fuller picture, though none of these replace the fact that an automated scan detected selling could not be completed on the date it was run.
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.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.