Quantum Audit Logo
Launch App

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

Is Virtual Protocol Safe?

VIRTUALBase
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
SummaryAI Copilot

The OptimismMintableERC20 contract serves as a cross-chain token, combining Optimism's mintable token standard with LayerZero's Omnichain Fungible Token (OFT) functionality.

Read the full analysis
What raised the score
  • Mintable supply — no cap found, dilution unbounded
  • Top-10 concentration > 30%
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 94.9%
  • LP top3 unlocked holders = 100.0%
  • 1 High finding(s) from audit
  • 1 Medium finding(s) from audit
  • 1 Low finding(s) from audit
Exact factors
  • Mintable supply — no cap found, dilution unbounded
  • Top-10 concentration > 30% (46.7% total → 36.9% effective; 30.3% in EOAs, 16.4% in contracts — moderate)
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 94.9% (independent LP — depth risk, pool = 46% of DEX liquidity)
  • LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 46% of DEX liquidity)
  • 1 High finding(s) from audit
  • 1 Medium finding(s) from audit
  • 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

Security Checklist

as of audit · Sep 43 of 5 checks passed
Contract verifiedVerified
OwnershipRenounced
MintMintable
Liquidity lockNot locked
UpgradeabilityFixed code

Holders

as of audit · Sep 4, 2026
16.4%Contracts30.3%Wallets53.3%Everyone else
16.4%Contracts30.3%Wallets53.3%Everyone else
ContractsWalletsEveryone elseBubble area = share of supply
46.7%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking16.4%
  • Walletsanonymous holders, free to sell30.3%
  • Everyone elsethe rest of the supply53.3%
Effective concentrationwhat the score reads36.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 4$9.32M across 30 pairs
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$4.33MShare of depth46.4%
Top-1 Unlocked Holder94.9%
Top-3 Unlocked100.0%
Unlocked LP held by
0xf1c4…71c80xfbc9…a3610x0ff1…7d770x2744…01ca0x3624…147c0xeff4…d00f0xda21…e12f0x46d8…b5b50x06c5…d2b40xceb9…3d6d

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

Security Findings

1 High1 Medium1 Low1 Info
High

Centralized Control over LayerZero Configuration (Owner and Delegate)

The deployer of the OptimismMintableERC20 contract becomes the owner of the inherited OAppCore component and is also set as the delegate for the LayerZero endpoint. This grants significant control over the contract's cross-chain functionality, including the ability to call setPeer (to configure trusted remote OApp instances) and potentially other LayerZero endpoint configurations via the delegate role. A compromise of this single owner/delegate key could lead to misrouting of cross-chain token transfers, denial of service, or other manipulations of the OFT functionality (7.3 Access Control, 7.6 External).H-01

Issue

The deployer of the OptimismMintableERC20 contract becomes the owner of the inherited OAppCore component and is also set as the delegate for the LayerZero endpoint. This grants significant control over the contract's cross-chain functionality, including the ability to call setPeer (to configure trusted remote OApp instances) and potentially other LayerZero endpoint configurations via the delegate role. A compromise of this single owner/delegate key could lead to misrouting of cross-chain token transfers, denial of service, or other manipulations of the OFT functionality (7.3 Access Control, 7.6 External).

Fix

Transfer the ownership of the OAppCore component and the LayerZero delegate role to a robust multi-signature wallet or a DAO. This decentralizes control and significantly reduces the risk associated with a single point of failure.

Status

Unresolved

Medium

Immutability of Critical Bridge Address

The BRIDGE address, which is critical for the mint and burn functions, is declared as immutable and set only during construction. While this prevents unauthorized modification post-deployment, it introduces operational rigidity. If the underlying bridge contract needs to be upgraded, replaced, or if a vulnerability is discovered in the designated bridge, this OptimismMintableERC20 contract would need to be redeployed, potentially requiring a costly and complex token migration process (7.1 Architecture, 7.8 Operations).M-01

Issue

The BRIDGE address, which is critical for the mint and burn functions, is declared as immutable and set only during construction. While this prevents unauthorized modification post-deployment, it introduces operational rigidity. If the underlying bridge contract needs to be upgraded, replaced, or if a vulnerability is discovered in the designated bridge, this OptimismMintableERC20 contract would need to be redeployed, potentially requiring a costly and complex token migration process (7.1 Architecture, 7.8 Operations).

Fix

Acknowledge the implications of the immutable BRIDGE address. For future deployments, consider if a mutable bridge address (managed by a robust governance mechanism) is preferable, or ensure a clear migration strategy is in place for potential bridge upgrades. For the current deployment, ensure the BRIDGE address is thoroughly vetted and secure.

Status

Unresolved

Low

Lack of Robust Ownership Management for LayerZero Configuration

