Early-stage security check — honeypot & rug-pull analysis
No Solidity source code was provided for analysis. Therefore, a comprehensive security audit could not be performed.
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.
0x1d2a…158cNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The Solidity source code for the contract at is not publicly verified on the Arbitrum block explorer. This prevents any form of static analysis or manual code review.
Verify the Solidity source code on the block explorer. This increases transparency and allows for community and professional security audits.
Unresolved
Without access to the source code, the exact purpose, logic, and intended functionality of the contract cannot be determined. This makes it impossible to assess its adherence to specifications or identify logical flaws.
Provide the source code and a clear specification or documentation outlining the contract's intended behavior and business logic.
Unresolved
Critical technical vulnerabilities such as reentrancy, integer overflows/underflows, denial-of-service vectors, or improper input validation cannot be identified or ruled out without the source code (7.2 Code Security).
A full technical security audit, including static analysis and manual review, should be performed once the source code is made available.
Unresolved
The contract's access control mechanisms (7.3 Access Control), potential for economic manipulation (7.4 Economic), or governance structures (7.5 Governance) cannot be evaluated. This includes risks like centralized control, oracle manipulation, or flash loan vulnerabilities.
Provide source code and documentation detailing access control roles, economic models, and governance processes for a comprehensive review.
Unresolved
The contract's upgradeability pattern (7.7 Upgrades), if any, and operational aspects such as pausing mechanisms or emergency procedures (7.8 Operations) are unknown. This prevents an assessment of potential upgrade safety issues or operational single points of failure.
Clarify the contract's upgradeability status and operational procedures through source code and documentation to allow for a proper risk assessment.
Unresolved
No Solidity source code was provided for analysis. Therefore, a comprehensive security audit could not be performed. The assessment is based solely on the provided metadata, and no specific vulnerabilities can be identified or ruled out. Users should exercise extreme caution when interacting with unverified contracts.
Without access to the Solidity source code, a technical security assessment (7.1 Architecture, 7.2 Code Security, 7.3 Access Control) cannot be conducted. No specific vulnerabilities related to reentrancy, integer overflows, or access control flaws can be identified or ruled out. The contract's functionality and security mechanisms remain unknown, making it impossible to evaluate its robustness or adherence to secure coding practices.
An economic and governance risk assessment (7.4 Economic, 7.5 Governance) is not possible without understanding the contract's logic, tokenomics, or administrative structures. Potential risks such as oracle manipulation, flash loan vulnerabilities, or centralized control cannot be evaluated. External dependencies (7.6 External) are also unknown, preventing an analysis of potential cascading failures or reliance on untrusted protocols.
The upgradeability status (7.7 Upgrades) of the contract cannot be determined without source code. It is unknown if the contract employs a proxy pattern (e.g., UUPS, Transparent) or if its logic is immutable. Operational risks (7.8 Operations) related to pausing, emergency shutdowns, or administrative key management are also unknown, leaving potential points of failure or centralized control unaddressed.
It is strongly recommended to verify the Solidity source code for this contract on a block explorer to enable a thorough security audit.
Without verified source code, users interact with this contract at their own risk, as its functionality and potential vulnerabilities are opaque. Always ensure that any smart contract you interact with has publicly available and verified source code to allow for community review and security assessment.
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 Catena Labs (CATE) contract on Arbitrum is 0x53abf0a712787f28a44d4d5fddb7e5c98067ca42. 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 Catena Labs is 80/100 (High risk) as of Sep 4, 2026, computed by a deterministic function from on-chain facts — Contract verified: Not verified; Liquidity lock: Locked; Upgradeability: Fixed code. 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: $80.6K.
As of Sep 4, 2026, the 10 largest holders own 93.5% 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