Is Chip Safe? Smart Contract Security Analysis

Security Findings

1 Crit1 High1 Med1 Info

Critical

Unverified Implementation Contract

C-01The proxy contract (0x0c1c…1f6e) points to an implementation contract (0x13ae…a03f) whose source code is not verified on Etherscan. This prevents any security analysis of the actual business logic and state management, making it impossible to ascertain the system's safety, functionality, or adherence to security best practices. The entire system's security is unknown.

IssueThe proxy contract () points to an implementation contract () whose source code is not verified on Etherscan. This prevents any security analysis of the actual business logic and state management, making it impossible to ascertain the system's safety, functionality, or adherence to security best practices. The entire system's security is unknown.

FixImmediately verify the source code of the implementation contract on Etherscan. Once verified, a comprehensive security audit of the implementation contract must be performed to identify and address any vulnerabilities before further operations.

StatusUnresolved

High

Centralized Upgrade Authority

H-01The `TransparentUpgradeableProxy` deploys a `ProxyAdmin` contract, whose `initialOwner` has sole control over upgrading the proxy's implementation. If this `initialOwner` is a single Externally Owned Account (EOA), it represents a single point of failure. A compromise of this EOA would allow an attacker to deploy arbitrary malicious code as the new implementation, potentially leading to a complete loss of funds or control over the protocol.

IssueThe `TransparentUpgradeableProxy` deploys a `ProxyAdmin` contract, whose `initialOwner` has sole control over upgrading the proxy's implementation. If this `initialOwner` is a single Externally Owned Account (EOA), it represents a single point of failure. A compromise of this EOA would allow an attacker to deploy arbitrary malicious code as the new implementation, potentially leading to a complete loss of funds or control over the protocol.

FixIt is strongly recommended that the `initialOwner` of the `ProxyAdmin` be a robust, multi-signature wallet (e.g., Gnosis Safe) or a decentralized autonomous organization (DAO) controlled by multiple parties. This distributes control and reduces the risk associated with a single point of failure.

StatusUnresolved

Medium

Lack of Timelock for Critical Operations

M-01The current setup allows the `ProxyAdmin` owner to execute upgrades immediately without any time delay. This means that if the admin key is compromised or if a malicious upgrade is pushed, there is no window for users or monitoring systems to react or exit before the changes take effect. This lack of a timelock increases the risk of rapid, unrecoverable damage.

IssueThe current setup allows the `ProxyAdmin` owner to execute upgrades immediately without any time delay. This means that if the admin key is compromised or if a malicious upgrade is pushed, there is no window for users or monitoring systems to react or exit before the changes take effect. This lack of a timelock increases the risk of rapid, unrecoverable damage.

FixImplement a timelock mechanism for the `ProxyAdmin` owner. This could involve making the `ProxyAdmin` owner a TimelockController contract, which introduces a mandatory delay between proposing an upgrade and its execution. This provides a crucial window for review and reaction, enhancing overall system security and user confidence.

StatusUnresolved

Info

Immutable Admin Address Design

I-01The `_admin` variable in `TransparentUpgradeableProxy` is declared as `immutable`. This is a design choice in OpenZeppelin Contracts v5.x to optimize gas costs by avoiding storage reads for the admin address. It means the specific `ProxyAdmin` instance deployed by the proxy cannot be changed; only its ownership can be transferred. While this prevents accidental overwrites of the admin slot by the implementation, it also means the proxy is permanently tied to that specific `ProxyAdmin` contract instance.

IssueThe `_admin` variable in `TransparentUpgradeableProxy` is declared as `immutable`. This is a design choice in OpenZeppelin Contracts v5.x to optimize gas costs by avoiding storage reads for the admin address. It means the specific `ProxyAdmin` instance deployed by the proxy cannot be changed; only its ownership can be transferred. While this prevents accidental overwrites of the admin slot by the implementation, it also means the proxy is permanently tied to that specific `ProxyAdmin` contract instance.

FixThis is an intentional design choice by OpenZeppelin and generally considered a security improvement. No direct action is required for the proxy itself, but it's important to understand that the security of the upgrade mechanism relies entirely on the `ProxyAdmin` contract's ownership and its own security practices.

StatusUnresolved

Category Ratings

TechnicalMedium6/10

