Early-stage security check — honeypot & rug-pull analysis
The DERC20 contract is a standard ERC-20 implementation with additional governance and vesting features.
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 Nov 2, 2026
The risk score reads depth across every pair.
The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.
0xe5ac…ce5dNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The owner has the ability to mint new tokens via the updateMintRate and release functions. This allows the owner to increase the total supply, which dilutes the value of existing holdings.
Consider implementing a timelock for minting operations or moving control to a multi-signature wallet to prevent unilateral supply changes.
Unresolved
The owner can use the lockPool and unlockPool functions to enable or disable token transfers. This gives the owner the power to freeze user assets or restrict market activity at will.
Remove the ability to arbitrarily lock transfers, or restrict this functionality to a decentralized governance vote to ensure it is only used in emergency scenarios.
Unresolved
0.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by 1 address(es) other than the owner/deployer. One of them — a wallet, 0xe5ac…ce5d — holds 100.0% and can remove that share at once; who controls it is not visible on-chain, so it is not treated as an independent provider. Some pools are concentrated-liquidity (V3/V4) positions; shares above are by position as GoPlus reports them.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
The ten largest holders own 95.5% of supply. What remains: 0.5% in wallets, 95.0% in other contracts. 162 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
162 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 $134.7M (DexScreener, all pools). 24h trading volume $1.1M (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: $134.7M 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 DERC20 contract is a standard ERC-20 implementation with additional governance and vesting features. The protocol relies on a centralized owner to manage inflation and transfer restrictions. While the code follows standard OpenZeppelin patterns, the high level of administrative control over token supply and transferability presents a significant centralization risk.
The architecture utilizes robust OpenZeppelin libraries for ERC-20, Votes, and Permit functionality. 7.1 Architecture and 7.2 Code Security are well-implemented, adhering to modern Solidity standards. 7.3 Access Control is strictly enforced via the Ownable pattern, though it creates a single point of failure. 7.8 Operations are standard, with no complex logic outside of the minting and vesting mechanisms.
7.4 Economic and 7.5 Governance aspects are heavily centralized under the contract owner. The owner has the authority to mint tokens and halt transfers, which directly impacts token holder value. While inflation is capped at 2% annually, the lack of a timelock or multi-sig requirement for these actions is a concern. 7.6 External dependencies are minimal and well-managed.
The contract is not a proxy and does not support 7.7 Upgrades. This provides immutability, which is a strength for security, as the logic cannot be altered post-deployment. The current state is fixed, ensuring that the rules governing the token remain consistent.
It is recommended to transition the ownership of the contract to a decentralized governance model, such as a multi-signature wallet or a DAO, to mitigate the risks associated with a single privileged owner.
Implementing a timelock on sensitive functions like updateMintRate would provide transparency and protection for token holders against sudden changes in supply. Additionally, ensure that the vesting schedule and pool locking mechanisms are clearly documented for users. Regular monitoring of the owner's actions is advised until a more decentralized control structure is implemented.
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.
The United Oil Dividend Fund (UODF) contract on Base is 0x2f22ad914991f87e809913e652f0b5ddcbf8eb55. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.
Quantum Audit's risk score for United Oil Dividend Fund is 55/100 (Medium risk) as of Nov 2, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; Ownership: Retained; Mint: Mintable; Liquidity lock: Not locked; Upgradeability: Fixed code; Honeypot: None found; Buy / sell tax: 0% / 0%. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.
Liquidity lock: Not locked (as of Nov 2, 2026). Total DEX liquidity: $134.72M.
As of Nov 2, 2026, the 10 largest holders own 95.5% of the supply across 162 holders. The Holders section on this page shows who they are by holder type.
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? Add your links and get it Verified
