Early-stage security check — honeypot & rug-pull analysis
The ClankerToken is an ERC-20 compliant token with cross-chain capabilities integrated via the Superchain Token Bridge.
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 21, 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 bridge contract to increase the total supply of tokens at any time, which can dilute the value of existing holdings. Ownership is renounced, so no one can call these functions now.
Ensure that the bridge contract is secured by a multi-signature wallet or a decentralized governance mechanism to prevent unauthorized minting.
Unresolved
The crosschainBurn function allows the bridge contract to remove tokens from any user's balance, effectively granting the bridge controller the power to seize or destroy user assets. Ownership is renounced, so no one can call these functions now.
Implement strict access controls and audit logs for the bridge contract to ensure that burn operations are only executed during legitimate cross-chain transfers.
Unresolved
The ten largest holders own 100.0% of supply. What remains: 1.0% in wallets, 99.0% in other contracts. 4,408 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
4,408 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 $57.9M (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 2 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 ClankerToken is an ERC-20 compliant token with cross-chain capabilities integrated via the Superchain Token Bridge. The architecture relies on the bridge contract to manage supply fluctuations. While the implementation follows standard OpenZeppelin patterns, the centralized control granted to the bridge for minting and burning poses inherent risks to token holders.
The contract utilizes standard OpenZeppelin libraries for ERC-20 and governance features (7.1 Architecture, 7.2 Code Security). The code is clean and follows established patterns for cross-chain interoperability (7.6 External). However, the reliance on a specific pre-deployed bridge address creates a single point of failure for supply management.
Economic control is centralized within the bridge contract (7.4 Economic, 7.5 Governance). The ability to mint and burn tokens allows for potential supply manipulation if the bridge is compromised. There are no automated circuit breakers or timelocks for these privileged operations.
The contract is not currently using a proxy pattern (7.7 Upgrades). Logic updates would require a full redeployment. Operational security (7.8 Operations) is dependent on the security of the bridge infrastructure.
Users should be aware that the token supply is dynamic and controlled by the Superchain Token Bridge.
We recommend monitoring the bridge's security posture and governance parameters, as any compromise of the bridge contract directly impacts token balances and total supply. For future iterations, consider implementing a multi-signature requirement or a timelock for administrative actions to reduce the impact of a single-point-of-failure in the bridge integration.
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
