Quantum Audit Logo
Launch App

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

Is MEET48 Token Safe?

IDOLBNB Chain
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/10Governance2/10Upgrades6/10Checks passed3 of 5Findings3 Info3
SummaryAI Copilot

The Meet contract is a standard ERC-20 token implementation, inheriting directly from OpenZeppelin's battle-tested ERC20 library.

Read the full analysis
What raised the score
  • Ownership status UNKNOWN
  • Top-10 concentration > 30%
  • 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%
Exact factors
  • Ownership status UNKNOWN (owner could not be resolved)
  • Top-10 concentration > 30% (80.5% total → 39.5% effective; 12.1% in EOAs, 68.4% in contracts — moderate)
  • 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)

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 43 of 5 checks passed
Contract verifiedVerified
OwnershipUnknown
MintNo mint
Liquidity lockNot locked
UpgradeabilityFixed code

Holders

as of audit · Sep 4, 2026
68.4%Contracts12.1%Wallets19.5%Everyone else
68.4%Contracts12.1%19.5%Everyone else
ContractsWalletsEveryone elseBubble area = share of supply
80.5%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking68.4%
  • Walletsanonymous holders, free to sell12.1%
  • Everyone elsethe rest of the supply19.5%
Effective concentrationwhat the score reads39.5%
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$977.7K across 6 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$977.7KShare of depth100.0%
Top-1 Unlocked Holder100.0%
Top-3 Unlocked100.0%
Unlocked LP held by
0xd782…d5dc0x6458…2df5

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

Security Findings

3 Info
Info

Centralized Initial Token Distribution

The Meet contract's constructor mints the entire maxSupply and distributes it to nine predefined addresses. This design choice results in a highly centralized initial token distribution, where a significant portion of the total supply is held by a small number of entities. While not a direct code vulnerability, it introduces a potential economic risk (7.4 Economic) if these addresses are compromised or act maliciously.I-01

Issue

The Meet contract's constructor mints the entire maxSupply and distributes it to nine predefined addresses. This design choice results in a highly centralized initial token distribution, where a significant portion of the total supply is held by a small number of entities. While not a direct code vulnerability, it introduces a potential economic risk (7.4 Economic) if these addresses are compromised or act maliciously.

Fix

Project stakeholders should be aware of the implications of this centralized distribution. Implement robust security measures for the private keys controlling these initial recipient addresses. Consider multi-signature wallets or cold storage for significant holdings.

Status

Unresolved

Info

Immutability and Lack of Upgradeability

The Meet contract is deployed as an immutable contract and does not incorporate any upgradeability patterns (7.7 Upgrades). This means that once deployed, its logic cannot be modified or patched. While this provides certainty and eliminates upgrade-related risks, any discovered vulnerabilities or desired feature enhancements would necessitate deploying a new contract and migrating assets, which can be a complex and costly process.I-02

Issue

The Meet contract is deployed as an immutable contract and does not incorporate any upgradeability patterns (7.7 Upgrades). This means that once deployed, its logic cannot be modified or patched. While this provides certainty and eliminates upgrade-related risks, any discovered vulnerabilities or desired feature enhancements would necessitate deploying a new contract and migrating assets, which can be a complex and costly process.

Fix

Acknowledge that the contract's immutability means no future code changes are possible. Ensure thorough testing and auditing are completed pre-deployment to minimize the risk of undiscovered vulnerabilities. Plan for potential migration strategies in case a critical issue arises.

Status

Unresolved

Info

No Administrative Control or Pause Mechanism

The Meet contract is a pure ERC-20 token without any additional administrative roles (e.g., owner, pauser, minter) or functions (7.3 Access Control, 7.8 Operations). This means there is no central entity capable of pausing transfers, blacklisting addresses, or performing further minting/burning beyond standard ERC-20 operations. While this decentralizes control and prevents malicious administrative actions, it also means there is no mechanism to respond to emergencies (e.g., a major exploit or hack) by pausing the contract or freezing funds.I-03

