On-chain security analysis — is it a scam or legit?
The CoinyeWest contract implements a standard ERC20 token with a fixed supply.
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.
0x159c…b329No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The contract does not include a mechanism to recover accidentally sent ERC20 tokens or native currency (ETH) that might be sent to the contract address. While not directly impacting the core ERC20 functionality, such funds would be permanently locked and inaccessible (7.8 Operations).
Implement a function, callable by a trusted address (e.g., the deployer or a multisig), to withdraw accidentally sent ERC20 tokens or native currency from the contract. This function should include checks to prevent draining legitimate contract balances.
Unresolved
The CoinyeWest token has a fixed total supply of 1,000,000,000 COINYE, all minted to the contract deployer during construction. There are no public functions to mint or burn tokens after deployment (7.4 Economic).
This is a design choice that ensures scarcity and predictability. Confirm that a fixed supply model aligns with the project's long-term economic strategy.
Unresolved
The contract lacks any administrative roles such as an owner, minter, pauser, or blacklister. This design promotes decentralization and immutability (7.3 Access Control, 7.5 Governance).
This design choice eliminates risks associated with centralized control but means there is no mechanism to pause transfers, recover accidentally sent tokens (as noted in L-01), or address potential future issues requiring administrative intervention. Ensure this level of decentralization is desired.
Unresolved
ERC20InsufficientBalance, ERC20InvalidSender) instead of traditional require statements with string messages. This is a modern Solidity best practice (7.2 Code Security).I-03The contract utilizes custom error types (e.g., ERC20InsufficientBalance, ERC20InvalidSender) instead of traditional require statements with string messages. This is a modern Solidity best practice (7.2 Code Security).
This approach improves gas efficiency and provides more structured, machine-readable error information, which is beneficial for dApp integration and debugging. No action required.
Unresolved
unchecked Blocksunchecked blocks for arithmetic operations, specifically for _balances[from] = fromBalance - value;, _balances[to] += value;, and _totalSupply -= value;. In cases of subtraction, prior checks (if (fromBalance < value)) prevent underflow. For addition, uint256 capacity is practically sufficient for the token's scale (7.2 Code Security).I-04The contract employs unchecked blocks for arithmetic operations, specifically for _balances[from] = fromBalance - value;, _balances[to] += value;, and _totalSupply -= value;. In cases of subtraction, prior checks (if (fromBalance < value)) prevent underflow. For addition, uint256 capacity is practically sufficient for the token's scale (7.2 Code Security).
The use of unchecked blocks here is a gas optimization technique and appears to be safe given the context and preceding checks. No action required.
Unresolved
The CoinyeWest contract implements a standard ERC20 token with a fixed supply. The code is well-structured, follows OpenZeppelin patterns, and utilizes modern Solidity features like custom errors. No critical or high-severity vulnerabilities were identified. The design emphasizes decentralization with no administrative roles or upgradeability.
The technical implementation of the CoinyeWest token is robust, adhering closely to the ERC20 standard and OpenZeppelin best practices. The contract effectively uses custom errors for improved gas efficiency and clarity (7.2 Code Security). Arithmetic operations within unchecked blocks are appropriately safeguarded by prior checks, preventing common integer overflow/underflow issues (7.2 Code Security). The architecture is simple and well-defined, with no complex external dependencies (7.1 Architecture). No reentrancy or other common EVM vulnerabilities were found.
The economic model is straightforward: a fixed supply token minted entirely to the deployer at creation (7.4 Economic). There are no governance mechanisms or administrative roles, promoting a highly decentralized and immutable token (7.5 Governance). This design choice eliminates risks associated with centralized control but also removes flexibility for future protocol adjustments or emergency interventions.
The CoinyeWest contract is not designed to be upgradeable, meaning its logic is immutable once deployed (7.7 Upgrades). This eliminates all risks associated with proxy patterns, upgradeability bugs, or malicious upgrades. However, it also means that any discovered bugs or desired feature changes would require a new contract deployment and migration.
The CoinyeWest token is a well-implemented, standard ERC20 contract.
The primary recommendation is to ensure that the fixed supply and lack of administrative control align with the long-term vision for the token, as these design choices are immutable. Consider implementing a mechanism for emergency recovery of accidentally sent funds if this is deemed a necessary safeguard for user experience, although it introduces a minor centralization point.
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 Coinye West (COINYE) contract on Base is 0x0028e1e60167b48a938b785aa5292917e7eaca8b. 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 Coinye West is 9/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: 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: $83.7K.
As of Sep 4, 2026, the 10 largest holders own 33.7% of the supply. The Holders section on this page shows who they are by holder type.
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
