IDRENT On-Chain Risk Check

IDRENT · BSC · 0x5b30d8ec99a42b2e6f69f4258721a56d2bc37777
11 / 12 On-chain Check
Checked 18 Nov 2026. On-chain Check, 12 of the 100-point ChainSift Score — what it covers. Holder distribution was unavailable for this contract, so that signal is excluded from the total.

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.

Evidence

Risk factorFindingEvidenceDate
Sellable Yes Transfer simulation 18 Nov 2026
Buy tax 3% Flap token code 18 Nov 2026
Sell tax 3% Flap token code 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
Liquidity locked 100% burned LP holders 18 Nov 2026
Holders 0 Token contract 18 Nov 2026

This contract — IDRENT

Deployed by0x82a145…21fb65
Current ownerNone — ownership renounced

What this means

This automated check scored IDRENT 11 out of 12 on contract mechanics, and it's worth unpacking what that actually covers. A transfer simulation found the token sellable on the date of the check, meaning no honeypot behaviour was detected — tokens bought can be sold back through the pool. The contract charges a transfer tax of up to 3%, applied as a 3% fee on both buys and sells through its launch pools; this rate was fixed at launch, there is no function in the code to change it, and it has no built-in end date, so it should be treated as a permanent cost of trading rather than a temporary promotional rate. No admin mint function was found, meaning the owner does not appear able to create new tokens and dilute holders. No pause function was found, so the owner does not appear able to freeze transfers. No blacklist function was found, so the owner does not appear able to block specific addresses from trading. The contract is not an upgradeable proxy, meaning its logic cannot be swapped out later for different behaviour. The source code is verified on the block explorer, so the logic reviewed is the logic actually running. Liquidity is reported as 100% burned, meaning the tokens representing the trading pool were sent to a dead address rather than held by a wallet that could withdraw them.

What this check does not tell you is just as important. It reads contract code and on-chain state only — it says nothing about who is behind the project, whether the team is anonymous, how tokens are distributed among wallets, what the stated purpose or roadmap is, or whether any marketing claims hold up. The holder count is reported as 0, which may reflect indexing lag rather than actual distribution, but either way this check does not assess concentration, team allocations, or vesting. Intent, legal structure, and future conduct of whoever controls the project are outside the scope of a mechanical contract read.

Before putting money in, it would be worth independently checking the real holder distribution and whether a small number of wallets control a large share of supply, looking at trading volume and liquidity depth on the actual exchange or pool you'd use, searching for the team's public identity and any history with other projects, and reading the project's own documentation or social channels for claims you can try to verify independently. None of this check's findings should be read as a conclusion about whether the token is worth buying.

Team, tokenomics and legal structure are not assessed here — that is the other 88 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 12 points out of 100.

A deep check also reviews the project's public materials, team, tokenomics and disclosures.

Related guides

Contract data read from GoPlus Security and the BSC block explorer. Scores are calculated by fixed rules from that data — no language model decides them. Last updated 18 Nov 2026. A check describes a contract on the date shown; contracts can be changed afterwards.