| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 3 Nov 2026 |
| Buy tax | 0% | Contract | 3 Nov 2026 |
| Sell tax | No data | Contract | 3 Nov 2026 |
| Admin mint | No data | Contract | 3 Nov 2026 |
| Transfers pausable | No data | Contract | 3 Nov 2026 |
| Address blacklist | No data | Contract | 3 Nov 2026 |
| Upgradeable proxy | No data | Contract | 3 Nov 2026 |
| Source verified | No | Block explorer | 3 Nov 2026 |
| Top-10 holders | 86.5% | Holder distribution | 3 Nov 2026 |
| Liquidity locked | No | LP holders | 3 Nov 2026 |
| Holders | 2192 | Token contract | 3 Nov 2026 |
| Deployed by | 0xe4d6e6…c35f5f |
| Holders | 2,192 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x6b3b80…3ba9bb | 20.50% |
| #2 · SushiSwapV2 · contract | 0x54dda9…7f37af | 14.06% |
| #3 | 0xb38e8c…82891d | 10.00% |
| #4 | 0x0d0707…b492fe | 10.00% |
| #5 | 0xe4d6e6…c35f5f | 9.10% |
This automated check scored ORHGO 0 out of 18 on Arbitrum, and the central reason is a honeypot flag: ChainSift's simulation found that selling is blocked by the contract. In practice, this means that while buying the token appears possible (buy tax recorded at 0%), the contract's code prevents transfers out again, so tokens acquired cannot currently be converted back to other assets. On top of this, the contract's source code is not verified, meaning the underlying logic is only visible as compiled bytecode and could not be independently read to confirm what functions exist, such as minting new supply, pausing transfers, or blacklisting addresses — these all show as "no data" because they couldn't be checked, not because they were ruled out. Liquidity is also not locked, which means whoever controls the liquidity pool retains the ability to withdraw it. Holder concentration is high, with the top 10 wallets holding 86.5% of supply, which means a small number of addresses could materially affect the token's market if they acted together.
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 ORHGO is, whether their stated plans or roadmap are credible, how the tokenomics are structured beyond what's on-chain, or whether any legal entity stands behind the project. No human has reviewed this contract or the project's intentions, and this check cannot speak to intent at all, only to what the code currently allows or does not allow the owner to do to holders.
Given that selling is blocked, no amount of money put into this token — including a small test purchase — can currently be withdrawn, since the honeypot behaviour means any tokens acquired may be stuck. Rather than testing with funds, next steps that don't involve financial exposure include checking the contract address directly on Arbiscan to look for any owner or admin comments, searching for the project's official channels and community discussion to see whether this selling restriction has been reported by others, and checking whether the contract has been flagged on other independent honeypot or scam-detection tools. If the project is new, it may also be worth checking whether the token is still within an initial lock-up or anti-bot period that developers sometimes build in temporarily — though this cannot be confirmed from bytecode alone, and would need separate verification from the project itself.
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.
The other 82 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.
Trading a meme coin? The meme coin check shows how much real money is in the pool and what you lose selling $1,000, who can pull that money out, who holds the supply and how it trades — ready within 3 minutes of payment, day or night.