Quantum Audit Logo
Launch App

On-chain security analysis — is it a scam or legit?

Is XEN Crypto Safe?

XENEthereum
Not verified This record has not gone through deep verification and is not being monitored. The score is a dated snapshot — the token’s risk can change at any time.Own this token? Put it under verification →
Last checked Sep 4, 2026 · 1 audit on record
Chart
Low RiskHow is this score calculated?
How the score breaks downratings: 10 is safest
Technical10/10Governance3/10Upgrades6/10Checks passed5 of 7Findings1 Low · 2 Info3
SummaryAI Copilot

The audit focused on the Math library, which serves as an implementation for the XENCrypto proxy.

Read the full analysis
What raised the score
  • Ownership status UNKNOWN
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 73.9%
  • LP top3 unlocked holders = 92.8%
  • 1 Low finding(s) from audit
Exact factors
  • Ownership status UNKNOWN (owner could not be resolved)
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 73.9% (independent LP — depth risk, pool = 64% of DEX liquidity)
  • LP top3 unlocked holders = 92.8% (independent LP — depth risk, pool = 64% of DEX liquidity)
  • 1 Low finding(s) from audit

Each 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

Security Checklist

as of audit · Sep 45 of 7 checks passed
Contract verifiedVerified
OwnershipUnknown
MintNo mint
Liquidity lockNot locked
UpgradeabilityFixed code
HoneypotNone found
Buy / sell tax0% / 0%

Holders

as of audit · Sep 4, 2026
5.5%13.4%Wallets81.1%Everyone else
5.5%13.4%Wallets81.1%Everyone else
ContractsWalletsEveryone elseBubble area = share of supply
18.9%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking5.5%
  • Walletsanonymous holders, free to sell13.4%
  • Everyone elsethe rest of the supply81.1%
Effective concentrationwhat the score reads15.6%
How holder types affect the score

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 Sep 4, 2026

Liquidity

as of audit · Sep 4$89.5K across 9 pairs
Show 3 more pairs

The risk score reads depth across every pair.

LP tokensNot locked

The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.

Analysed pool$57.7KShare of depth64.5%
Top-1 Unlocked Holder73.9%
Top-3 Unlocked92.8%
Unlocked LP held by
0xd3b9…08360x945d…04af0x2ffa…354f0x758c…33940xb251…27af0xa443…df850x03e5…5db50x78e3…9e4a0x4d0b…5d5f0x3fc8…5c3c

No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.

Security Findings

1 Low2 Info
Low

Extensive Use of require for Fixed-Point Range Checks

The ABDKMath64x64 library extensively uses require statements within unchecked blocks to enforce range limits (MIN_64x64, MAX_64x64) for 64.64-bit fixed-point numbers after intermediate int256 calculations. While these checks are crucial for preventing overflows/underflows and ensuring mathematical correctness, they can lead to higher gas costs for transactions that provide inputs resulting in out-of-range fixed-point values, as such transactions will revert. This is an expected trade-off for safety in fixed-point arithmetic.L-01

Issue

The ABDKMath64x64 library extensively uses require statements within unchecked blocks to enforce range limits (MIN_64x64, MAX_64x64) for 64.64-bit fixed-point numbers after intermediate int256 calculations. While these checks are crucial for preventing overflows/underflows and ensuring mathematical correctness, they can lead to higher gas costs for transactions that provide inputs resulting in out-of-range fixed-point values, as such transactions will revert. This is an expected trade-off for safety in fixed-point arithmetic.

Fix

This is a design choice for safety and is generally acceptable for fixed-point libraries. Users of the Math library should be aware that inputs leading to results outside the 64.64-bit range will cause transactions to revert. No direct action is required unless gas optimization for invalid inputs is a critical concern, which would typically involve a different fixed-point implementation strategy.

Status

Unresolved

Info

Reliance on Third-Party Library

The Math contract's core functionality for fixed-point arithmetic is entirely dependent on the ABDKMath64x64 library. While ABDKMath64x64 is a well-known and generally robust library, any undiscovered vulnerability or subtle bug within its extensive codebase would directly impact the Math contract and any protocol relying on it. This introduces an inherent dependency risk.I-01

Issue

The Math contract's core functionality for fixed-point arithmetic is entirely dependent on the ABDKMath64x64 library. While ABDKMath64x64 is a well-known and generally robust library, any undiscovered vulnerability or subtle bug within its extensive codebase would directly impact the Math contract and any protocol relying on it. This introduces an inherent dependency risk.

Fix

Ensure that the ABDKMath64x64 library has been thoroughly audited independently and that its specific version used in this project is free from known vulnerabilities. Consider maintaining a local copy of the audited version to prevent unexpected changes from external dependencies.

Status

Unresolved

