NEDU On-Chain Risk Check

Nedu Protocol · BSC · 0xb36e6bd49a41d040b82fbde83c6a5c8bf1e31fee
6 / 10 On-chain Check
Checked 18 Nov 2026. On-chain Check, 10 of the 100-point ChainSift Score — what it covers. Contract function analysis 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 ChainSift simulation 18 Nov 2026
Buy tax 0% Contract 18 Nov 2026
Sell tax 0% Contract 18 Nov 2026
Admin mint No data Contract 18 Nov 2026
Transfers pausable No data Contract 18 Nov 2026
Address blacklist No data Contract 18 Nov 2026
Upgradeable proxy No data Contract 18 Nov 2026
Source verified No Block explorer 18 Nov 2026
Top-10 holders 11.6% Holder distribution 18 Nov 2026
Liquidity locked No LP holders 18 Nov 2026
Holders 375 Token contract 18 Nov 2026

This contract — NEDU

Deployed by0x4b6049…b73f11
Holders375

Largest holders

RankAddressShare
#1 0x4b6049…b73f11 4.26%
#2 0xadc408…16aadc 3.44%
#3 0x32d5c2…c45597 0.59%
#4 0x214b6c…cf6a6d 0.57%
#5 0x9c1b3b…c35608 0.51%

What this means

This automated check found that a simulated sale of NEDU went through, and that the buy and sell tax were both recorded at 0% at the time of the check — meaning no honeypot behaviour or excessive tax was detected on this occasion. However, a significant portion of the picture is missing: the contract's source code is not verified on the block explorer, so ChainSift could only examine the deployed bytecode rather than readable code. This means functions that are common ways for an owner to act against holders — minting new tokens, pausing transfers, blacklisting addresses, or upgrading the contract's logic entirely — could not be scored and show as "no data" rather than confirmed absent. In practice, this means the check cannot tell you whether the contract owner retains any of these abilities; it only means that, with unverified source, those capabilities couldn't be inspected one way or the other. Liquidity is also not locked, which means whoever controls the liquidity pool could withdraw it, and holder concentration shows the top 10 wallets holding 11.6% of supply, a moderate but not extreme figure, recorded with only 375 holders total, a small base that can made price more sensitive to large trades.

It's important to be clear about what this check does not cover. This is an automated, mechanical read of the contract and its on-chain data as they stood on the day of the check — it says nothing about the team behind Nedu Protocol, their intentions, the project's tokenomics design, roadmap, or any legal standing. No person has reviewed this contract or project; the score reflects pattern-matching against known contract behaviours only, and a contract can score reasonably here while still carrying risks this type of check is not built to detect, such as a team quietly selling off their own holdings or marketing that misrepresents the project.

Given the unverified source and the unlocked liquidity, it would be reasonable to look for the contract's source code directly on the explorer, or ask the project team to verify it, before treating the "no data" functions as benign. Checking who holds the liquidity pool tokens and whether there is any lock or vesting schedule in place, researching the team's public identity and track record, and reading any available audit reports in full rather than summaries are all concrete next steps. None of this should be read as a signal to buy, hold, or avoid the token — it is simply unfinished information that a verified contract and locked liquidity would normally help fill in.

Team, tokenomics and legal structure are not assessed here — that is the other 90 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 10 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. The trade simulation (a buy, then a sale an hour later) is run by ChainSift directly on BSC — our data source returned none for this contract. 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.