Early-stage security check — honeypot & rug-pull analysis
BNB ChainThe JagentTokenV2 contract is a standard ERC-20 token with added administrative controls for minting, burning, and transfer restrictions.
Read the full analysisEach factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed
Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.
Holder balances as recorded by the audit of Oct 28, 2026
The risk score reads depth across every pair.
The LP tokens of the analysed pool are locked or burned.
0x0ed9…9706No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The 'minter' address has the authority to call the mint function, which increases the total supply of tokens. This allows the controller to dilute the value of existing holdings at any time.
Implement a hard cap on total supply or transition the minting authority to a decentralized governance mechanism.
Unresolved
The 'minter' can trigger the 'disableBlocks' function, which modifies the transfer logic. This grants the controller the ability to halt all token transfers or sales globally.
Remove the ability to globally disable transfers or implement a community-voted mechanism for such drastic actions.
Unresolved
The 'minter' can use 'setPoolBlocked' to prevent specific addresses from interacting with the token. This allows the controller to freeze individual user funds without due process.
Restrict the blacklisting functionality to only address malicious actors via a transparent, verifiable process, or remove the feature entirely.
Unresolved
The ten largest holders own 17.4% of supply. Of that, 4.4% burned, 6.8% in DEX pools — not holders that can sell, so excluded from the concentration score. What remains: 5.5% in wallets, 0.6% in other contracts. 4,364 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
4,364 holders. Not listed by CoinGecko or any exchange GoPlus tracks. Nothing independent confirms who is behind this token, so every power its contract grants is scored at face value.
Match the contract address against the project's official channels before trading.
Acknowledged
98.9% of the pool's LP is burned or time-locked. 98.9% of the LP tokens were sent to a burn address — that liquidity can never be withdrawn by anyone. 1.1% is held, unlocked, by 1 address(es) other than the owner/deployer. No single one holds a majority: their exits thin the market rather than hand anyone the pool. Some pools are concentrated-liquidity (V3/V4) positions; shares above are by position as GoPlus reports them.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
Liquidity $197K (DexScreener, all pools). 24h trading volume $1.8M (DexScreener, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
A token issued by a project for use, governance or fundraising. Scored on its contract and market facts. The class itself adds no points; the contract and market facts decide the score. Basis: no class-specific evidence. Tokenomics — Supply: mintable with no on-chain cap found. Control: an owner that could not be resolved. Code: not upgradeable (no proxy). Fees: 1% on buy, 2% on sell. Market: $197K of DEX liquidity across 1 pools. Launch: under a day of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
The token's oldest DEX pool is less than a day old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
Re-check ownership, liquidity and holder distribution as the token matures; those are the facts that move early.
Acknowledged
The JagentTokenV2 contract is a standard ERC-20 token with added administrative controls for minting, burning, and transfer restrictions. The protocol relies on a centralized 'minter' role that holds significant power over token supply and holder liquidity. While the code follows standard OpenZeppelin patterns, the centralization of power represents a notable risk to token holders.
The contract utilizes standard OpenZeppelin libraries for ERC-20 functionality, ensuring 7.1 Architecture and 7.2 Code Security standards are met. The implementation is clean and follows 7.8 Operations best practices for state management. However, the logic includes custom transfer hooks that introduce 7.6 External dependencies on administrative state. These hooks are correctly implemented but grant the minter significant control over token flow.
The protocol exhibits high centralization, violating 7.5 Governance best practices by concentrating power in a single minter address. The 7.4 Economic model allows for arbitrary supply inflation and liquidity restriction. There are no timelocks or multi-signature requirements for these sensitive administrative actions.
The contract is not upgradeable, satisfying 7.7 Upgrades safety by design. The logic is immutable once deployed. No proxy patterns are utilized, eliminating risks associated with implementation updates.
It is recommended to transition the 'minter' role to a decentralized multi-signature wallet or a DAO-governed contract to mitigate the risks of single-point-of-failure.
Implementing a timelock on sensitive administrative functions like 'setPoolBlocked' would provide transparency and protection to token holders against sudden policy changes.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
The JAGENT contract on BNB Chain is 0x8e6442663a4f8c50b6132c68d42a30e7dfe4ae15. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.
Quantum Audit's risk score for JAGENT is 42/100 (Medium risk) as of Oct 28, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; Mint: Mintable; Liquidity lock: Locked; Upgradeability: Fixed code; Honeypot: None found; Buy / sell tax: 1% / 2%. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.
Liquidity lock: Locked (as of Oct 28, 2026). Total DEX liquidity: $197.3K.
As of Oct 28, 2026, the 10 largest holders own 17.4% of the supply across 4,364 holders. The Holders section on this page shows who they are by holder type.
This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.
Get Detailed Audit Is this your token? Add your links and get it Verified
