Quantum Audit Logo
Launch App

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

Is RaveDAO Safe?

RAVEBase
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
Medium RiskHow is this score calculated?
How the score breaks downratings: 10 is safest
Technical8/10Governance1/10Upgrades7/10Checks passed3 of 5Findings1 Low · 3 Info4
SummaryAI Copilot

The RaveToken contract is an Omnichain Fungible Token (OFT) built on LayerZero v2, inheriting from OpenZeppelin's Ownable.

Read the full analysis
What raised the score
  • Ownership not renounced — strong Multisig
  • Top-10 concentration > 70%
  • 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 Low finding(s) from audit
Exact factors
  • Ownership NOT renounced — strong Multisig (3-of-5)
  • Top-10 concentration > 70% (81.7% total → 81.7% effective; 81.7% in EOAs, 0.0% in contracts — extreme)
  • 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 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
OwnershipRetained
MintNo mint
Liquidity lockNot locked
UpgradeabilityFixed code

Holders

as of audit · Sep 4, 2026
81.7%Wallets18.3%Everyone else
81.7%Wallets18.3%Everyone else
WalletsEveryone elseBubble area = share of supply
81.7%of supply sits with the top 10 holders
  • Walletsanonymous holders, free to sell81.7%
  • Everyone elsethe rest of the supply18.3%
Effective concentrationwhat the score reads81.7%
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$162.9K across 3 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$162.9KShare of depth100.0%
Top-1 Unlocked Holder100.0%
Top-3 Unlocked100.0%
Unlocked LP held by
0x8815…288b

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

Security Findings

1 Low3 Info
Low

Centralization Risk of Owner

The RaveToken contract inherits Ownable, granting significant administrative control to a single owner address. This owner, even if a multisig, has the ability to configure critical LayerZero parameters (e.g., setTrustedRemoteAddress, setPeer, setMinDstGas, setFeeManager) through the inherited OFT functions. A compromise of the multisig or malicious intent by its signers could lead to operational issues, unexpected cross-chain transfer fees, or disruption of token bridging functionality (7.3 Access Control, 7.8 Operations).L-01

Issue

The RaveToken contract inherits Ownable, granting significant administrative control to a single owner address. This owner, even if a multisig, has the ability to configure critical LayerZero parameters (e.g., setTrustedRemoteAddress, setPeer, setMinDstGas, setFeeManager) through the inherited OFT functions. A compromise of the multisig or malicious intent by its signers could lead to operational issues, unexpected cross-chain transfer fees, or disruption of token bridging functionality (7.3 Access Control, 7.8 Operations).

Fix

While a multisig mitigates single points of failure, consider implementing a timelock for critical owner-controlled functions. This would introduce a delay before changes take effect, allowing for community review or emergency intervention in case of a compromised key or malicious action. Regularly review and secure the multisig signers and their operational procedures.

Status

Unresolved

Info

Reliance on LayerZero v2 Protocol

The RaveToken contract is built as an Omnichain Fungible Token (OFT) using the LayerZero v2 protocol. Its core cross-chain transfer functionality is entirely dependent on the security, correctness, and availability of the LayerZero endpoint, message libraries, and overall infrastructure. Any vulnerabilities, misconfigurations, or operational issues within the LayerZero protocol itself could directly impact the security and functionality of the RaveToken (7.6 External).I-01

Issue

The RaveToken contract is built as an Omnichain Fungible Token (OFT) using the LayerZero v2 protocol. Its core cross-chain transfer functionality is entirely dependent on the security, correctness, and availability of the LayerZero endpoint, message libraries, and overall infrastructure. Any vulnerabilities, misconfigurations, or operational issues within the LayerZero protocol itself could directly impact the security and functionality of the RaveToken (7.6 External).

Fix

Acknowledge the inherent dependency risk associated with using a third-party protocol. Monitor LayerZero's security announcements, audits, and community channels. Ensure that the configured LayerZero endpoint and associated libraries are the official and most secure versions. Consider a robust incident response plan for potential LayerZero-related issues.

Status

Unresolved

Info

Fixed Supply Token Model

The RaveToken contract mints a fixed totalSupply to the specified owner address during its constructor execution. There are no additional minting capabilities provided after initial deployment. This establishes a fixed supply token model, which can be beneficial for transparency and predictability of tokenomics (7.4 Economic). The burn function allows for a reduction in total supply by any token holder.I-02

