Free above: contract permissions, sell test and tax when data is available.
Paid report: pool balances, trading activity, large holders and estimated price impact for supported pools.
| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 18 Nov 2026 |
| Buy tax | 0% | Contract | 18 Nov 2026 |
| Sell tax | 0% | Contract | 18 Nov 2026 |
| Admin mint | Not present | Contract | 18 Nov 2026 |
| Transfers pausable | Not present | Contract | 18 Nov 2026 |
| Address blacklist | Not present | Contract | 18 Nov 2026 |
| Upgradeable proxy | No | Contract | 18 Nov 2026 |
| Source verified | Yes | Block explorer | 18 Nov 2026 |
| Top-10 holders | 100% | Holder distribution | 18 Nov 2026 |
| Liquidity locked | No | LP holders | 18 Nov 2026 |
| Holders | 5 | Token contract | 18 Nov 2026 |
| Deployed by | 0xa5fdaf…c45228 |
| Current owner | 0x4928a1…8b2381 |
| Holders | 5 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x4928a1…8b2381 | 82.64% |
| #2 | 0xa5fdaf…c45228 | 11.15% |
| #3 | 0xba0ca4…a8b10d | 3.30% |
| #4 | 0x915c53…1e0e71 | 1.72% |
| #5 | 0xfa1557…85b2bc | 1.19% |
This automated check looked at the RYDEME contract's code and current on-chain state, and scored it 12 out of 18. A simulated transfer went through without being blocked, and no honeypot behaviour was detected at the time of the check, meaning a sale could be processed under current conditions. Buy and sell tax both read as 0%, so no hidden fee was found on transactions as coded. No admin minting function was detected, so the owner does not appear able to create new tokens out of thin air and dilute holders that way. Transfers do not appear pausable and no blacklist function was found, meaning the owner does not currently have a coded way to freeze the contract or lock specific wallets out of trading. The contract is not upgradeable through a proxy, so the logic deployed now is not set up to be swapped for different logic later. The source code is verified on the block explorer, which means the code is publicly readable and matches what's deployed, though "readable" is not the same as "harmless." The two points that stand out against the token are that liquidity is not locked, so whoever controls the liquidity pool could withdraw it, and the top 10 holders control 100% of supply across only 5 wallets, which is an extremely concentrated holding pattern — a small number of addresses could move the market significantly in either direction.
It's important to be clear about what this check does not cover. It reads contract mechanics only: the functions written into the code and the current holder and liquidity snapshot. It says nothing about who the team behind RYDEME is, whether they have a track record, what their stated plans or tokenomics actually mean in practice, or whether there is any legal entity standing behind the project. A clean mechanical read and a trustworthy project are not the same thing, and this check cannot speak to intent.
Before putting any money in, it would be worth looking at who holds those 5 wallets and whether any are known exchange, burn, or team addresses rather than independent holders, checking the liquidity pool directly to see who the pool tokens belong to and whether they could be pulled, looking for any public team identity or social presence with a history that predates the token, and searching for independent discussion of the project outside of its own channels. Given that liquidity is unlocked and ownership is this concentrated, the practical risk is less about whether a sale can technically execute right now and more about what could happen to price and liquidity if a small number of wallets or the liquidity owner acted at once.
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.