JCT On-Chain Risk Check

JANCTION · BSC · 0xea37a8de1de2d9d10772eeb569e28bfa5cb17707
10 / 18 On-chain Check
Checked 18 Nov 2026. On-chain Check, 18 of the 100-point ChainSift Score — what it covers.

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 Enabled Implementation code 18 Nov 2026
Transfers pausable Not found Implementation code 18 Nov 2026
Address blacklist Not found Implementation code 18 Nov 2026
Upgradeable proxy Yes — a 5-of-7 multisig can replace the code Proxy contract 18 Nov 2026
Source verified Yes Block explorer 18 Nov 2026
Top-10 holders 79.4% Holder distribution 18 Nov 2026
Liquidity locked No LP holders 18 Nov 2026
Holders 18502 Token contract 18 Nov 2026

This contract — JCT

Deployed by0x513bc7…39a15a
Code can be replaced by0x65f8e5…1ca0a6 — a 5-of-7 multisig
Current code0x3184f3…85a8ef
Holders18,502

Largest holders

RankAddressShare
#1 0xa4856e…310f10 22.96%
#2 · contract 0x73d8bd…4946db 21.82%
#3 · contract 0xb8e6d3…be6b23 16.24%
#4 0x498208…6e89cb 4.34%
#5 0xed9ab5…c18771 2.93%

What this means

This automated check scanned the JCT contract on BNB Chain and found a score of 10 out of 18. A few mechanics are worth translating into plain terms. The contract owner can mint new tokens at will, which means the circulating supply can be increased without holder approval, diluting everyone who already holds JCT. More significantly, the contract sits behind an upgradeable proxy controlled by a 5-of-7 multisig — in practice this means that five of seven key-holders could agree to replace the entire contract logic, including removing or changing any of the protections or behaviours described in this report, at any point in the future. On the positive side, no transfer-pausing or address-blacklisting functions were found in the implementation code on the date of this check, and the simulation confirmed that selling currently works, with buy and sell tax both set to 0%. The contract source is verified on the block explorer, which allows this kind of inspection in the first place. Holder concentration is high: the top ten wallets hold 79.4% of supply, meaning a small number of addresses could move a large share of tokens if they chose to sell. Liquidity is not locked, though in this case the main pool is spread across 116 separate providers rather than concentrated in one or two wallets.

It's important to be clear about what this check does not cover. It reads contract code and on-chain data only — mint functions, pause and blacklist capabilities, proxy upgradeability, tax settings, holder distribution and liquidity ownership. It says nothing about who is behind the project, whether the team has a history of delivering, how tokenomics are designed to play out over time, whether any legal or regulatory structure exists, or what the people controlling the multisig actually intend to do with that power. A contract can look mechanically clean and still be attached to a project with no real product, or a team that disappears. None of that is visible from bytecode.

Before putting money into JCT, it would be reasonable to look into who holds the multisig keys and whether their identities or track record are disclosed anywhere, to check whether the project has any audit from a named firm and read what it actually covers, to look at the trading history and growth pattern of those top-10 wallets rather than just the current snapshot, and to search independently for any community discussion, news, or complaints about the team or token. Checking the liquidity pool composition directly on a block explorer, rather than relying on a summary, is also worthwhile given liquidity is not locked.

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.

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. Upgrade rights, the functions of the current code and the trade simulation are read by ChainSift directly from BSC — our data source doesn't analyse upgradeable contracts. 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.