| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No data | Transfer simulation | 12 Nov 2026 |
| Buy tax | No data | Contract | 12 Nov 2026 |
| Sell tax | No data | Contract | 12 Nov 2026 |
| Admin mint | No data | Contract | 12 Nov 2026 |
| Transfers pausable | No data | Contract | 12 Nov 2026 |
| Address blacklist | No data | Contract | 12 Nov 2026 |
| Upgradeable proxy | No data | Contract | 12 Nov 2026 |
| Source verified | No | Block explorer | 12 Nov 2026 |
| Top-10 holders | 99.9% | Holder distribution | 12 Nov 2026 |
| Liquidity locked | No | LP holders | 12 Nov 2026 |
| Holders | 837 | Token contract | 12 Nov 2026 |
| Deployed by | 0x6a78a3…4a67c9 |
| Holders | 837 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x6a78a3…4a67c9 | 77.25% |
| #2 | 0xbe0eb5…4d33e8 | 8.78% |
| #3 | 0xf89d7b…5eaa40 | 7.22% |
| #4 | 0x1c4b70…bb558c | 6.60% |
| #5 | 0xcf9b36…eaecf3 | 0.03% |
This automated check could not confirm most of the mechanics that usually matter most for a token like TUQP. The contract's source code is not verified on the block explorer, which means the check only had raw bytecode to work with and could not reliably determine whether functions like minting new tokens, pausing transfers, blacklisting addresses, or changing tax rates exist in this contract. Because of that, several core checks — including whether the token can actually be sold — returned no data rather than a pass or fail. No data is not the same as a clean result; it means the behaviour is unknown as of the date of this check, not that it was tested and found absent. What is known is concerning on its own: the top 10 holders control 99.9% of the total supply, and the liquidity backing this token is not locked, meaning whoever holds it could remove it from the trading pool at any time. These two findings together describe a structure where a very small number of wallets hold both the tokens and the ability to pull the trading liquidity, which would leave remaining holders unable to sell at a meaningful price even if the contract itself allows selling.
It is also worth being clear about what this check does not do. It only reads contract code and on-chain data — it does not assess who the team behind Tuqify Protocol is, whether they have a track record, what the stated use case or roadmap involves, how tokens were allocated or vested, or whether any legal entity stands behind the project. None of that is visible from bytecode or holder distribution, and this report makes no claim about the intentions of the people who deployed this contract.
Given that sellability itself returned no data, this is not a case where a small test purchase would help confirm anything — if the contract turns out to block sells, any funds put in would simply be stuck, so that approach carries its own risk and is not a way to "check safely." Before considering this token further, it would be worth seeking a verified source code audit from the project team directly, checking whether any reputable third-party contract audit exists and matches the deployed bytecode, and looking at whether liquidity lock or multisig arrangements are documented anywhere outside this check. Given the unverified source and the extreme holder concentration combined with unlocked liquidity, this profile carries a markedly elevated risk of total loss of funds, and that should be weighed carefully against the significant gaps in what could actually be verified here.
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.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.