| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 29 Oct 2026 |
| Buy tax | 0% | Contract | 29 Oct 2026 |
| Sell tax | 0% | Contract | 29 Oct 2026 |
| Admin mint | No data | Contract | 29 Oct 2026 |
| Transfers pausable | No data | Contract | 29 Oct 2026 |
| Address blacklist | No data | Contract | 29 Oct 2026 |
| Upgradeable proxy | No data | Contract | 29 Oct 2026 |
| Source verified | No data | Block explorer | 29 Oct 2026 |
| Holders | 0 | Token contract | 29 Oct 2026 |
| Deployed by | 0xbf7707…21a6c3 |
This automated check simulated a sell transaction for REWOLF and found that it could not be completed: the contract blocks transfers in a way that stops holders from selling their tokens back. This is known as honeypot behaviour, and it is the most serious finding this tool can return. When selling is blocked at the contract level, it does not matter what the buy or sell tax rates are set to on paper, or how any other signal looks — the token scores 0 out of 8 automatically, because the core function of being able to exit a position is not available. In practice, this means that whoever controls the contract has structured it so that tokens can be bought but not sold by ordinary holders, which is a mechanism that can trap funds permanently.
It is worth being clear about what this check does and does not cover. This is an automated read of the contract's mechanics on the date of the check — it simulates transactions and inspects code patterns, nothing more. It does not know who the team behind REWOLF is, what their intentions are, how the token's supply or distribution is structured beyond the contract logic, or whether any legal entity stands behind the project. Several fields in the evidence table above are marked "no data," including whether the contract is verified on a block explorer, whether an admin can mint new tokens, and whether transfers can be paused — these simply were not retrieved or detected at the time of the check, not confirmed as absent. No holder data was available either, so concentration of ownership could not be assessed here.
Given that selling has been found to be blocked, there is no safe way to "test" this token with a small purchase — if the contract prevents sales for other holders, there is no reason to expect a small buy would behave differently, and any funds sent in would likely remain inaccessible. Instead, the sensible next step is to treat this finding as a strong signal to investigate further before any funds are committed at all. That means reading the actual contract source code on a block explorer if it is verified, checking community forums or project channels for other reports of blocked sales, and looking at whether the contract owner has renounced privileged functions. If the source code is not verified, that itself is a separate and significant gap, since it limits what anyone — automated tool or person — can confirm about how the contract behaves.
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 8 points out of 100.
The other 92 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.