On-chain security analysis — is it a scam or legit?
This audit report is based on the analysis of a contract address on the Base network without access to its verified source code.
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 Sep 4, 2026
The 15 remaining pairs hold $13.2K between them and are not listed. The risk score reads depth across every pair.
The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.
0x39a3…98c10xa928…faea0x24dc…0cbe0xa19f…7b6a0x603b…b3a30x3a8b…6e860x62ce…5c8a0x4a4c…9cc70x31f9…9eda0x5810…8eafNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The source code for the contract at is not verified on the block explorer. This prevents any form of security analysis, architectural review (7.1 Architecture), or code security assessment (7.2 Code Security). Users cannot independently verify the contract's intended functionality or identify potential vulnerabilities.
Verify the contract's source code on the block explorer. This is a fundamental step for transparency and allows for proper security auditing and community trust.
Unresolved
Without source code, the access control mechanisms (7.3 Access Control) governing critical functions are unknown. It is impossible to ascertain if administrative privileges are properly secured, if a multi-signature wallet is used, or if there are any single points of failure. This lack of visibility poses a significant risk, as an attacker could potentially exploit weak access controls if they exist.
Implement robust access control mechanisms, preferably using a multi-signature wallet for critical operations. Clearly document and verify these controls within the source code to ensure transparency and security.
Unresolved
The economic model, fee structures, and tokenomics (7.4 Economic) of the contract cannot be verified without source code. This includes understanding how value is accrued, distributed, or if there are any mechanisms for inflation/deflation. The absence of this information makes it impossible to assess potential economic exploits or long-term sustainability, impacting user trust and investment decisions.
Clearly define and document the economic model and tokenomics within the contract's source code and external documentation. Ensure that all financial flows and asset management logic are transparent and auditable.
Unresolved
This audit report is based on the analysis of a contract address on the Base network without access to its verified source code. Consequently, a comprehensive security assessment of the contract's logic, architecture, and potential vulnerabilities could not be performed. The risk levels assigned reflect the inherent uncertainty and lack of transparency due to the absence of source code.
Without access to the contract's source code, a detailed technical analysis (7.1 Architecture, 7.2 Code Security) is impossible. The contract's internal logic, state variables, and function implementations remain unknown, preventing any assessment of common vulnerabilities like reentrancy, integer overflows, or access control flaws (7.3 Access Control). For example, it is impossible to determine if critical functions are properly protected or if external calls are handled securely (7.6 External). This lack of transparency introduces significant technical risk.
The economic model and governance mechanisms (7.4 Economic, 7.5 Governance) of the contract cannot be determined without source code. It is unknown how assets are managed, if there are any fees, or if the contract interacts with oracles (7.6 External) that could be manipulated. The absence of a clear governance structure means that critical decisions or parameter changes could be made without community oversight, posing a high risk to users. For instance, potential backdoors or privileged functions cannot be identified.
The upgradeability status of the contract (7.7 Upgrades) is unknown without source code. It is impossible to determine if the contract employs a proxy pattern (e.g., UUPS, Transparent) or if it is immutable. If it is upgradeable, the mechanisms for upgrades, such as multi-signature requirements or time locks, are not verifiable. This introduces a high risk, as an unverified upgrade mechanism could allow malicious changes to the contract's logic, impacting user funds and trust. The operational procedures (7.8 Operations) for any potential upgrades are also entirely opaque.
For any interaction with this contract, it is strongly recommended to await the verification of its source code on block explorers.
Without verified source code, users cannot independently audit or understand the contract's behavior, making any interaction inherently risky. Protocols should always publish and verify their smart contract source code to ensure transparency and allow for community and professional security review.
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 NVIDIA Corporation (NVDAC) contract on Base is 0xb20000000000000000000078ee7ce2fe4908108c. 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 NVIDIA Corporation is 21/100 (Low risk) as of Sep 4, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; 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.
Liquidity lock: Not locked (as of Sep 4, 2026). Total DEX liquidity: $2.73M.
As of Sep 4, 2026, the 10 largest holders own 58.1% of the supply. The Holders section on this page shows who they are by holder type.
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
