Is Allora (ALLO) Safe? Smart Contract Security Analysis

Security Findings

1 Crit1 High1 Med1 Low

Critical

Unverified Implementation Contract Source Code

C-01The core logic of the system resides in the implementation contract (AlloOFTUpgradeable at 0xb21c…6278), but its source code is not publicly verified. This prevents any security assessment of the actual business logic, making it impossible to identify vulnerabilities such as reentrancy, access control flaws, or economic exploits. Users and auditors cannot independently verify the contract's behavior or safety.

IssueThe core logic of the system resides in the implementation contract (AlloOFTUpgradeable at ), but its source code is not publicly verified. This prevents any security assessment of the actual business logic, making it impossible to identify vulnerabilities such as reentrancy, access control flaws, or economic exploits. Users and auditors cannot independently verify the contract's behavior or safety.

FixImmediately verify and publish the source code for the `AlloOFTUpgradeable` implementation contract on block explorers. Conduct a thorough security audit of this implementation contract to identify and remediate any vulnerabilities. Ensure that all future implementation upgrades also have their source code verified.

StatusUnresolved

High

Lack of Timelock for Critical Operations (Upgrades)

H-01While the upgrade mechanism is controlled by a 2-of-3 multisig, there is no timelock in place for executing upgrades. This means that once the required multisig approvals are obtained, an upgrade can be deployed instantly. This lack of a delay period prevents users, the community, or automated monitoring systems from reacting to a potentially malicious or erroneous upgrade before it takes effect, increasing the risk of irreversible damage or fund loss.

IssueWhile the upgrade mechanism is controlled by a 2-of-3 multisig, there is no timelock in place for executing upgrades. This means that once the required multisig approvals are obtained, an upgrade can be deployed instantly. This lack of a delay period prevents users, the community, or automated monitoring systems from reacting to a potentially malicious or erroneous upgrade before it takes effect, increasing the risk of irreversible damage or fund loss.

FixIntegrate a timelock contract into the upgrade process. The `ProxyAdmin` should be owned by a timelock, which in turn is controlled by the multisig. This ensures that any proposed upgrade has a mandatory delay period (e.g., 24-72 hours) before it can be executed, allowing for review and potential intervention.

StatusUnresolved

Medium

Reliance on External Contracts for Core Logic

M-01The security and functionality of the entire system are entirely dependent on the `AlloOFTUpgradeable` implementation contract. Any vulnerability within this external contract, whether due to design flaws, coding errors, or malicious intent, will directly impact the proxy and its users. This risk is exacerbated by the unverified source code of the implementation.

IssueThe security and functionality of the entire system are entirely dependent on the `AlloOFTUpgradeable` implementation contract. Any vulnerability within this external contract, whether due to design flaws, coding errors, or malicious intent, will directly impact the proxy and its users. This risk is exacerbated by the unverified source code of the implementation.

FixEnsure rigorous security practices for the development, testing, and auditing of the implementation contract. Implement robust monitoring for the implementation contract's behavior and state. Consider formal verification or extensive fuzzing for critical components of the implementation.

StatusUnresolved

Low

Centralized Upgrade Authority

L-01Although the upgrade authority is managed by a 2-of-3 multisig, this still represents a centralized point of control. If a majority of the multisig signers are compromised, collude, or act maliciously, they could unilaterally upgrade the contract to a harmful implementation, potentially leading to loss of funds or system compromise.

IssueAlthough the upgrade authority is managed by a 2-of-3 multisig, this still represents a centralized point of control. If a majority of the multisig signers are compromised, collude, or act maliciously, they could unilaterally upgrade the contract to a harmful implementation, potentially leading to loss of funds or system compromise.

FixWhile a multisig is a strong control, consider further decentralizing the upgrade authority over time, possibly by integrating a more distributed governance mechanism or a larger, more diverse set of signers. Implement strict operational security procedures for all multisig signers, including hardware wallets, secure key management, and multi-factor authentication.

StatusUnresolved

Category Ratings

TechnicalMedium4/10

The proxy contract (ERC1967Proxy) is built upon battle-tested OpenZeppelin libraries, ensuring a robust foundation for its core functionality (7.2 Code Security). The architecture correctly implements the EIP-1967 standard for storage slots, minimizing collision risks (7.1 Architecture). However, a critical technical risk is the unverified source code for the `AlloOFTUpgradeable` implementation contract, making it impossible to assess its security and potential vulnerabilities (7.2 Code Security). This lack of visibility into the core logic significantly elevates the overall technical risk.

GovernanceHigh1/10

The governance model for upgrades employs a 2-of-3 multisig for the `ProxyAdmin` (7.5 Governance), which is a strong access control mechanism, reducing the risk of a single point of failure (7.3 Access Control). This setup requires multiple approvals for critical operations like upgrades. However, the absence of a timelock for upgrades means that once the multisig approves an upgrade, it can be executed immediately, leaving no time for community review or reaction to a potentially malicious change (7.8 Operations). This introduces a moderate economic risk if the multisig signers are compromised or collude.

UpgradesHigh1/10

The system utilizes the EIP-1967 Transparent Proxy pattern, a well-established and secure method for upgradeability (7.7 Upgrades). This pattern correctly separates the admin interface from the implementation, preventing function selector clashes. Upgrades are controlled by a 2-of-3 multisig, enhancing security against unauthorized changes. However, the unverified source code of the implementation contract poses a significant risk, as any vulnerability introduced in an upgrade cannot be independently verified (7.7 Upgrades). Furthermore, the lack of a timelock for upgrade execution increases the operational risk, as upgrades can be deployed instantly without a grace period (7.8 Operations).

Security Checklist

1/5 checks passed

Contract VerifiedPass

Ownership RenouncedFail

No Mint FunctionFail

Liquidity LockedFail

Not a ProxyFail

Proxy Upgrade Controls

Proxy TypeEip1967 Transparent

AdminOZ ProxyAdmin → Multisig 2-of-3

ImplementationVerified source

Upgrades (30d)0 · stable

Holder Composition

93.4% in top 10

87.0% in wallets6.3% in contracts

Effective Concentration89.6%

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

$6.6K across 2 pairs

Uniswap v4USDTanalysed$5.3K Uniswap v4USDT$1.3K

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 Holder100.0%

Top-3 Unlocked100.0%

Key Addresses

2 addresses

Deployer

0x09aa…5f68

Unlocked LP Held By

0x7c9f…b301

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

What Raised This Score

12 factors

Ownership NOT renounced — Multisig (2-of-3)
Mintable supply — no cap found, dilution unbounded
Proxy contract (upgradeable — admin can replace logic)
Top-10 concentration > 70% (93.4% total → 89.6% effective; 87.0% in EOAs, 6.3% in contracts — extreme)
Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
Liquidity < $10k ($6,633 across 2 pairs — easily drained)
LP top1 unlocked holder = 100.0% (independent LP — depth risk, pool = 80% of DEX liquidity)
LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 80% of DEX liquidity)
1 Critical finding(s) from audit
1 High finding(s) from audit
1 Medium finding(s) from audit
1 Low 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

Is Allora Safe?

Security Findings

Unverified Implementation Contract Source Code

Lack of Timelock for Critical Operations (Upgrades)

Reliance on External Contracts for Core Logic

Centralized Upgrade Authority

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 Allora?