JASON On-Chain Risk Check

Jason Duval · Base · 0xfa71887b8fb16e09b376ba91bc78e76784c20080
4 / 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.

Previous check: 1/10 on 15 Nov 2026. Since then: top-10 holders 78.4% → 38.3%.

Evidence

Risk factorFindingEvidenceDate
Sellable No data Transfer simulation 18 Nov 2026
Buy tax No data Contract 18 Nov 2026
Sell tax No data 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 38.3% Holder distribution 18 Nov 2026
Holders 13798 Token contract 18 Nov 2026

This contract — JASON

Deployed by0xb7b1a9…bb051d
Holders13,798

Largest holders

RankAddressShare
#1 0xb7b1a9…bb051d 29.37%
#2 0x727b25…b123a3 1.02%
#3 0x7391dc…022e97 1.01%
#4 0xc71216…ac962b 0.99%
#5 0xcfc8eb…dbb007 0.99%

What this means

This automated check scored JASON 4 out of 10 on Base, and the most important thing to understand is how much of the picture is actually missing. Contract source is not verified, meaning the underlying code has not been published for inspection — only the compiled bytecode exists on-chain. Because of this, the functions that normally reveal whether an owner can mint new tokens, pause transfers, blacklist addresses, swap in an upgraded contract, or block sales were not reported by the data source at all. No honeypot behaviour was detected in this check, but that is because the relevant data was unavailable, not because sellability was confirmed — this is a meaningful distinction. Separately, the top 10 holders control 38.3% of the supply, which is a concentration level that means a small number of wallets could move a large portion of tokens at once, independent of anything the contract code does.

It's worth being clear about what this check does not cover. It reads contract mechanics only — things that can, in principle, be detected from code and on-chain data. It says nothing about who is behind the Jason Duval name attached to this token, whether any team has committed to a roadmap, how tokens were allocated or vested, whether there is a legal entity standing behind the project, or what the intent of the deployer is. A token can show no flags on a mechanical check and still carry risk tied to team behaviour, marketing claims, or how tokenomics are structured. None of that is assessed here, and this check does not involve any human reviewer — it is fully automated.

Given the unverified source and the missing function data, the practical next step is to look at the contract directly on the Base block explorer and see whether the bytecode has since been verified, since that would allow the mint, pause, blacklist, and tax functions to actually be scored. It's also worth checking whether liquidity is locked and for how long, who holds the top wallets (some concentration can be exchange or liquidity-pool addresses rather than individuals), and whether the project has any public documentation, audits, or team identity that can be independently verified. Because core sellability data was not available, this is not a case where a small test transaction can substitute for that information — if sell behaviour can't be confirmed, money placed into the token cannot be assumed to be retrievable. Any decision should wait until the missing contract data can be reviewed directly, alongside independent research into the people and structure behind the project.

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 Base 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.