Early-stage security check — honeypot & rug-pull analysis
This audit report is based on an unverified contract address where the source code was not provided.
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 risk score reads depth across every pair.
The LP tokens of the analysed pool are locked or burned.
The source code for the contract at was not provided or verified on the block explorer. This prevents any form of static analysis, dynamic testing, or manual review to identify vulnerabilities (7.2 Code Security). Without source code, the contract's intended functionality and security posture cannot be independently confirmed, posing a significant trust and transparency issue.
Always verify contract source code on block explorers. This allows for public scrutiny, independent audits, and user confidence in the contract's operations. Projects should prioritize transparency by publishing their code.
Unresolved
The contract is owned by an Externally Owned Account (EOA) . Without source code, the extent of control this owner has over critical functions (e.g., pausing, upgrading, fee changes, fund withdrawals) is unknown (7.3 Access Control). This poses a potential centralization risk, as a single entity could unilaterally execute privileged operations, potentially leading to censorship, fund manipulation, or other malicious actions.
Implement multi-signature wallets (e.g., Gnosis Safe) or decentralized governance mechanisms for critical administrative functions. This distributes control, reduces single points of failure, and enhances the security and trustlessness of the protocol.
Unresolved
Smart contracts often interact with other contracts, such as oracles, token contracts, or other DeFi protocols. Without source code, it's impossible to identify these external dependencies, assess their security, or understand the potential cascading risks from vulnerabilities in integrated protocols (7.6 External). This lack of visibility prevents a comprehensive risk assessment of the contract's broader ecosystem interactions.
Clearly document all external dependencies and their respective contract addresses, functionalities, and security audit statuses. Ensure that all integrated protocols are robust, well-audited, and have strong security track records to minimize exposure to external risks.
Unresolved
This audit report is based on an unverified contract address where the source code was not provided. Therefore, a comprehensive security analysis for vulnerabilities, economic risks, or upgradeability concerns could not be performed. All risk levels are set to Low as no specific issues could be identified without code. Users should exercise extreme caution when interacting with unverified contracts.
Without access to the contract's source code, a technical security analysis (7.1 Architecture, 7.2 Code Security, 7.3 Access Control) cannot be performed. This prevents the identification of common vulnerabilities such as reentrancy, integer overflows, or logic errors. The lack of transparency significantly hinders any assessment of the contract's internal mechanisms and security posture, making it impossible to confirm adherence to secure coding practices.
An assessment of economic (7.4 Economic) and governance (7.5 Governance) risks is not possible without understanding the contract's functionality and tokenomics. The presence of an EOA owner () introduces a potential centralization risk, as a single entity controls critical functions. Without source code, the extent of this control and its implications for economic stability and governance remain unknown.
The contract's upgradeability status (7.7 Upgrades) is unknown as no source code was provided and is_proxy is false. Without this information, it's impossible to determine if the contract can be modified, which patterns are used (e.g., UUPS, Transparent), or what risks might be associated with potential upgrades. This lack of clarity impacts long-term security and maintainability, as future changes cannot be predicted or audited.
For any smart contract deployment, it is crucial to verify the source code on block explorers to ensure transparency and allow for public scrutiny.
Users should exercise extreme caution when interacting with unverified contracts, as their functionality and security cannot be independently confirmed. A full security audit requires complete access to the contract's source code and deployment configuration to identify and mitigate potential risks effectively.
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 Opal contract on Base is 0x119b63b1605be3a8ff4543c7f76f7f1f79eecd1f. 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 Opal is 36/100 (Medium risk) as of Sep 4, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; Ownership: Retained; Mint: No mint; Liquidity lock: Locked; Upgradeability: Fixed code; Honeypot: None found; Buy / sell tax: 5% / 5%. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.
Liquidity lock: Locked (as of Sep 4, 2026). Total DEX liquidity: $2.77M.
As of Sep 4, 2026, the 10 largest holders own 80.7% of the supply. 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? Publish your own audit on this page
