Early-stage security check — honeypot & rug-pull analysis
The audit evaluated the DERC20 smart contract on the Base network, focusing on standard compliance, security controls, and governance parameters.
Read the full analysisEach 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
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 Oct 24, 2026
The risk score reads depth across every pair.
Whether the LP tokens are locked could not be determined.
The contract allows the owner to call updateMintRate(uint256) which automatically triggers mintInflation() when an active yearly cycle is in progress, expanding the total supply up to the 2% annual cap. While release() distributes already-allocated vested tokens, updateMintRate alters inflationary growth, diluting token holders.
Place updateMintRate behind a timelock and emit clear events when the mint rate is updated or tokens are minted. Document inflation scheduling transparently for token holders.
Unresolved
The owner has authority to invoke lockPool(address) and unlockPool(), toggling the boolean isPoolUnlocked and assigning the pool address. This switch decides whether transfers involving the pool are permitted or blocked, giving the owner unilateral power to freeze trading activity.
Restrict lockPool functionality to an initial launch window or implement a permanent pool unlocking mechanism that cannot be reversed by the owner once trading is initialized.
Unresolved
The ten largest holders own 100.0% of supply. Of that, 3.8% burned — not holders that can sell, so excluded from the concentration score. What remains: 16.2% in wallets, 80.0% in other contracts. The deployer/owner wallet itself holds 16.2%. 10,026 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
10,026 holders. Not listed by CoinGecko or any exchange GoPlus tracks. Nothing independent confirms who is behind this token, so every power its contract grants is scored at face value.
Match the contract address against the project's official channels before trading.
Acknowledged
Liquidity $146K (DexScreener, all pools). 24h trading volume $724K (DexScreener, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
A token issued by a project for use, governance or fundraising. Scored on its contract and market facts. The class itself adds no points; the contract and market facts decide the score. Basis: no class-specific evidence. Tokenomics — Supply: mintable with no on-chain cap found. Control: a ProxyAdmin contract. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $146K of DEX liquidity across 1 pools. Launch: under a day of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
The token's oldest DEX pool is less than a day old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
Re-check ownership, liquidity and holder distribution as the token matures; those are the facts that move early.
Acknowledged
The audit evaluated the DERC20 smart contract on the Base network, focusing on standard compliance, security controls, and governance parameters. The contract integrates standard OpenZeppelin implementations including ERC20Votes, ERC20Permit, and vesting mechanics. However, administrative capabilities grant the contract owner control over pool trading states and inflationary mint rate adjustments.
Under 7.1 Architecture and 7.2 Code Security, the contract demonstrates robust adherence to OpenZeppelin ERC-20 standards, with clean implementation of EIP-712 permit signing and ERC-5805 voting capabilities. The vesting logic in release() safely tracks claiming state via getVestingDataOf. However, under 7.3 Access Control, central authority is granted to the owner via lockPool() and unlockPool(), which gate transfers according to the isPoolUnlocked flag. Additionally, under 7.6 External dependencies, liquidity interactions depend heavily on the designated pool address remaining valid.
In terms of 7.4 Economic mechanisms, the token features a hard-coded cap on annual inflation via MAX_YEARLY_MINT_RATE_WAD (2% per year), protecting holders from unbounded arbitrary dilution. Vesting schedules are structured deterministically through computeAvailableVestedAmount. Under 7.5 Governance, however, the owner can alter the inflation rate at will using updateMintRate() and unilaterally freeze liquidity pool transfers using lockPool(). Furthermore, under 7.8 Operations, governance actions require multi-signature or timelock safeguards to avoid sudden unilateral market disruptions.
Regarding 7.7 Upgrades, the contract is deployed as an immutable, non-proxy contract with no delegatecall routing or proxy upgrade patterns present. This design ensures the core bytecode and dispatch logic cannot be swapped or tampered with maliciously post-deployment. The principal dynamic factor remains administrative parameters, such as tokenURI and isPoolUnlocked, which should be managed with strict operational oversight.
We recommend transferring contract ownership to a multi-signature wallet paired with a decentralized timelock controller.
This structure ensures adequate community notice and review before privileged actions—specifically updateMintRate() or lockPool()—can take effect. Additionally, consider implementing event emissions on all administrative state changes and formalizing transition paths to permanently renounce or irrevocably freeze the lockPool capability once initial liquidity has been stably established.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.
Get Detailed Audit Is this your token? Publish your own audit on this page
