Quantum Audit Logo
Launch App

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

Is 0G Safe?

BNB 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
Medium RiskHow is this score calculated?
How the score breaks downratings: 10 is safest
Technical8/10Governance1/10Upgrades6/10Checks passed5 of 7Findings1 Low · 2 Info3
SummaryAI Copilot

The ZeroGravityOFT contract is a minimal implementation of an Omnichain Fungible Token (OFT) using LayerZero v2. It inherits directly from LayerZero's OFT contract and OpenZeppelin's Ownable.

Read the full analysis
What raised the score
  • Ownership not renounced — owner is an EOA
  • Top-10 concentration > 70%
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 99.9%
  • LP top3 unlocked holders = 100.0%
  • 1 Low finding(s) from audit
Exact factors
  • Ownership NOT renounced — owner is an EOA (single private key)
  • Top-10 concentration > 70% (91.5% total → 91.5% effective; 91.5% 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 = 99.9% (independent LP — depth risk, pool = 93% of DEX liquidity)
  • LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 93% 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

Security Checklist

as of audit · Sep 45 of 7 checks passed
Contract verifiedVerified
OwnershipRetained
MintNo mint
Liquidity lockNot locked
UpgradeabilityFixed code
HoneypotNone found
Buy / sell tax0% / 0%

Holders

as of audit · Sep 4, 2026
91.5%Wallets8.5%Everyone else
91.5%Wallets8.5%
WalletsEveryone elseBubble area = share of supply
91.5%of supply sits with the top 10 holders
  • Walletsanonymous holders, free to sell91.5%
  • Everyone elsethe rest of the supply8.5%
Effective concentrationwhat the score reads91.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$94.5K across 4 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$88.0KShare of depth93.1%
Top-1 Unlocked Holder99.9%
Top-3 Unlocked100.0%
Unlocked LP held by
0x14c9…272d0x9b56…5f53

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

Security Findings

1 Low2 Info
Low

Centralized Control by Owner EOA

The contract's ownership is held by a single External Owned Account (EOA), as initialized in the constructor via the _delegate parameter. This owner has significant control over critical LayerZero configurations, such as setting trusted remote addresses, minimum destination gas, and other operational parameters (7.3 Access Control, 7.8 Operations). While this is standard for OFT contracts, reliance on a single EOA introduces a centralized point of failure. If the EOA's private key is compromised, an attacker could manipulate cross-chain functionality, potentially leading to denial of service or unauthorized fee adjustments.L-01

Issue

The contract's ownership is held by a single External Owned Account (EOA), as initialized in the constructor via the _delegate parameter. This owner has significant control over critical LayerZero configurations, such as setting trusted remote addresses, minimum destination gas, and other operational parameters (7.3 Access Control, 7.8 Operations). While this is standard for OFT contracts, reliance on a single EOA introduces a centralized point of failure. If the EOA's private key is compromised, an attacker could manipulate cross-chain functionality, potentially leading to denial of service or unauthorized fee adjustments.

Fix

It is highly recommended to transfer ownership of the contract to a robust multi-signature wallet (e.g., Gnosis Safe). This would require multiple approvals for any critical administrative actions, significantly reducing the risk associated with a single point of compromise.

Status

Unresolved

Info

Fundamental Reliance on LayerZero Protocol Security

The ZeroGravityOFT contract is built upon LayerZero's Omnichain Fungible Token (OFT) standard, inheriting its core cross-chain messaging and token transfer logic. Consequently, the security and operational integrity of this contract are fundamentally dependent on the underlying LayerZero protocol and its smart contract implementations (7.6 External). Any vulnerabilities or exploits discovered within the LayerZero protocol itself could directly impact the functionality and security of ZeroGravityOFT.I-01

Issue

The ZeroGravityOFT contract is built upon LayerZero's Omnichain Fungible Token (OFT) standard, inheriting its core cross-chain messaging and token transfer logic. Consequently, the security and operational integrity of this contract are fundamentally dependent on the underlying LayerZero protocol and its smart contract implementations (7.6 External). Any vulnerabilities or exploits discovered within the LayerZero protocol itself could directly impact the functionality and security of ZeroGravityOFT.

Fix

While this is an inherent architectural dependency, it is crucial for the ZeroGravity team to stay informed about LayerZero security updates, audits, and any potential advisories. Implement robust monitoring for LayerZero network activity and contract interactions.

Status

Unresolved

Info

Minimal Custom Logic Reduces Attack Surface

The ZeroGravityOFT contract introduces no custom business logic beyond its constructor, which correctly initializes the inherited OFT and Ownable components. All core functionality for token transfers and cross-chain operations is derived directly from the audited LayerZero OFT library and OpenZeppelin's Ownable contract (7.2 Code Security). This minimalist approach significantly reduces the potential attack surface for novel vulnerabilities specific to this contract's codebase.I-02

Issue

The ZeroGravityOFT contract introduces no custom business logic beyond its constructor, which correctly initializes the inherited OFT and Ownable components. All core functionality for token transfers and cross-chain operations is derived directly from the audited LayerZero OFT library and OpenZeppelin's Ownable contract (7.2 Code Security). This minimalist approach significantly reduces the potential attack surface for novel vulnerabilities specific to this contract's codebase.

Fix

Maintain this design principle of minimal custom logic if future extensions are considered. Any new functionality should be thoroughly reviewed and audited to ensure it does not introduce new vulnerabilities.

Status

Unresolved

Analysis

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

The ZeroGravityOFT contract is a minimal implementation of an Omnichain Fungible Token (OFT) using LayerZero v2. It inherits directly from LayerZero's OFT contract and OpenZeppelin's Ownable. The contract introduces no custom logic beyond its constructor, which initializes the OFT and sets the owner. The primary risks stem from the inherent centralization of control by the owner over LayerZero configurations and the fundamental reliance on the LayerZero protocol's security.

Technical8/10Low risk

The contract exhibits strong technical security due to its minimal custom code (7.2 Code Security) and reliance on well-audited libraries from OpenZeppelin and LayerZero. The architecture (7.1 Architecture) is straightforward, acting as a direct wrapper for the OFT standard. The constructor correctly initializes both the OFT and Ownable components, ensuring proper setup. No reentrancy or integer overflow/underflow vulnerabilities were identified within the contract's specific logic.

Governance1/10High risk

The contract utilizes the Ownable pattern, granting the deployer (or specified delegate) significant control over LayerZero configurations (7.3 Access Control). This includes the ability to set trusted remote addresses, minimum destination gas, and other critical parameters that directly impact cross-chain operations and associated fees (7.4 Economic). While standard for OFT implementations, the current ownership by an EOA introduces a centralized point of failure. If the owner's private key is compromised, the token's cross-chain functionality could be manipulated or halted (7.5 Governance).

Upgrades6/10Medium risk

The ZeroGravityOFT contract is not designed as an upgradeable proxy (7.7 Upgrades). It is a standard implementation contract. Any future changes or upgrades to its logic would require deploying a new contract and migrating users or liquidity, which avoids the complexities and specific risks associated with proxy upgrade patterns.

Final RecommendationWhat to do about this score

To enhance the security posture, it is strongly recommended to transition the contract ownership from the current EOA to a robust multi-signature wallet.

This will significantly mitigate the risk of a single point of failure and provide a more secure governance model for critical LayerZero configurations. Additionally, continuous monitoring of the LayerZero protocol for any security advisories or updates is crucial, given the contract's fundamental dependency on its underlying infrastructure.

Contract & Record

1 audit on record
TypeSolidity 0.8.22
NetworkBNB Chain
Token age11mo
Contract0x4b94…b3ee
Deployer0xce0f…c78a
Badge for your website
0G 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 1, 202663Medium

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

Related Audits

6 more on the recordAll audits
CalderaERA · BNB Chain63MediumTAKEBNB Chain63MediumZEUSBNB Chain63MediumPro TokenPRO · BNB Chain64MediumStarpower NetworkSTAR · BNB Chain62MediumElonCoinBNB Chain64Medium

Would You Like a More Detailed Audit of 0G?

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