The proxy contract (7.1 Architecture) is a standard OpenZeppelin TransparentUpgradeableProxy, which is a well-vetted and secure component. It correctly implements the transparent proxy pattern, preventing selector clashes and ensuring proper admin-only upgrade functionality (7.2 Code Security). The admin address is set as immutable during construction, enhancing security by preventing accidental overwrites of the admin slot. However, the critical issue is that the implementation contract's source code is not verified, making it impossible to assess its code security, potential vulnerabilities, or adherence to best practices. This lack of visibility into the core logic introduces significant technical risk.

GovernanceHigh1/10

The system relies on a `ProxyAdmin` contract for upgrade management (7.5 Governance). The `initialOwner` of this `ProxyAdmin` determines the centralization level of upgrade authority. If this owner is a single EOA, it represents a single point of failure and a high centralization risk (7.3 Access Control). Without a timelock mechanism for upgrades, the `ProxyAdmin` owner can execute upgrades immediately, which could lead to rapid deployment of malicious code or unvetted changes (7.4 Economic). The economic security is entirely dependent on the implementation's logic, which is currently unknown.

UpgradesHigh3/10

The contract utilizes the Transparent Proxy pattern for upgradeability (7.7 Upgrades), allowing the implementation logic to be updated. This flexibility is a strength, enabling bug fixes and feature enhancements. However, the unverified nature of the current implementation contract means that any future upgrades, even if the new implementation is verified, would be building upon an unknown and unaudited foundation. Furthermore, the lack of a timelock for upgrades means that the `ProxyAdmin` owner can instantly change the contract's behavior, posing a significant risk if the admin key is compromised or acts maliciously.

Security Checklist

2/5 checks passed

Contract VerifiedPass

Ownership Renounced?

No Mint FunctionPass

Liquidity LockedFail

Not a ProxyFail

Proxy Upgrade Controls

Proxy TypeEip1967 Transparent

AdminOZ ProxyAdmin

ImplementationVerified source

Upgrades (30d)0 · stable

Holder Composition

74.3% in top 10

67.3% in wallets7.0% in contracts

Effective Concentration70.1%

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.

Liquidity Depth

$1.12M across 4 pairs

UniswapUSDCanalysed$1.07M UniswapUSDC$48.2K UniswapUSDC$118 UniswapWETH$33

The risk score reads depth across every pair. The volume figure and the volume-to-liquidity ratio elsewhere on this page describe only the pair this audit analysed, so the two are not directly comparable.

LP Distribution

Top-1 Unlocked Holder64.2%

Top-3 Unlocked100.0%

Key Addresses

4 addresses

Deployer

0x9868…79b2

Unlocked LP Held By

0x9946…bb460x3421…22aa0x2945…a02d

No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.

What Raised This Score

9 factors

Ownership status UNKNOWN (owner could not be resolved)
Proxy contract (upgradeable — admin can replace logic)
Top-10 concentration > 70% (74.3% total → 70.1% effective; 67.3% in EOAs, 7.0% in contracts — extreme)
Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
LP top1 unlocked holder = 64.2% (independent LP — depth risk, pool = 96% of DEX liquidity)
LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 96% of DEX liquidity)
1 Critical finding(s) from audit
1 High finding(s) from audit
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

Final Recommendation

AI Copilot

The most critical recommendation is to immediately verify the source code of the implementation contract () on Etherscan.…

Read the verdictHide

Without this, a proper security assessment is impossible, and the system remains at severe risk. Once verified, a full audit of the implementation logic should be conducted to identify and mitigate any vulnerabilities. Additionally, consider implementing a robust governance mechanism for the `ProxyAdmin` owner, such as a multi-signature wallet with a timelock, to introduce a delay for critical operations like upgrades, enhancing security and transparency.

Contract

TypeTransparentUpgradeableProxy

Audit History

1 audit on record

Jul 2276Jul 2373

Score changes are recorded as dated snapshots — history is append-only and cannot be edited.

Not Signed In

Is Chip Safe?

Security Findings

Unverified Implementation Contract

Centralized Upgrade Authority

Lack of Timelock for Critical Operations

Immutable Admin Address Design

Category Ratings

Security Checklist

Proxy Upgrade Controls

Holder Composition

Liquidity Depth

LP Distribution

Key Addresses

What Raised This Score

Related Audits

Would You Like a More Detailed Audit of Chip?