The LOOP token contract is a fixed-supply ERC20 token built upon OpenZeppelin's battle-tested implementation. Its primary function is to mint the entire supply to a designated 'lending hook' address during deployment and allow users to burn their own tokens. The contract itself is minimal and well-structured. However, the critical risk lies in the complete centralization of the initial token supply to a single external address, making the security of this 'lending hook' paramount for the entire protocol's integrity.

On-chain security analysis — is it a scam or legit?
Is LO0P Safe?
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 →The LOOP token contract is a fixed-supply ERC20 token built upon OpenZeppelin's battle-tested implementation.
Read the full analysis- Ownership status UNKNOWN
- Top-10 concentration > 20%
- Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
- LP top1 unlocked holder = 100.0%
- LP top3 unlocked holders = 100.0%
- 1 High finding(s) from audit
Exact factors
- Ownership status UNKNOWN (owner could not be resolved)
- Top-10 concentration > 20% (68.1% total → 27.2% effective; 0.0% in EOAs, 68.1% in contracts — mild)
- Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
- LP top1 unlocked holder = 100.0% (independent LP — depth risk)
- LP top3 unlocked holders = 100.0% (independent LP — depth risk)
- 1 High 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 4Holders
as of audit · Sep 4, 2026- Contractstreasury, vesting, bridge, staking68.1%
- Everyone elsethe rest of the supply31.9%
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 4The 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.
0xf9fd…f90fNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
Security Findings
HighCentralization of Initial Supply and External Dependency Risk
The entire TOTAL_SUPPLY of 1,000,000 LO0P tokens is minted to a single mintTo address in the constructor. The contract description identifies this address as a 'lending hook'. This design choice makes the security and integrity of the mintTo address (and the associated 'lending hook' contract) paramount, as it represents a single point of failure for the entire token supply. Any vulnerability, compromise, or mismanagement in the 'lending hook' contract could lead to the loss or misuse of all LO0P tokens. This impacts 7.1 Architecture, 7.3 Access Control, 7.6 External, and 7.8 Operations.H-01
Issue
The entire TOTAL_SUPPLY of 1,000,000 LO0P tokens is minted to a single mintTo address in the constructor. The contract description identifies this address as a 'lending hook'. This design choice makes the security and integrity of the mintTo address (and the associated 'lending hook' contract) paramount, as it represents a single point of failure for the entire token supply. Any vulnerability, compromise, or mismanagement in the 'lending hook' contract could lead to the loss or misuse of all LO0P tokens. This impacts 7.1 Architecture, 7.3 Access Control, 7.6 External, and 7.8 Operations.
Fix
A thorough security audit of the 'lending hook' contract (the mintTo address) is critically important to ensure robust security, proper access controls, and resilience against common attack vectors. Consider implementing multi-signature control, time-locks, or other decentralized governance mechanisms for critical operations within the lending hook, especially those involving large token movements or administrative changes.
Status
Unresolved
InfoFixed Supply and No Further Minting
The LOOP token has a TOTAL_SUPPLY constant of 1,000,000 * 1e18 tokens, all minted during construction to the mintTo address. There are no functions or mechanisms to mint additional tokens after deployment. This design choice ensures a fixed and predictable supply, preventing inflationary pressures from arbitrary minting. This relates to 7.4 Economic.I-01
Issue
The LOOP token has a TOTAL_SUPPLY constant of 1,000,000 * 1e18 tokens, all minted during construction to the mintTo address. There are no functions or mechanisms to mint additional tokens after deployment. This design choice ensures a fixed and predictable supply, preventing inflationary pressures from arbitrary minting. This relates to 7.4 Economic.
Fix
This is an intentional design choice that enhances transparency and predictability for token holders. No specific security recommendation is needed, but stakeholders should be fully aware of the implications of a fixed supply model.
Status
Unresolved
InfoUse of OpenZeppelin Standard
The LOOP contract inherits from OpenZeppelin's ERC20 contract, which is a widely audited, community-vetted, and industry-standard implementation of the ERC-20 token specification. This significantly reduces the risk of common ERC-20 vulnerabilities and enhances the overall reliability and security of the token. This relates to 7.2 Code Security.I-02
Issue
The LOOP contract inherits from OpenZeppelin's ERC20 contract, which is a widely audited, community-vetted, and industry-standard implementation of the ERC-20 token specification. This significantly reduces the risk of common ERC-20 vulnerabilities and enhances the overall reliability and security of the token. This relates to 7.2 Code Security.
Fix
Continue to monitor OpenZeppelin's official channels for any updates or security advisories related to the specific version of contracts used (implied v5.5.0). While highly secure, no library is entirely immune to future discoveries.
Status
Unresolved
InfoPublic Burn Function
The burn function is declared as external and allows any user to burn tokens from their own balance (msg.sender). The contract description also notes that the 'lending hook' contract is intended to call this function for liquidations on tokens it holds. This functionality is a common feature in many token designs, allowing users to voluntarily reduce the circulating supply. This relates to 7.3 Access Control and 7.4 Economic.I-03
Issue
The burn function is declared as external and allows any user to burn tokens from their own balance (msg.sender). The contract description also notes that the 'lending hook' contract is intended to call this function for liquidations on tokens it holds. This functionality is a common feature in many token designs, allowing users to voluntarily reduce the circulating supply. This relates to 7.3 Access Control and 7.4 Economic.
Fix
This is an intended feature. Ensure that users understand the irreversible nature of burning tokens. For the 'lending hook' contract, ensure its logic for calling burn is secure and aligns with its intended liquidation mechanisms.
Status
Unresolved
Analysis
AI Copilotas of audit · Sep 4The LOOP contract demonstrates high technical quality, inheriting from OpenZeppelin's robust ERC20 implementation (7.2 Code Security). It includes a basic burn function for user-initiated token destruction and a constructor that mints the entire fixed supply to a single address. The primary technical risk (7.1 Architecture, 7.6 External) stems from the complete reliance on the security of the external 'lending hook' contract, which receives the entire token supply at deployment. No reentrancy or integer overflow issues were identified within the contract's custom logic.
The economic model of LOOP is characterized by a fixed total supply with no further minting capabilities (7.4 Economic), promoting scarcity and predictability. There is no team allocation, enhancing trust. However, the entire initial supply is transferred to a single 'lending hook' address during deployment (7.4 Economic, 7.5 Governance). This centralization of the initial token distribution creates a significant economic and governance risk, as the security and operational integrity of this single address dictate the safety of all tokens.
The LOOP token contract is not designed to be upgradeable (7.7 Upgrades). It does not implement any proxy patterns (e.g., UUPS, Transparent, Beacon), meaning its logic is immutable once deployed. This eliminates upgrade-related risks such as proxy misconfigurations or malicious upgrade paths.
The primary security concern for the LOOP token lies with the external 'lending hook' contract that receives the entire initial token supply.
It is imperative to conduct a comprehensive security audit of this 'lending hook' contract to ensure its robustness against all potential attack vectors. Implement strong access controls, multi-signature mechanisms, and potentially time-locks for any critical operations within the 'lending hook' that manage the LO0P tokens. Additionally, ensure clear documentation and transparency regarding the 'lending hook's' functionality and security measures.
Contract & Record
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
- Jul 31, 202637Medium
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Frequently Asked Questions
What is the LO0P contract address?
The LO0P contract on Ethereum is 0x00000000000050806673b532d7486ac114c1de3f. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.
Is LO0P a scam?
Quantum Audit's risk score for LO0P is 37/100 (Medium 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. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.
Is LO0P liquidity locked?
Liquidity lock: Not locked (as of Sep 4, 2026). Total DEX liquidity: $271.6K.
Who holds LO0P?
As of Sep 4, 2026, the 10 largest holders own 68.1% of the supply. The Holders section on this page shows who they are by holder type.
Would You Like a More Detailed Audit of LO0P?
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