Quantum Audit Logo

Is World of Dypians Safe?

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

Is this your token? Publish your own audit on this page →

World of Dypians WOD
0xb994…b0e8
BNB Chain Not verifiedLast checked 3d ago 1 audit on record
Executive SummaryAI Copilot

The WorldOfDypians token contract is a standard ERC-20 implementation, inheriting from well-audited OpenZeppelin contracts. It features a fixed maximum supply, with all tokens minted to a designated lock address during deployment. The contract exhibits robust code quality and adheres to common security practices, with no critical or high-severity vulnerabilities identified. Minor findings relate to design choices regarding token distribution and immutability.

1 Low2 Informational
Volume 24h
$346.5K
Liquidity
$258.2K
Price
$0.003606
Token Age
1y
Top 10 Holders
75.4%

Security Findings

Low

Centralized Control of Initial Supply

L-01The entire `MAX_SUPPLY` of WorldOfDypians tokens is minted to a single `tokenLockAddress` (0x3589…3890) during contract deployment. This design choice centralizes control over the initial token distribution to the entity managing this specific address. Any compromise, mismanagement, or single point of failure associated with the `tokenLockAddress` could significantly impact the entire token supply and its intended distribution (7.3 Access Control, 7.4 Economic, 7.6 External).
IssueThe entire `MAX_SUPPLY` of WorldOfDypians tokens is minted to a single `tokenLockAddress` () during contract deployment. This design choice centralizes control over the initial token distribution to the entity managing this specific address. Any compromise, mismanagement, or single point of failure associated with the `tokenLockAddress` could significantly impact the entire token supply and its intended distribution (7.3 Access Control, 7.4 Economic, 7.6 External).
FixImplement robust security measures for the `tokenLockAddress`, such as a multi-signature wallet or a time-locked contract, to distribute control and reduce the risk of a single point of failure. Clearly communicate the purpose and management of this address to stakeholders.
StatusUnresolved
Info

Immutable Token Supply

I-01The WorldOfDypians token contract implements a fixed token supply model. After the initial minting of `MAX_SUPPLY` tokens to the `tokenLockAddress` in the constructor, there are no public or internal functions available to mint additional tokens or burn existing ones. This design makes the total token supply immutable, preventing any future inflation or deflation through contract-level operations (7.4 Economic).
IssueThe WorldOfDypians token contract implements a fixed token supply model. After the initial minting of `MAX_SUPPLY` tokens to the `tokenLockAddress` in the constructor, there are no public or internal functions available to mint additional tokens or burn existing ones. This design makes the total token supply immutable, preventing any future inflation or deflation through contract-level operations (7.4 Economic).
FixNo action is required if a fixed supply is the intended economic model. Ensure this design choice is clearly communicated in the project's documentation and whitepaper.
StatusUnresolved
Info

Hardcoded `tokenLockAddress`

I-02The `tokenLockAddress` (0x3589…3890) is defined as a `public constant` within the contract. While this ensures the address cannot be changed after deployment, it also introduces inflexibility. If the intended recipient or the strategy for managing the initial token supply needs to change in the future, it would necessitate deploying an entirely new contract (7.1 Architecture).
IssueThe `tokenLockAddress` () is defined as a `public constant` within the contract. While this ensures the address cannot be changed after deployment, it also introduces inflexibility. If the intended recipient or the strategy for managing the initial token supply needs to change in the future, it would necessitate deploying an entirely new contract (7.1 Architecture).
FixNo action is required if immutability of the lock address is the intended design. For future projects requiring flexibility, consider making such critical addresses configurable via constructor arguments or an owner-controlled setter function, if appropriate for the project's risk model.
StatusUnresolved

Category Ratings

TechnicalLow10/10

The technical implementation of the WorldOfDypians token is based on battle-tested OpenZeppelin ERC20 and Ownable contracts, ensuring a high standard of code security (7.2 Code Security). The use of Solidity 0.8.20 provides default overflow/underflow protection, and `unchecked` blocks are used appropriately where safety is guaranteed. No reentrancy vectors or other common EVM vulnerabilities were identified (7.2 Code Security). The architecture is straightforward, implementing a basic token with a fixed supply (7.1 Architecture).

GovernanceMedium6/10

The contract utilizes the Ownable pattern for administrative control, allowing the owner to transfer or renounce ownership (7.3 Access Control). However, the owner has no control over the token supply after deployment, as there are no minting or burning functions (7.4 Economic). The entire `MAX_SUPPLY` is minted to a `tokenLockAddress` in the constructor, centralizing initial distribution control to that address (7.4 Economic, 7.5 Governance). This design ensures a fixed token supply, preventing inflationary risks from arbitrary minting.

UpgradesLow9/10

The WorldOfDypians contract is not designed as an upgradeable proxy. It is a standard, non-upgradeable implementation, meaning its logic cannot be modified after deployment (7.7 Upgrades). Any future changes to the token's functionality would require deploying a new contract.

Security Checklist

Contract VerifiedPass
Ownership RenouncedPass
No Mint FunctionPass
Liquidity LockedFail
Not a ProxyPass
HoneypotNoneBuy Tax0.0%Sell Tax0.0%

Holder Composition

0.0% in wallets75.4% in contracts
Effective Concentration30.2%

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.

Liquidity Depth

The risk score reads depth across every pair. The volume figure and the volume-to-liquidity ratio elsewhere on this page describe only the pair this audit analysed, so the two are not directly comparable.

LP Distribution

Top-1 Unlocked Holder100.0%
Top-3 Unlocked100.0%

Key Addresses

Deployer
0xb57a…1ea4
Unlocked LP Held By
0xd5d4…d492

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

What Raised This Score

  • Top-10 concentration > 30% (75.4% total → 30.2% effective; 0.0% in EOAs, 75.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, pool = 99% of DEX liquidity)
  • LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 99% of DEX liquidity)
  • 1 Low 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

Related Audits

Cubus Store Coin (CSC)Low RiskLiability Vortex (LVTR)Low RiskARIA.AI (ARIA)Low RiskBroccoliLow RiskMomentum (MNTM)Low RiskFrippyLow Risk

Would You Like a More Detailed Audit of World of Dypians?

Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.

Get Detailed Audit