Is ClawBank Safe? Smart Contract Security Analysis

Security Checklist

4/5 checks passed

Contract VerifiedPass

Ownership RenouncedPass

No Mint FunctionPass

Liquidity LockedFail

Not a ProxyPass

Audit History

2 audits on record

Jul 2240Jul 232

Every audit run adds a dated snapshot — history is append-only and cannot be edited.

Audit Summary

The ClankerToken contract is an ERC20 token with extensions for burning, voting, and cross-chain functionality. It leverages battle-tested OpenZeppelin libraries for core token logic, enhancing code security. Key features include an admin role for metadata management and a one-time verification mechanism by an original admin. Cross-chain minting and burning are restricted to a predefined SuperchainTokenBridge. The primary risk identified is the centralized control held by the `_admin` role, which can update critical token metadata and transfer its own administrative privileges.

Final Recommendation: To enhance the security posture, it is crucial to implement robust operational security practices for the `_admin` key. Consider multi-signature wallets or time-locks for sensitive administrative actions, especially for transferring the admin role. Additionally, ensure the `Predeploys.SUPERCHAIN_TOKEN_BRIDGE` is thoroughly audited and maintained, as the token's cross-chain integrity relies heavily on its security. Regular reviews of the administrative access controls and external dependencies are recommended.

Category Ratings

TechnicalLow

10/10

The contract demonstrates strong technical foundations (7.1 Architecture, 7.2 Code Security). It inherits from well-audited OpenZeppelin ERC20, ERC20Permit, ERC20Votes, and ERC20Burnable contracts, minimizing common vulnerabilities. Custom logic for cross-chain minting and burning (e.g., `crosschain

GovernanceLow

7/10

The contract's economic model (7.4 Economic) involves a fixed `maxSupply_` minted to the deployer on a specific chain, which is a clear design choice. Governance (7.5 Governance) is centralized around an `_admin` role, which can update token metadata (`_image`, `_metadata`) and transfer the adm

UpgradesLow

9/10

The ClankerToken contract is not designed with an upgrade mechanism (7.7 Upgrades), meaning its logic is immutable once deployed. This eliminates risks associated with proxy patterns or upgradeable contracts, such as proxy misconfigurations or upgrade delays. However, it also means that any discover

LP Distribution

Top-1 Unlocked Holder100.0%

Top-3 Unlocked100.0%

What Raised This Score

4 factors

Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
LP top1 unlocked holder = 100.0% (independent LP — depth risk, pool = 99% of DEX liquidity)
LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 99% of DEX liquidity)
1 Medium finding(s) from audit

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

Security Findings

3 total

1 Medium 2 Info

M-01MediumUnresolved

Centralized Control by Admin Role

The `_admin` role has significant control over the contract, including the ability to update the token's image, metadata, and crucially, to transfer the `_admin` role itself to any address via `updateAdmin`, `updateImage`, and `updateMetadata` functions. If the `_admin` key is compromised, an attacker could alter token branding or transfer administrative control, potentially leading to reputational damage or further exploits.

Recommendation: Implement a multi-signature wallet for the `_admin` role to require multiple approvals for sensitive operations like `updateAdmin`. Consider adding a time-lock mechanism for `updateAdmin` to provide a window for community or team intervention if an unauthorized transfer is initiated. Clearly document the responsibilities and security procedures for managing the `_admin` key.

I-01InformationalUnresolved

Reliance on External Bridge Security

The `crosschainMint` and `crosschainBurn` functions are critical for maintaining the token's supply consistency across chains. These functions are exclusively callable by `Predeploys.SUPERCHAIN_TOKEN_BRIDGE`. The security and integrity of the ClankerToken's cross-chain operations are entirely dependent on the security of this external bridge contract.

Recommendation: Ensure that the `Predeploys.SUPERCHAIN_TOKEN_BRIDGE` contract is rigorously audited, continuously monitored, and maintained with the highest security standards. Any vulnerability in the bridge could directly impact the ClankerToken's supply and value. Consider establishing a robust incident response plan for bridge-related issues.

I-02InformationalUnresolved

Fixed Initial Supply Distribution to Deployer

In the constructor, the entire `maxSupply_` is minted to `msg.sender` (the contract deployer) if `block.chainid` matches `initialSupplyChainId_`. This design choice means the initial token distribution is entirely concentrated with the deployer on a specific chain, rather than being distributed or held by a treasury contract.

Recommendation: This is a design decision, not a vulnerability. However, it's important for the project to clearly communicate this initial distribution strategy to stakeholders. If not already planned, consider a transparent mechanism for subsequent distribution or management of this initial supply to avoid perceptions of centralization or to fund ecosystem development.

Is ClawBank Safe? CLAWBANK