INT On-Chain Risk Check

Intmax · BSC · 0x85be6e4d4443133e51e4ffc9bcb3b986cd2a78e4
0 / 18 On-chain Check
Checked 17 Oct 2026. On-chain Check, 18 of the 100-point ChainSift Score — what it covers.

Evidence

Risk factorFindingEvidenceDate
Sellable No — transfers blocked ChainSift simulation 17 Oct 2026
Buy tax 0% Contract 17 Oct 2026
Sell tax No data Contract 17 Oct 2026
Admin mint No data Contract 17 Oct 2026
Transfers pausable No data Contract 17 Oct 2026
Address blacklist Enabled Contract bytecode 17 Oct 2026
Upgradeable proxy No data Contract 17 Oct 2026
Source verified No Block explorer 17 Oct 2026
Top-10 holders 99.9% Holder distribution 17 Oct 2026
Liquidity locked No LP holders 17 Oct 2026
Holders 6157 Token contract 17 Oct 2026

This contract — INT

Deployed by0x487077…569510
Holders6,157

Largest holders

RankAddressShare
#1 0x487077…569510 79.08%
#2 0xf97781…41acec 6.11%
#3 0xf89d7b…5eaa40 4.90%
#4 0x635308…7553d9 3.00%
#5 0x3b5a23…23b32d 2.50%

What this means

This automated check on INT (Intmax) on BSC returned a score of 0 out of 18, and the findings point to serious structural risk indicators that were detected in the contract on the date of this check. The most significant is honeypot behaviour: ChainSift's simulation found that selling is blocked by the contract, meaning holders can buy the token but may not be able to sell it back for other assets. The contract also supports blacklisting addresses, which would let whoever controls it prevent specific wallets from transacting at all. On top of this, the top 10 holders control 99.9% of the supply, so a very small number of wallets — potentially including the project team or deployer — hold the overwhelming majority of tokens and could affect the market significantly if they moved them. The contract source code is not verified, meaning no one can read a human-readable version of what the contract actually does; only raw bytecode is available, which limits independent scrutiny. Finally, liquidity is not locked, so whoever supplied the trading pool could withdraw it at any time, which could leave buyers holding a token with no functioning market.

It's important to understand what this check does not cover. This is an automated read of contract mechanics only — it looks at code behaviour, holder distribution and liquidity status. It says nothing about who is behind the project, their intentions, their track record, the token's economic design, whether any entity has legal accountability, or whether marketing claims made elsewhere are accurate. No human has reviewed this project, and the absence of a specific flag only means that particular behaviour was not detected at the time of the check — it is not a guarantee that the behaviour doesn't exist or won't be added later.

Before considering any transaction involving this token, it would be worth independently verifying several things: whether the contract source code can be obtained and reviewed elsewhere, whether there is any public documentation identifying the team and their history, whether the liquidity pool details can be confirmed directly on-chain through a block explorer, and whether other holders have reported being able to sell successfully. Given that selling was blocked in this simulation and liquidity is unlocked, anyone considering an interaction with this contract should treat the inability to exit a position as a live possibility rather than a remote one, and should weigh that carefully against any amount they are considering committing.

Team, tokenomics and legal structure are not assessed here — that is the other 82 points of the ChainSift Score. How this check works and what it misses.

Watch this contract

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 send one confirmation message and nothing else until something changes.

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.

Related guides

Contract data read from GoPlus Security and the BSC block explorer. The trade simulation (a buy, then a sale an hour later) and the functions found in the contract bytecode come from ChainSift directly on BSC — our data source returned neither for this contract. Scores are calculated by fixed rules from that data — no language model decides them. Last updated 17 Oct 2026. A check describes a contract on the date shown; contracts can be changed afterwards.