Quantum Audit Logo
BNB Chain · Smart Contract Security · Updated Jul 24, 2026

Is 币安人生 Safe? 币安人生

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

Contract 0x924f…4444 DexScreener ↗
Volume 24h
$1.08M
Liquidity
$7.88M
Price
$0.6474
Token Age
9mo
Top 10 Holders
82.0%

Security Checklist

Contract VerifiedPass
Ownership RenouncedPass
No Mint FunctionPass
Liquidity LockedPass
Not a ProxyPass

Audit History

Jul 2241Jul 230

Every audit run adds a dated snapshot — history is append-only and cannot be edited.

Audit Summary

The FourERC20 contract is an implementation of the ERC-20 standard, largely based on OpenZeppelin Contracts. It provides core token functionalities but is designed as a base contract, requiring a derived contract to implement minting, burning, and constructor-based initialization. The code quality is high, leveraging well-audited OpenZeppelin patterns. Identified risks are primarily architectural regarding its incompleteness as a standalone token and standard ERC-20 considerations.

Final Recommendation: It is recommended that any derived contract building upon FourERC20 implements a secure and well-defined constructor to properly initialize the token's name and symbol, and establishes robust access control mechanisms for minting and burning functionalities. Thoroughly audit the derived contract's specific supply management logic and ensure users are educated on the safe use of `increaseAllowance` and `decreaseAllowance` over the standard `approve` function to mitigate known ERC-20 front-running risks.

Category Ratings

TechnicalLow
10/10

The technical architecture (7.1) is sound, utilizing battle-tested OpenZeppelin patterns for ERC-20 implementation. Code security (7.2) is robust, with proper handling of integer arithmetic and standard checks. Access control (7.3) for core token operations like transfer and allowance is standard ER

GovernanceMedium
6/10

The contract itself does not implement any specific economic models (7.4) beyond standard ERC-20 token transfers, nor does it include any governance mechanisms (7.5). Its economic stability relies entirely on the design of the derived contract that utilizes it and the broader ecosystem. There are no

UpgradesLow
10/10

The FourERC20 contract is not designed with explicit upgradeability features (7.7) such as proxy patterns. If this contract were to be used as an implementation in an upgradeable proxy system, careful consideration would be needed regarding the `_init` function to prevent re-initialization issues. A

LP Distribution

LP Burned100.0% · ≈ permanent lock
LP Locked100.0%

What Raised This Score

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 Findings

1 Low 2 Info
L-01LowUnresolved

Reliance on Derived Contracts for Supply Management and Initialization

As `_mint` and `_burn` are internal functions, any token built upon `FourERC20` will need to implement its own supply management logic. Similarly, the `_init` function is internal, requiring a derived contract to call it for setting token metadata. This introduces a dependency on the security and correctness of the derived contract for controlling the total supply, distribution, and initial setup of tokens. While flexible, it shifts the responsibility for critical economic parameters and initial configuration to external code (7.1 Architecture, 7.3 Access Control).

Recommendation: When developing the derived contract, ensure that minting, burning, and initialization functions are implemented with robust access control (e.g., `onlyOwner` or a multi-signature wallet) and adhere to best security practices. Thoroughly audit the derived contract's specific logic for these critical operations.
I-01InformationalUnresolved

Incomplete Token Implementation (No Mint/Burn Mechanism or Public Constructor)

The `FourERC20` contract serves as a base for an ERC-20 token but lacks a public constructor to initialize `name` and `symbol` and does not implement any minting or burning mechanisms. These functionalities (`_init`, `_mint`, `_burn`) are internal and must be implemented or called by a derived contract to create a fully functional token. This is an architectural design choice rather than a vulnerability, but it means the contract cannot be deployed as a standalone, fully functional token without further development.

Recommendation: Ensure that any derived contract inheriting from `FourERC20` implements a public constructor that calls `_init` to set the token's metadata and provides appropriate, access-controlled functions for `_mint` and `_burn` to manage the token supply. Document these dependencies clearly for future developers and auditors.
I-02InformationalUnresolved

Standard ERC-20 `approve` Race Condition

The `approve` function, while compliant with the ERC-20 standard, is susceptible to a known race condition where a malicious spender can exploit a user's attempt to change an allowance. If a user approves `X` amount, then approves `Y` amount, a front-running attacker can spend `X` before the `Y` transaction confirms, resulting in the attacker spending `X+Y`. This is a characteristic of the ERC-20 standard, not a flaw in this specific implementation (7.2 Code Security).

Recommendation: Advise users and integrated applications to prefer using `increaseAllowance` and `decreaseAllowance` functions over directly calling `approve` when modifying existing allowances. If `approve` must be used, the recommended safe practice is to first set the allowance to zero, wait for that transaction to confirm, and then set the new desired allowance.

Would You Like a More Detailed Audit of 币安人生?

Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, no signup required.

Get Detailed Audit
Run Free Audit →