Issue

The Meet contract is a pure ERC-20 token without any additional administrative roles (e.g., owner, pauser, minter) or functions (7.3 Access Control, 7.8 Operations). This means there is no central entity capable of pausing transfers, blacklisting addresses, or performing further minting/burning beyond standard ERC-20 operations. While this decentralizes control and prevents malicious administrative actions, it also means there is no mechanism to respond to emergencies (e.g., a major exploit or hack) by pausing the contract or freezing funds.

Fix

Understand that the lack of administrative control means the token's operations are entirely permissionless after deployment. This design choice prioritizes decentralization over emergency response capabilities. Ensure the project's risk management strategy accounts for this immutability of control.

Status

Unresolved

Analysis

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

The Meet contract is a standard ERC-20 token implementation, inheriting directly from OpenZeppelin's battle-tested ERC20 library. Its primary function is to define a fixed total supply and distribute all tokens to a set of predefined addresses during deployment. The contract is immutable and lacks any administrative functions, ensuring a high degree of decentralization post-deployment. No critical or high-severity vulnerabilities were identified.

Technical10/10Low risk

The Meet contract is a straightforward ERC-20 implementation, leveraging the highly secure and audited OpenZeppelin ERC20 library (7.2 Code Security). This significantly reduces the risk of common vulnerabilities like reentrancy or integer overflows. The contract's architecture (7.1 Architecture) is simple, with all token minting occurring solely within the constructor, ensuring a fixed total supply and preventing unauthorized inflation. There are no complex external interactions or administrative functions (7.3 Access Control), further simplifying the attack surface.

Governance2/10High risk

The token's economic model (7.4 Economic) is simple: a fixed total supply of 4.8 billion tokens, with all tokens minted and distributed to nine specific addresses during deployment. This ensures no further inflation or deflation mechanisms are possible. While this initial distribution centralizes a significant portion of the supply among these addresses, the contract itself lacks any governance mechanisms (7.5 Governance) or administrative controls that could be exploited. The immutability of the contract also prevents any future changes to its economic rules.

Upgrades6/10Medium risk

The Meet contract is not designed to be upgradeable (7.7 Upgrades). It is deployed as a standard, immutable contract, meaning its logic cannot be altered post-deployment. This eliminates all risks associated with upgrade mechanisms, such as proxy implementation bugs or malicious upgrade paths. While this provides certainty, it also means any discovered vulnerabilities would require a new contract deployment and migration, which can be a complex process.

Final RecommendationWhat to do about this score

Ensure all initial recipient addresses are correct and secure before deployment, as the token distribution is immutable.

Given the contract's simplicity and reliance on OpenZeppelin, focus on external factors such as the security of the addresses holding the initial token supply and the broader ecosystem interactions. Thoroughly test all integrations with external platforms.

Contract & Record

1 audit on record
TypeToken
NetworkBNB Chain
Token age1y
Contract0x3b4d…ab07
Deployer0x07af…9d9d
Badge for your website
MEET48 Token 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, 202623Low
  2. Aug 11, 202621Low

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

Frequently Asked Questions

What is the IDOL contract address?

The MEET48 Token (IDOL) contract on BNB Chain is 0x3b4de3c7855c03bb9f50ea252cd2c9fa1125ab07. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.

Is MEET48 Token a scam?

Quantum Audit's risk score for MEET48 Token is 23/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. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.

Is IDOL liquidity locked?

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

Who holds IDOL?

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

Related Audits

6 more on the recordAll audits
binanceus doodlesBOODLES · BNB Chain23LowMarsCoinBNB Chain23LowChainGPTCGPT · BNB Chain23Low妖蝶BNB Chain22LowZygoSwapZSWAP · BNB Chain21LowThe Final Form BullCZ · BNB Chain25Low

Would You Like a More Detailed Audit of MEET48 Token?

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