Issue

The RaveToken contract mints a fixed totalSupply to the specified owner address during its constructor execution. There are no additional minting capabilities provided after initial deployment. This establishes a fixed supply token model, which can be beneficial for transparency and predictability of tokenomics (7.4 Economic). The burn function allows for a reduction in total supply by any token holder.

Fix

Document this fixed supply model clearly in the project's whitepaper or tokenomics documentation to ensure transparency for users and investors. This design choice is generally considered a positive security and economic characteristic for many token projects.

Status

Unresolved

Info

Use of Latest Solidity Version

The contract utilizes pragma solidity ^0.8.28;, which is the latest stable version of the Solidity compiler at the time of this audit. This ensures that the contract benefits from the most recent compiler optimizations, bug fixes, and security features, including default checked arithmetic for integer operations, which prevents common overflow/underflow vulnerabilities (7.2 Code Security).I-03

Issue

The contract utilizes pragma solidity ^0.8.28;, which is the latest stable version of the Solidity compiler at the time of this audit. This ensures that the contract benefits from the most recent compiler optimizations, bug fixes, and security features, including default checked arithmetic for integer operations, which prevents common overflow/underflow vulnerabilities (7.2 Code Security).

Fix

Continue to monitor Solidity compiler updates and security advisories. While using the latest version is beneficial, always thoroughly test contracts with the specific compiler version used for deployment to ensure consistent behavior and avoid unexpected issues from minor version changes.

Status

Unresolved

Analysis

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

The RaveToken contract is an Omnichain Fungible Token (OFT) built on LayerZero v2, inheriting from OpenZeppelin's Ownable. The contract implements a standard fixed-supply ERC-20 token with a burn function. The audit identified no critical or high-severity vulnerabilities. A low-severity finding relates to the centralization of control via the owner, and several informational findings highlight architectural and best-practice aspects. The contract's reliance on well-audited libraries and a simple logic contributes to its low overall risk profile.

Technical8/10Low risk

The RaveToken contract exhibits good technical security (7.2 Code Security) by leveraging battle-tested OpenZeppelin Ownable and LayerZero v2 OFT libraries. The contract logic is minimal and straightforward, primarily consisting of a constructor for initial minting and a burn function, reducing the attack surface. The use of Solidity 0.8.28 ensures default checked arithmetic, mitigating integer overflow/underflow risks. No reentrancy vectors or complex external interactions were identified.

Governance1/10High risk

The economic model (7.4 Economic) of RaveToken is a fixed-supply token, with all tokens minted to the owner at deployment, and no further minting capabilities. The burn function allows users to reduce supply. Governance (7.5 Governance) is centralized through an Ownable pattern, where a multisig address acts as the owner, controlling critical LayerZero configurations such as setTrustedRemoteAddress and setFeeManager. While a multisig enhances security over a single EOA, this still represents a point of centralization (7.3 Access Control, 7.8 Operations). The contract's functionality is heavily reliant on the LayerZero v2 protocol (7.6 External), introducing dependency risk.

Upgrades7/10Low risk

The RaveToken contract is implemented as a standard, non-upgradeable contract. There are no proxy patterns (e.g., UUPS, Transparent) or other mechanisms for on-chain upgradeability. This design choice eliminates upgrade-related risks (7.7 Upgrades) such as proxy misconfigurations, storage collisions, or logic inconsistencies between versions. Any changes to the contract's logic would require a new deployment.

Final RecommendationWhat to do about this score

It is recommended to ensure robust operational security for the multisig controlling the RaveToken contract, as it holds significant administrative power over LayerZero configurations.

Regular audits of the LayerZero v2 protocol are advised, given the inherent dependency. Additionally, consider implementing a timelock for critical owner-controlled functions to provide a delay for review and potential intervention, further decentralizing control and enhancing security.

Contract & Record

1 audit on record
TypeRaveToken
NetworkBase
Token age1y
Contract0x1aa8…cfc3
Deployer0x17f1…b9f5
Badge for your website
RaveDAO 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. Aug 15, 202644Medium

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

Related Audits

6 more on the recordAll audits
Aerodrome FinanceAERO · Base44MediumSapienBase44MediumMocaBase44MediumNockchainNOCK · Base45MediumSolana (Universal)USOL · Base45MediumElsaBase45Medium

Would You Like a More Detailed Audit of RaveDAO?

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