| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No data | Transfer simulation | 13 Nov 2026 |
| Buy tax | 0% | Contract | 13 Nov 2026 |
| Sell tax | 0% | Contract | 13 Nov 2026 |
| Admin mint | No data | Contract | 13 Nov 2026 |
| Transfers pausable | No data | Contract | 13 Nov 2026 |
| Address blacklist | No data | Contract | 13 Nov 2026 |
| Upgradeable proxy | No data | Contract | 13 Nov 2026 |
| Source verified | No | Block explorer | 13 Nov 2026 |
| Top-10 holders | 100% | Holder distribution | 13 Nov 2026 |
| Holders | 5 | Token contract | 13 Nov 2026 |
| Deployed by | 0x88818b…11b9fd |
| Holders | 5 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x88818b…11b9fd | 100.00% |
| #2 · contract | 0xf91bf7…ea8d6c | 0.00% |
| #3 · contract | 0xfc3c46…a5129a | 0.00% |
| #4 · contract | 0x208ab2…fe5a5d | 0.00% |
| #5 · Uniswap v4 pool · contract | 0x000000…e08a90 | 0.00% |
This automated check returned a score of 0 out of 10 for ARGP, and the reason is largely that there is very little to actually check. The contract's source code is not verified on the block explorer, which means the underlying logic is only visible as compiled bytecode. In practice, this blocks automated analysis of the functions that matter most: whether the owner can mint new tokens at will, pause transfers, freeze or blacklist specific wallets, or upgrade the contract to change its rules after launch. None of these were confirmed present, but none were confirmed absent either — they are simply unreadable from the outside, which is itself a meaningful risk indicator. Separately, whether the token can be sold at all could not be established through transfer simulation; no sell result was returned. On top of that, the top 10 holders control 100% of the total supply across only 5 wallets, meaning a very small number of addresses hold the entire circulating amount and could move or dump it without any advance signal to other holders.
It's worth being clear about what this check does not cover. It reads contract mechanics only — it does not assess who is behind the project, how tokens are allocated or vested, whether there is a working product, whether any claims made in marketing materials are accurate, or whether the team has any legal accountability. A contract can look mechanically unremarkable and still be attached to a project with no real activity behind it, and conversely, unverified source code does not by itself prove bad intent — it simply means this automated process cannot confirm what the code does.
Given that sellability could not be confirmed and the contract is unverified, no test transaction is a reasonable way to find out more — if selling turns out to be blocked, funds put in would not be retrievable. Instead, the more useful next steps are to look for the contract source being published and independently verified on a block explorer, to check whether the project or team has had the contract audited by a named third party, to look at the holder list directly on-chain to see how concentrated and how active those five wallets are, and to search for any independent commentary or documentation about Araget Protocol outside of its own channels. None of this check's findings should be read as a conclusion about the project's intentions — only as a description of what is and isn't verifiable from the contract itself on the date of this check.
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.