The OAppCore component, which manages LayerZero configurations, is Ownable. The current setup assigns ownership to the contract deployer and does not include a mechanism or explicit recommendation to transfer this ownership to a more secure entity (e.g., a multi-signature wallet or DAO) or to renounce it if no further configuration changes are anticipated. While the deployer's address is initially the owner, relying on a single externally owned account (EOA) for such critical configuration control introduces a single point of failure risk (7.3 Access Control, 7.5 Governance).L-01

Issue

The OAppCore component, which manages LayerZero configurations, is Ownable. The current setup assigns ownership to the contract deployer and does not include a mechanism or explicit recommendation to transfer this ownership to a more secure entity (e.g., a multi-signature wallet or DAO) or to renounce it if no further configuration changes are anticipated. While the deployer's address is initially the owner, relying on a single externally owned account (EOA) for such critical configuration control introduces a single point of failure risk (7.3 Access Control, 7.5 Governance).

Fix

Implement a robust ownership management strategy. Transfer ownership of the OAppCore component to a multi-signature wallet or a DAO immediately after deployment. If no further setPeer or delegate changes are expected, consider renouncing ownership to the zero address, though this would prevent any future configuration adjustments.

Status

Unresolved

Info

Reliance on External Bridge Security

The core functionality of minting and burning tokens is entirely dependent on the security and correct functioning of the BRIDGE contract, whose address is set immutably in the constructor. Any vulnerability, exploit, or malicious action within the designated BRIDGE contract would directly impact the integrity and supply of this OptimismMintableERC20 token (7.6 External).I-01

Issue

The core functionality of minting and burning tokens is entirely dependent on the security and correct functioning of the BRIDGE contract, whose address is set immutably in the constructor. Any vulnerability, exploit, or malicious action within the designated BRIDGE contract would directly impact the integrity and supply of this OptimismMintableERC20 token (7.6 External).

Fix

Ensure that the BRIDGE contract is thoroughly audited, regularly monitored, and maintained to the highest security standards. Users should be aware that the security of this token is intrinsically linked to the security of the external bridge.

Status

Unresolved

Analysis

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

The OptimismMintableERC20 contract serves as a cross-chain token, combining Optimism's mintable token standard with LayerZero's Omnichain Fungible Token (OFT) functionality. The audit identified a high-severity access control issue related to the centralized management of LayerZero configurations, alongside medium and low-severity findings concerning operational rigidity and ownership best practices.

Technical7/10Low risk

The contract leverages well-audited OpenZeppelin and LayerZero libraries, providing a robust foundation for ERC20 and cross-chain functionality. The mint and burn functions are appropriately restricted to the immutable BRIDGE address, enhancing core token supply security (7.3 Access Control, 7.2 Code Security). However, a significant concern arises from the centralized control over LayerZero's setPeer function and the delegate role, which could allow a compromised owner to manipulate cross-chain message routing (7.3 Access Control, 7.6 External).

Governance5/10Medium risk

The economic model relies on the integrity of the BRIDGE contract for token supply management, which is an inherent design dependency (7.4 Economic). The BRIDGE address is immutable, preventing unauthorized changes but introducing rigidity; any future bridge upgrades would necessitate redeployment of this token contract (7.1 Architecture). Furthermore, the deployer's control over LayerZero's setPeer and delegate roles presents a centralized governance risk for cross-chain operations (7.5 Governance).

Upgrades6/10Medium risk

The contract is not designed with an upgradeability pattern (e.g., proxy), meaning its logic cannot be modified post-deployment. While this eliminates upgrade-specific risks like proxy misconfigurations or logic bugs during upgrades (7.7 Upgrades), it also means that any future changes, bug fixes, or necessary updates to the OptimismMintableERC20 or its BRIDGE dependency would require a complete redeployment and migration of token holders, incurring significant operational overhead (7.8 Operations).

Final RecommendationWhat to do about this score

It is strongly recommended to transfer the ownership of the OAppCore component and the LayerZero delegate role to a robust multi-signature wallet or a decentralized autonomous organization (DAO) to mitigate the single point of failure identified in the LayerZero configuration.

Additionally, consider implementing a clear operational plan for potential future bridge upgrades, acknowledging the immutability of the BRIDGE address and the implications for token migration. Regular security reviews of the external BRIDGE contract are also advised due to the direct dependency on its security.

Contract & Record

1 audit on record
TypeToken
NetworkBase
Token age2y
Contract0x0b3e…7e1b
Deployer0x97cf…90a3
Badge for your website
Virtual Protocol 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, 202635Medium
  2. Aug 7, 202636Medium

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

Frequently Asked Questions

What is the VIRTUAL contract address?

The Virtual Protocol (VIRTUAL) contract on Base is 0x0b3e328455c4059eeb9e3f84b5543f74e24e7e1b. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.

Is Virtual Protocol a scam?

Quantum Audit's risk score for Virtual Protocol is 35/100 (Medium risk) as of Sep 4, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; Ownership: Renounced; Mint: Mintable; 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 VIRTUAL liquidity locked?

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

Who holds VIRTUAL?

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

Would You Like a More Detailed Audit of Virtual Protocol?

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