Quantum Audit Logo

Is Sustainable Aviation Fuel a Scam?

Early-stage security check — honeypot & rug-pull analysis

Is this your token? Publish your own audit on this page →

Sustainable Aviation Fuel SAF
0xfe4d…eef9
Ethereum Not verifiedLast checked 3d ago 1 audit on record New Launch · 2d old
DexScreener ↗
How is this score calculated? → High Risk
Executive SummaryAI Copilot

The SAFToken contract implements a standard ERC20 token with Ownable access control, inheriting from battle-tested OpenZeppelin libraries. The token supply is fixed at deployment, with no further minting or burning capabilities. The contract exhibits a high degree of security due to its reliance on well-audited components and minimal custom logic. No critical or high-severity vulnerabilities were identified.

3 Informational
! Early-stage analysis. This token has limited on-chain history (2d old). New tokens carry elevated risk — data may change rapidly. Always verify independently before investing.
Volume 24h
$2.2K
Liquidity
$78.6K
Price
$0.0007809
Token Age
2d
Top 10 Holders
99.1%

Security Findings

3 Info
Info

Fixed Token Supply

I-01The SAFToken contract mints all 1,000,000,000 tokens to the `initialOwner` during its constructor execution. There are no public `mint` or `burn` functions available, meaning the total supply of the token is fixed at deployment and cannot be altered by any entity, including the contract owner. This is a design choice that impacts the token's economic model.
IssueThe SAFToken contract mints all 1,000,000,000 tokens to the `initialOwner` during its constructor execution. There are no public `mint` or `burn` functions available, meaning the total supply of the token is fixed at deployment and cannot be altered by any entity, including the contract owner. This is a design choice that impacts the token's economic model.
FixNo action is required if a fixed supply is the intended design. Ensure this fixed supply model is clearly communicated to token holders and stakeholders, as it prevents future inflation or deflation through contract-controlled mechanisms.
StatusUnresolved
Info

Unused Interfaces Imported

I-02The contract imports `IERC721Errors` and `IERC1155Errors` interfaces. However, the `SAFToken` contract is an ERC20 token and does not implement any ERC721 or ERC1155 functionalities. Consequently, these imported interfaces are not utilized within the contract's logic.
IssueThe contract imports `IERC721Errors` and `IERC1155Errors` interfaces. However, the `SAFToken` contract is an ERC20 token and does not implement any ERC721 or ERC1155 functionalities. Consequently, these imported interfaces are not utilized within the contract's logic.
FixWhile harmless, removing unused imports can slightly reduce the compiled contract size and improve code readability by eliminating unnecessary dependencies. Consider removing `interface IERC721Errors` and `interface IERC1155Errors` if they are not intended for future use.
StatusUnresolved
Info

Reliance on Standard OpenZeppelin Libraries

I-03The `SAFToken` contract primarily inherits and utilizes the `ERC20` and `Ownable` implementations from OpenZeppelin Contracts. These libraries are widely used, battle-tested, and have undergone extensive audits by the community and professional auditors. This reliance significantly reduces the likelihood of common vulnerabilities such as reentrancy, integer overflows/underflows, and basic access control flaws within the core token functionalities.
IssueThe `SAFToken` contract primarily inherits and utilizes the `ERC20` and `Ownable` implementations from OpenZeppelin Contracts. These libraries are widely used, battle-tested, and have undergone extensive audits by the community and professional auditors. This reliance significantly reduces the likelihood of common vulnerabilities such as reentrancy, integer overflows/underflows, and basic access control flaws within the core token functionalities.
FixContinue to leverage well-audited and maintained libraries like OpenZeppelin. When introducing custom logic, ensure it is thoroughly reviewed and tested to maintain the overall security posture established by the base contracts.
StatusUnresolved

Category Ratings

TechnicalLow8/10

The technical architecture (7.1) is robust, leveraging OpenZeppelin's highly audited ERC20 and Ownable contracts. Code security (7.2) is strong, benefiting from the `unchecked` blocks being correctly applied where prior checks prevent underflow/overflow, and standard error handling. Access control (7.3) is managed via the Ownable pattern, granting the deployer the ability to transfer or renounce ownership, but no special token-related privileges post-deployment. The contract does not introduce new attack vectors like reentrancy or flash loan vulnerabilities.

GovernanceHigh1/10

The economic model (7.4) for SAFToken is straightforward: a fixed supply of 1 billion tokens is minted to the initial owner during deployment, with no subsequent minting or burning mechanisms. This design ensures predictable tokenomics without inflationary pressures from the contract itself. Governance (7.5) is minimal, relying solely on the `Ownable` pattern for managing contract ownership, allowing the owner to transfer or renounce this role. There are no complex governance modules or voting systems.

UpgradesLow7/10

The SAFToken contract is implemented as a standard, non-upgradeable contract (7.7). It does not utilize any proxy patterns (e.g., UUPS, Transparent) or other mechanisms for future modification of its logic. This design choice eliminates upgrade-related risks such as proxy misconfigurations, storage collisions, or insecure upgrade paths, ensuring immutability of the deployed code.

Security Checklist

4/5 checks passed
Contract VerifiedPass
Ownership RenouncedFail
No Mint FunctionPass
Liquidity LockedPass
Not a ProxyPass

Holder Composition

99.1% in top 10
64.0% in wallets35.0% in contracts
Effective Concentration78.1%

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.

Liquidity Depth

$78.6K

The risk score reads depth across every pair. The volume figure and the volume-to-liquidity ratio elsewhere on this page describe only the pair this audit analysed, so the two are not directly comparable.

LP Distribution

LP Locked100.0% · TeamFinance

Key Addresses

1 addresses
Deployer
0xc631…2317

What Raised This Score

3 factors
  • Ownership NOT renounced — owner is an EOA (single private key)
  • Top-10 concentration > 70% (99.1% total → 78.1% effective; 64.0% in EOAs, 35.0% in contracts — extreme)
  • Token age < 7 days (early, volatile)

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

Related Audits

6 more on the record
Arbitrum (ARB)High RiskHelix Token (HLX)High RiskEuler (EUL)High RiskPaxos Gold (PAXG)High RiskIlluvium (ILV)High RiskQuant (QNT)High Risk

Would You Like a More Detailed Audit of Sustainable Aviation Fuel?

This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.

Get Detailed Audit