| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | Transfer simulation | 13 Nov 2026 |
| Buy tax | 0% | Contract | 13 Nov 2026 |
| Sell tax | No data | Contract | 13 Nov 2026 |
| Admin mint | Not present | Contract | 13 Nov 2026 |
| Transfers pausable | Not present | Contract | 13 Nov 2026 |
| Address blacklist | Not present | Contract | 13 Nov 2026 |
| Upgradeable proxy | No | Contract | 13 Nov 2026 |
| Source verified | Yes | Block explorer | 13 Nov 2026 |
| Top-10 holders | 55.9% | Holder distribution | 13 Nov 2026 |
| Liquidity locked | 85.9% burned | LP holders | 13 Nov 2026 |
| Holders | 119325 | Token contract | 13 Nov 2026 |
| Deployed by | 0xe3bb32…143879 |
| Holders | 119,325 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x02eb78…43a13b | 21.14% |
| #2 · contract | 0xbfdafe…e52bc8 | 16.29% |
| #3 · burned | 0x000000…00dead | 14.59% |
| #4 | 0x688b83…309b61 | 0.92% |
| #5 | 0x2f21a5…8341f5 | 0.72% |
This automated check found that Sorai's contract currently blocks selling. In practice, this means that wallets holding this token can buy in but cannot execute a sell transaction back through the contract as it stands — this is the single most serious finding this check can produce, and it is why the overall score sits at 0 out of 18 regardless of any other signals. When selling is blocked, funds placed into the token remain in the wallet with no confirmed path back out at the time of this check, so no test purchase, however small, is a way to verify this — a blocked sell function typically blocks all sells, not just large ones.
The other findings describe separate aspects of the contract and are worth understanding on their own terms, though none of them offset the sell block. No minting function, pausable transfer function, blacklist function or upgradeable proxy were detected, meaning the contract does not appear to give its owner those specific tools to alter supply, freeze transfers, block individual addresses, or swap out the underlying code after deployment — as read on the date of this check. Liquidity was found to be 85.9% burned, which generally reduces (though does not eliminate) the risk of the pool itself being withdrawn by whoever controls it. Source code is verified on the block explorer, meaning the code is publicly readable, not that it has been assessed for intent. Holder concentration was found to be high, with the top 10 wallets controlling 55.9% of supply — a structure where a small number of addresses hold majority supply, which carries its own separate liquidity and price-impact considerations.
It's important to be clear about what this check does not cover. This is an automated read of contract mechanics only — it does not assess who the team behind the token is, their track record, the token's economic design or distribution plan, any marketing claims, or the legal structure the project operates under. No human has reviewed this project, and nothing here speaks to intent.
Given the honeypot finding specifically, anyone evaluating this token further would reasonably want independent confirmation of sell-side behaviour from another source before considering any interaction with the contract, a look at whether the development team is identifiable and has any public history, a check of how the 55.9% top-10 holder concentration is distributed among those wallets (exchange, deployer, or unrelated individual wallets each carry different implications), and a review of the liquidity lock details — including who performed the burn and when — through the explorer link for the LP tokens directly.
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.