On-chain security analysis — is it a scam or legit?
ClankerToken is an ERC-20 compliant token designed for cross-chain interoperability on the Base network.
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 3, 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.
0xffa3…07620.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 contract, 0xffa3…0762 — 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 crosschainMint function allows the designated bridge address to create new tokens at will, which can dilute the value of existing holdings. Ownership is renounced, so no one can call these functions now.
Ensure the bridge contract is secured by a multi-signature wallet and monitor minting events for anomalous activity.
Unresolved
The crosschainBurn function allows the bridge address to remove tokens from any user's balance, effectively granting it the power to seize assets. Ownership is renounced, so no one can call these functions now.
Restrict the burn functionality to only allow users to burn their own tokens, or implement a transparent, audited process for any bridge-initiated burns.
Unresolved
The ten largest holders own 100.0% of supply. What remains: 1.0% in wallets, 99.0% in other contracts. 5,629 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
5,629 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 $10.3M (DexScreener, all pools). 24h trading volume $53.5M (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: nobody (ownership renounced). Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $10.3M of DEX liquidity across 1 pools. Launch: 365 days of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
ClankerToken is an ERC-20 compliant token designed for cross-chain interoperability on the Base network. The architecture relies on the SuperchainTokenBridge for cross-chain minting and burning operations. While the implementation follows standard OpenZeppelin patterns for voting and permit functionality, the centralization of mint/burn authority poses significant risks to token holders.
The contract utilizes standard OpenZeppelin libraries for ERC-20, Votes, and Permit functionality, ensuring 7.1 Architecture and 7.2 Code Security compliance. 7.3 Access Control is implemented via a specific bridge address for cross-chain operations. 7.6 External dependencies are limited to standard pre-deployed bridge contracts. The codebase is clean and follows modern Solidity practices.
7.4 Economic and 7.5 Governance risks are centered on the bridge's authority to modify supply. While necessary for cross-chain functionality, the ability to burn tokens from any address creates a centralized point of failure. There are no automated governance mechanisms for these privileged actions.
7.7 Upgrades are not currently implemented as the contract is not a proxy. 7.8 Operations are handled via the immutable bridge address. No upgrade paths exist for the token logic itself.
The protocol should implement a multi-signature wallet or a timelock for any administrative functions that modify metadata or admin roles to mitigate centralization risks.
Additionally, users should be aware that the cross-chain bridge holds the technical capability to burn tokens from any address, which is a standard requirement for cross-chain bridges but represents a trust assumption.
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.
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? Add your links and get it Verified
