| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 29 Oct 2026 |
| Buy tax | 0% | Contract | 29 Oct 2026 |
| Sell tax | 0% | Contract | 29 Oct 2026 |
| Admin mint | Not present | Contract | 29 Oct 2026 |
| Transfers pausable | Not present | Contract | 29 Oct 2026 |
| Address blacklist | Not present | Contract | 29 Oct 2026 |
| Upgradeable proxy | No | Contract | 29 Oct 2026 |
| Source verified | Yes | Block explorer | 29 Oct 2026 |
| Liquidity locked | 50.3%, end date unknown | LP holders · Mudra | 29 Oct 2026 |
| Holders | 251 | Token contract | 29 Oct 2026 |
| Deployed by | 0xd7a848…fdedb1 |
| Current owner | None — ownership renounced |
| Holders | 251 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0xd7a848…fdedb1 | 100.00% |
| #2 | 0x20235e…349c74 | 29.76% |
| #3 · contract | 0x34dbf2…2487f0 | 21.00% |
| #4 · contract | 0x71fabb…5f69f2 | 20.00% |
| #5 · contract | 0xb57a78…87173a | 10.50% |
This automated check of MinaCash (MC) on BNB Chain returned a score of 12 out of 12, based on the contract mechanics that were tested on the date of the check. A transfer simulation found the token to be sellable, with no honeypot behaviour detected. Buy and sell tax were both read at 0% directly from the contract code. No admin mint function was found, meaning the contract owner does not appear to retain a way to create new tokens out of thin air and dilute holders. No transfer-pausing function was detected, so the owner does not currently appear able to freeze trading for everyone at will. No address blacklist function was found, meaning there is no mechanism visible in the code to block specific wallets from trading. The contract is not an upgradeable proxy, which means its logic cannot be swapped out later for different behaviour without deploying an entirely new contract. The source code is verified on the block explorer, so the logic described above can be read by anyone. Liquidity is reported as 50.3% locked, though the lock's end date is unknown, which limits how much confidence can be placed in that lock holding over any particular time horizon.
It's important to be clear about what this check does not cover. This is a purely automated read of contract code and a handful of on-chain data points — nothing here involves a human reviewing the project. It says nothing about who is behind MinaCash, whether the team is anonymous, how tokens are distributed among insiders versus the public, what the stated use case or roadmap is, or whether any marketing claims hold up. A clean mechanical score does not speak to tokenomics design, legal structure, jurisdiction, or the intent of the people running the project. Contract owners can also hold other privileges, such as large undisclosed wallet balances or the ability to change fees later through means not captured here.
Before considering any transaction, it would be worth looking up the liquidity lock directly on the locking platform to confirm the actual unlock date, since "unknown" leaves a gap. The holder list (251 holders here) is worth reviewing for concentration — a small number of wallets holding most of the supply is a separate risk from anything this check measures. It's also worth searching independently for the team's identity, any audit reports, community discussion, and the project's official channels, and treating unsolicited links or urgency to act quickly with caution.
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 12 points out of 100.
The other 88 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.