Info

Truncated log_2 Function in ABDKMath64x64

The provided source code for the ABDKMath64x64.log_2 function is incomplete, indicated by ... (truncated). Without the full implementation, a comprehensive security assessment of this specific function's logic, including potential edge cases, gas consumption, and correctness, cannot be performed.I-02

Issue

The provided source code for the ABDKMath64x64.log_2 function is incomplete, indicated by ... (truncated). Without the full implementation, a comprehensive security assessment of this specific function's logic, including potential edge cases, gas consumption, and correctness, cannot be performed.

Fix

Provide the complete source code for the ABDKMath64x64.log_2 function to allow for a full and thorough audit of its implementation. Verify that the deployed bytecode matches the complete source code.

Status

Unresolved

Analysis

AI Copilotas of audit · Sep 4
Executive SummaryWhat the contract is and what the review found

The audit focused on the Math library, which serves as an implementation for the XENCrypto proxy. The Math contract provides basic utility functions and leverages the well-established ABDKMath64x64 library for fixed-point arithmetic. The contract is stateless and contains no complex logic, access control, or economic mechanisms. The ABDKMath64x64 library employs robust checks to prevent common fixed-point arithmetic issues. Overall, the technical risk is low due to the simplicity and reliance on a battle-tested library.

Technical10/10Low risk

The Math contract (7.1 Architecture) is a simple, stateless library providing min, max, and logX64 functions. Its core functionality for fixed-point arithmetic is delegated to the ABDKMath64x64 library, which is a widely used and generally robust solution for 64.64-bit fixed-point math in Solidity. The ABDKMath64x64 library (7.2 Code Security) incorporates unchecked blocks with explicit require statements to prevent integer overflows/underflows and ensure results remain within the valid fixed-point range. No reentrancy or other common code security vulnerabilities were identified due to the contract's pure nature.

Governance3/10High risk

The Math contract is a pure utility library (7.4 Economic). It does not manage any assets, tokens, or user funds, nor does it implement any economic models or fee structures. Consequently, there are no direct economic risks such as flash loan attacks or oracle manipulation. Similarly, the contract lacks any governance mechanisms (7.5 Governance) or access control (7.3 Access Control), as all its functions are external pure and stateless, meaning no privileged operations exist.

Upgrades6/10Medium risk

The Math contract serves as an implementation behind a proxy (7.7 Upgrades). As a stateless and pure library, it is an ideal candidate for an upgradeable implementation, minimizing upgrade-related risks. Future upgrades to this specific implementation would primarily involve replacing the mathematical logic, which is a low-risk operation given its lack of state. The proxy's upgrade mechanism itself (7.8 Operations) would be the primary point of concern for upgrade safety, but this implementation does not introduce specific upgrade vulnerabilities.

Final RecommendationWhat to do about this score

The Math contract is a well-structured and secure implementation for fixed-point arithmetic, leveraging a reputable third-party library.

It is recommended to ensure that the complete ABDKMath64x64 library, including the truncated log_2 function, has undergone thorough review. For any future upgrades, maintain the stateless and pure nature of the implementation to preserve its low-risk profile.

Contract & Record

1 audit on record
TypeProxy
NetworkEthereum
Token age3y
Contract0x0645…6fb8
Deployer0xa82c…591a
Badge for your website
XEN Crypto security record badge

Free for any token on the record. It links to this page and always shows the current score and the date it was checked.

Audit History
  1. Sep 4, 202613Low

Score changes are recorded as dated snapshots — history is append-only and cannot be edited.

Frequently Asked Questions

What is the XEN contract address?

The XEN Crypto (XEN) contract on Ethereum is 0x06450dee7fd2fb8e39061434babcfc05599a6fb8. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.

Is XEN Crypto a scam?

Quantum Audit's risk score for XEN Crypto is 13/100 (Low risk) as of Sep 4, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; Mint: No mint; Liquidity lock: Not locked; Upgradeability: Fixed code; Honeypot: None found; Buy / sell tax: 0% / 0%. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.

Is XEN liquidity locked?

Liquidity lock: Not locked (as of Sep 4, 2026). Total DEX liquidity: $89.5K.

Who holds XEN?

As of Sep 4, 2026, the 10 largest holders own 18.9% of the supply. The Holders section on this page shows who they are by holder type.

Related Audits

6 more on the recordAll audits
ManyuEthereum13LowRektEthereum13LowWrapped liquid staked Ether 2.0WSTETH · Ethereum12LowEthereumcatETHCAT · Ethereum14LowA Hunters DreamCAW · Ethereum12LowTetherUSDT · Ethereum12Low

Would You Like a More Detailed Audit of XEN Crypto?

Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.

Get Detailed Audit Is this your token? Publish your own audit on this page